Date: Tue, 16 Mar 2004 06:19:51 +0800 (CST) From: "M. Warner Losh" <imp@bsdimp.com> To: dgilbert@dclg.ca Cc: freebsd-current@freebsd.org Subject: Re: GCC include files conundrum. Message-ID: <20040316.061951.58644040.imp@bsdimp.com> In-Reply-To: <16468.65270.123954.862565@canoe.dclg.ca> References: <16468.65270.123954.862565@canoe.dclg.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <16468.65270.123954.862565@canoe.dclg.ca>
David Gilbert <dgilbert@dclg.ca> writes:
: The C++ FAQ referred to by iostream (not iostream.h) seems to imply
: that you should use iostream and sstream (no .h)... but including
: those files imposes a very different standard that this port is not
: ready to accept. It appears that (among other things that I havn't
: found yet) all 'istream' must be written 'std::istream' ... etc.
:
: So what's the solution?
Fix the code. Use the new, non .h variation. And put 'using
namespace std;' at the top of your files *OR* fix all the uses to have
std:: in front of them. That's C++, get used to it. :-)
C++ used to define things differently, but as compilers become more
standards conforming, you'll see more and more things like this.
The old .h files are obsoleted.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040316.061951.58644040.imp>