This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: string reserve()
- To: "ColinThomas at dunelm dot org dot uk" <ColinThomas at dunelm dot org dot uk>
- Subject: Re: string reserve()
- From: Phil Edwards <pedwards at disaster dot jaj dot com>
- Date: Fri, 31 Aug 2001 14:54:35 -0400
- Cc: "'libstdc++ at gcc dot gnu dot org'" <libstdc++ at gcc dot gnu dot org>
- References: <01C13261.76AAB500.ColinThomas@olneybucks.freeserve.co.uk>
On Fri, Aug 31, 2001 at 09:10:57PM +0100, Colin Thomas wrote:
> Back to the original question:
>
> How do I know what version of libstdc++ my gcc (2.95.2) is using which gives the reserve() problem ?
Not our version.
More specifically: gcc 2.95.2 does not support the new libstdc++-v3.
If you're using gcc 2.95.2 you're using the old libstdc++. The code is
different; in the case of the string class, it's /completely/ different.
The old library is not maintained and not supported.
> Has the problem re c++ string reserve() not altering the c++'s string capacity been seen before,
Not that I recall. You can go to the libstdc++-v3 homepage at
gcc.gnu.org/libstdc++/ and search the mailing list archive, though.
You might just try your code with gcc 3.0 and see what happens.
Or CodeSourcery has an online "try it out" interface to gcc 3.something;
you can go to www.codesourcery.com and try it out.
--
Would I had phrases that are not known, utterances that are strange, in
new language that has not been used, free from repetition, not an utterance
which has grown stale, which men of old have spoken.
- anonymous Egyptian scribe, c.1700 BC