Hi, Anybody knows what happened to the iterator that was suggested? I mean, what keeps it from being added to the library? Michael Marcin-2 wrote:

Yes, destructing and recreating the object pool will release and allocate memory with the system heap.

- Michael Marcin

May that be avoided by calling the destructors and constructors directly? For example, destroy_all (object_pool& pool) { pool.~object_pool(); new (&pool) object_pool(); } I'm not sure about the correctness of those instructions. Anyway, its not something you want all around your code. -- View this message in context: http://www.nabble.com/-pool--object_pool%3A%3Adestroy_all--%28from-users%29-... Sent from the Boost - Dev mailing list archive at Nabble.com.