From owner-freebsd-current@FreeBSD.ORG  Sun Mar 14 17:10:23 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 AC5A916A4CE
	for <freebsd-current@freebsd.org>;
	Sun, 14 Mar 2004 17:10:23 -0800 (PST)
Received: from relay.pair.com (relay.pair.com [209.68.1.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id 4316B43D31
	for <freebsd-current@freebsd.org>;
	Sun, 14 Mar 2004 17:10:23 -0800 (PST)	(envelope-from silby@silby.com)
Received: (qmail 39111 invoked from network); 15 Mar 2004 01:10:22 -0000
Received: from niwun.pair.com (HELO localhost) (209.68.2.70)
  by relay.pair.com with SMTP; 15 Mar 2004 01:10:22 -0000
X-pair-Authenticated: 209.68.2.70
Date: Sun, 14 Mar 2004 19:10:21 -0600 (CST)
From: Mike Silbersack <silby@silby.com>
To: David Gilbert <dgilbert@dclg.ca>
In-Reply-To: <16468.65270.123954.862565@canoe.dclg.ca>
Message-ID: <20040314190825.V56652@odysseus.silby.com>
References: <16468.65270.123954.862565@canoe.dclg.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Mon, 15 Mar 2004 05:00:12 -0800
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 01:10:23 -0000


On Sun, 14 Mar 2004, David Gilbert wrote:

> 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?
>
> Dave.

#include <blahblahblah>
using namespace STD;

or something similar should restore the behavior the application is
expecting.

(Apparently including namespace std is evil, and this is why the FAQs
aren't helpful in telling you this.)

Mike "Silby" Silbersack