Subj : Re: #include <string> vs #include <string.h>
To   : borland.public.cpp.borlandcpp
From : Nathaniel L. Walker
Date : Tue Feb 22 2005 04:34 am

"I.candide" <i.candide@verizon.net> wrote in message
news:421a31fa$1@newsgroups.borland.com...
>
> How do I get the compiler to accept both instructions?
>
> Does not
>
> <string>
>
> mean the same thing as:
>
> <string.h>?
>
> I know that I can suppress the message, but the explanation leads me to
believe that the compiler will create extranious code when I include
<string.h>.  I was taught that good programming does not include extranious
code.
>

No, <string> is the header for the C++ STL std::string class.  <string.h> is
for C style string functions.

The warnings are of no significance unless you wrote the header and actually
expected the functions
to expand inline.

They are more hints than warnings in reality (at least IMO).

BTW:  About the namespace error, I have quite a few problems with that also.
I haven't bothered
to look through the headers to see what's up, but it's a PITA especially
since I rather use BC++
to test code given it won't force me to create an entirely new
project/workspace to compile/run it
(/rude/ Visual C++).  There may be some extra using std::cin/cout things in
there.  I may check later :)

Nathaniel L. Walker

.