Re: [Boost-users] custom allocators, pool_alloc release_memory() seems to be broken

AMDG B Hart wrote:

nope, continued upwards and release_memory() always returns false.

I stepped though #include #include <set> int main() { { std::set s; for(int i = 0; i < 100; ++i) { s.insert(i); } } boost::singleton_pool::release_memory(); } and the call to release memory does seem to work.

Also, I would say that release_memory is broken, or needing revision, if one has to guess what the pool size is.

It isn't broken. release_memory works fine if you can find the right pool. Because std::set does not expose the type that it actually allocates there is no portable way to do so. In Christ, Steven Watanabe