basic_string - once more...

[Stefan Olsson]

Hi!

I have just read through the lengthy discussion regarding the memory
allocation issues with basic_string<> where the 2.95 seems to have an
"allocate a block" and 3.0 an "allocate exact the requested amount".

I am well aware that one should use the .reserve() method where ever
possible, but the "old" approach has the advantage of being well-behaved
when inserting/deleting from map's, vector's etc...

Is there any way to "add the old approach" to the current stdc++?

Our specific application relies hevily on map's and such containers and
the performance and level of memory fragementation that the current
stdc++ generates is to high...

Thanks for input!

/Stefan

--
Military intelligence is a contradiction in terms.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20011106/3a0d1fca/attachment.htm>