
8 Dec
2004
8 Dec
'04
1:53 a.m.
"Thorsten Ottosen" wrote:
I have sometimes spoken with people here that had an interest in allocators that could be reset within containers. For example, some have wanted a
allocator& container::get_allocator(); member function.
The point may be that only container itself is enough to change allocator state, no pointers or external variables that need to be passed down into functions or made global.
One way to solve that problem could be a class like this:
template< class Allocator > class external_allocator { public: // forward to Allocator* member };
With a special allocator, how can one access its specific interface via 'external_allocator'? /Pavel