This is the mail archive of the
mailing list for the libstdc++ project.
Re: Why generic definitions of char_traits were removed from libstdc++3?
- From: James Su <suzhe at gnuchina dot org>
- To: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- Cc: bkoz at redhat dot com, libstdc++ at gcc dot gnu dot org
- Date: Thu, 29 Aug 2002 09:31:49 +0800
- Subject: Re: Why generic definitions of char_traits were removed from libstdc++3?
- References: <3D6CA716.firstname.lastname@example.org> <email@example.com>
Will this situation be changed in future libstdc++? If the generic
definitions of char_traits will come back into libstdc++?
Thank you very much.
Gabriel Dos Reis wrote:
James Su <firstname.lastname@example.org> writes:
| Recently, I moved one of my projects from gcc-2.95.3 to gcc-3.2 and
| my project cannot successfully compiled anymore. The reason is the
| generic definitions of char_traits were removed from libstdc++3, and my
| project uses basic_string<unsigned long>.
Hmm, how bad...
| How can I resolve this problem?
There were several discussions about this issue. You might want to
read the thread around
| Can I define char_traits<unsigned long> within my program?
You can do that, but then technically you're invoking an undefined
behaviour. There is no gurantee that it will work with other
standard library implementations or future versions of V3.
| And how
| can I maintain compatiblity of my
| program under deferent environments?
See the other messages of Benjamin's and mine in the thread around
for possible ways to maintain compatibility within V3 and other