On 4/11/2011 1:54 PM, Nevin Liber wrote:
On 11 April 2011 14:47, Phil Bouchard<philippe@fornux.com> wrote:
I see the Boost.Pool is not making its way up to the C++ standards yet an it is very unfortunate given its great use. Boost.Pool provides an is_from() member function that does a simple range check and returns whether a pointer is part of the pool or not. This is a very useful function which I think should be part of the standards because it could be used for the global pool as well; i.e. the one used by operator ::new and ::delete. The benefits outweigh the costs.
What are the costs?
The cost of having to pollute the global namespace.
As far as I know, there is no requirement that the heap be contiguous.
I meant range checks of the heap memory pages...
Plus, the intent is that implementations can use C's malloc calls, and the malloc interface doesn't expose this.
This is actually surprising.
If you seriously want this feature, contact your friendly neighborhood C committee member... :-)
I will, thanks. -Phil