This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

basic_string - once more...

From: Stefan Olsson <stefan at noname4us dot com>
To: libstdc++ at gcc dot gnu dot org
Date: Tue, 20 Nov 2001 16:44:50 +0100
Subject: basic_string - once more...
Organization: Noname4us

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.

Follow-Ups:
- Re: basic_string - once more...
  - From: Benjamin Kosnik

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]