
24 Oct
2008
24 Oct
'08
2:40 p.m.
That said, there doesn't seem to be any reason why we could not expose the tag used by pool_allocator (and fast_pool_allocator) to parameterization. The result might look something like this:
template <typename T, typename UserAllocator = default_user_allocator_new_delete, typename Mutex = boost::mutex, unsigned NextSize = 32, typename Tag = pool_allocator_tag> class pool_allocator;
Would that do what you want?
I suppose no, because there still may be several underneath singleton_pools, so i wouldn't be able to release all memory, allocated by this allocator. Thanks for your reply. I will try to find other ways, how to solve it. VoidEx