On Fri, 2004-09-03 at 04:10, Bradley T Hughes wrote:
> On Friday 03 September 2004 09:41, Markus Ottenbacher wrote:
> [snip]
> > ... or SuSE 8.2/9.1 users (gcc 3.3 and gcc 3.3.3)...
> >
> > Could anyone explain above mentioned workaround? "making an adapted
> > copy-paste of the 'char_traits.h' file" seems rather vague to me.
>
> The standard C++ library distributed with g++ 3.3.x and below properly
> forward declares std::char_traits as defined in the C++ standard... but
> it doesn't actually implement them. It actually only implements 2
> specializations: char and wchar_t. What this means is that if you try
> to use std::basic_string with anything other than char or wchar_t, you
> will get undefined symbols.
>
> Since this is C++, we can work around this, and have it work on all
> standard compliant compilers :) We need to define our own character
> type (typedef unsigned int Uchar;), and then implement a specialization
> of std::char_traits for our character type. See the attached diff (I
> plan on putting this into CVS as soon as I verify it with a few more
> compilers). So far, I've checked g++ 3.3, g++ 3.4 and intel 8.0. I'm
> going to try intel 7.1 and g++ 3.2 before committing.
a) you rock for doing this workaround!
2) it sucks that you have to do this workaround! =:)
--
,-----------------------------------------------------------------//
| Jason 'vanRijn' Kasper :: Numbers 6:22-26
`
| All brontosauruses are thin at one end, much MUCH thicker
| in the middle, and then thin again at the far end. That is
| the theory that I have and which is mine, and what it is too.
,
| bash$ :(){ :|:&};:
`----------------------//
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
List archives: http://asgardsrealm.net/lurker/splash/index.html
Trouble? Contact [EMAIL PROTECTED]
