From owner-freebsd-current@FreeBSD.ORG  Mon Mar 15 14:19:42 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1633016A4CE; Mon, 15 Mar 2004 14:19:42 -0800 (PST)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 6AD8643D1F; Mon, 15 Mar 2004 14:19:41 -0800 (PST)
	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.10/8.12.9) with ESMTP id i2FMJVkj074743;
	Mon, 15 Mar 2004 15:19:31 -0700 (MST)
	(envelope-from imp@bsdimp.com)
Date: Tue, 16 Mar 2004 06:19:51 +0800 (CST)
Message-Id: <20040316.061951.58644040.imp@bsdimp.com>
To: dgilbert@dclg.ca
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <16468.65270.123954.862565@canoe.dclg.ca>
References: <16468.65270.123954.862565@canoe.dclg.ca>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: freebsd-hackers@freebsd.org
cc: freebsd-current@freebsd.org
Subject: Re: GCC include files conundrum.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Mar 2004 22:19:42 -0000

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