Message-ID: <002001c0952e$bbcecb60$4358893e@oemcomputer>
From: "Stephen Silver" <djgpp AT argentum DOT freeserve DOT co DOT uk>
To: "DJGPP Workers" <djgpp-workers AT delorie DOT com>
Subject: Re: namespace std and libstdc++ V3
Date: Mon, 12 Feb 2001 20:02:29 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Reply-To: djgpp-workers AT delorie DOT com

Laurynas Biveinis wrote:

> > Could you please explain the practical meaning of this?  
>
> I will, but note that this situation is temporary. I mentioned
> it only to show that things will change.
>
> > Does it mean
> > that non-standard functions will be available in the global namespace?
>
> Yes. In fact, everything is available in the global namespace, and
> standard functions are put in namespace std.

The c_std option doesn't put the standard functions (or anything else)
in namespace std if the user includes <*.h> instead of <c*>.  It was
this sort of incorrect behaviour that I was trying to avoid.

If the ultimate aim is to use the c_shadow headers, then there is
not much point is using my namespace std patches (and the three so
far applied should be removed in order to allow the c_std headers to
be used as a stop-gap).  It may be best to wait until libstdc++ V3
is released before attempting to modify the DJGPP headers to work
with c_shadow.  In the meantime, someone needs to write the wide
character functions.

Stephen