libstdc++/9615: STL classes are not in the std namespace
Kevin Henry
kevin.henry@amdocs.com
Fri Feb 7 18:11:00 GMT 2003
It's not decided by SGI 'a few days ago', as you say. It's in the STLPort4 code from last February as being in that location, in Microsoft's STL provided with MSVC 6.0 (from '96?) All other platforms have these STL portions in the std namespace, and because of these changes, STL on gcc3.x.x is useless! STL was originally conceived by SGI, not as part of the C++ standard. The changes that have been made to the compiler make it impossible for me to use STLPort4 instead of the supplied STL.
I will not get into a shouting match over your definition of standard.
Thanks for your lack of help.
Kevin
> -----Original Message-----
> From: paolo@gcc.gnu.org [mailto:paolo@gcc.gnu.org]
> Sent: Friday, February 07, 2003 12:45 PM
> To: gcc-bugs@gcc.gnu.org; gcc-prs@gcc.gnu.org; khenry@amdocs.com;
> nobody@gcc.gnu.org
> Subject: Re: libstdc++/9615: STL classes are not in the std namespace
>
>
> Synopsis: STL classes are not in the std namespace
>
> State-Changed-From-To: open->closed
> State-Changed-By: paolo
> State-Changed-When: Fri Feb 7 17:45:14 2003
> State-Changed-Why:
> Why do you think we have moved that stuff to the __gnu_cxx
> namespace and the ext dir? Because it's _not_ standard!
> On the other hand, all of the standard STL classes, where
> standard means as mandated by ISO/IEC 14882 International
> Standard (not what happened to be chosen by SGI a few
> days ago, which is _completely_ irrelevant) _are_ in
> namespace std.
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&
database=gcc&pr=9615
>
-------------- next part --------------
-------------------------------------------------------------------------------------
The information contained in this message is proprietary of Amdocs,
protected from disclosure, and may be privileged.
The information is intended to be conveyed only to the designated recipient(s)
of the message. If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination, use, distribution or copying of
this communication is strictly prohibited and may be unlawful.
If you have received this communication in error, please notify us immediately
by replying to the message and deleting it from your computer.
Thank you.
-------------------------------------------------------------------------------------
More information about the Gcc-bugs
mailing list