This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: string_char_traits or char_traits
- To: Valignat Cedric <valignat at nevrax dot com>
- Subject: Re: string_char_traits or char_traits
- From: Phil Edwards <pedwards at disaster dot jaj dot com>
- Date: Mon, 29 Jan 2001 07:42:39 -0500
- Cc: libstdc++ at gcc dot gnu dot org
- References: <20010129124842.A33739@nevrax.com>
On Mon, Jan 29, 2001 at 12:48:42PM +0100, Valignat Cedric wrote:
>
> I'm far away to be a C++ guru, so did i misunderstood something ?
> is it for internal use only ?
> or is it a compatibility problem ?
Given those three choices, let's call it a compatibility problem.
Your understanding is correct, and char_traits is certainly for public use;
it exists to be specialized, after all. But the library you are using is
quite old and outdated, and very very non-conforming to the ISO standard.
The most recent release of the compiler shipped with that library, so even
if you are using GCC 2.95.2, the C++ support library will cause problems.
If you must use 2.95.2, you have a few choices, including using STLport to
override the headers which come with the old libstdc++-v2, or downloading
one of the pre-2.91 snapshots of libstdc++-v3. If you are not restrained
to using GCC 2.95.2, then one of the recent compiler snapshots will include
the new ISO-compliant library.
Luck++;
Phil
--
pedwards at disaster dot jaj dot com | pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools. Fools are protected by more capable fools.