[v3] __pool_alloc locking bits

[Carlo Wood]

On Fri, Jun 25, 2004 at 01:09:06AM -0500, Benjamin Kosnik wrote:
> The problem is that the derived class is a template, and thus with
> multi-locks, allocator<int>::allocate and allocator<char>::allocate are
> different code paths. Thus, if both these codepaths are called in
> separate threads, with different size allocations, and thus mutexes,

Benjamin, is this is a feature or could it be changed in a future release?
I am relying on allocator<Foo1> and allocator<Foo2> to be *different*
memory pools (assuming they are memory pools at all).  Is this something
that might change in the future?

-- 
Carlo Wood <carlo@alinoe.com>