From: Stephan Tolksdorf (andorxor_at_[hidden])
Date: 2006-06-28 12:57:44
I already posted this message a week a ago, but there were some problems
with the mailing list and I got no replies, so I give it another try:
I was looking for a lightweight Allocator interface and found many
references to the UserAllocator interface from Pool
I'm not sure if the interface was designed to be used outside of Pool in
the first place, but if one tries to do so, the signature of the free
function becomes a problem. The free function currently takes a char*
const argument, which makes it difficult to use as a deleter for
shared_ptrs and requires a typecast everytime one wants to free memory.
What is the design rationale for not using a void* (non-const) argument?
Could the specification be changed?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk