|
Boost : |
From: Thorsten Ottosen (thorsten.ottosen_at_[hidden])
Date: 2007-02-24 16:49:56
JOAQUIN LOPEZ MU?Z wrote:
> ----- Mensaje original -----
> So, the problem is far (IMHO) from simple and involves
> other important and as of yet not completely settled
> issues like move constructors and extended allocators
> (see http://www.open-
> std.org/jtc1/sc22/wg21/docs/papers/2006/n2045.html,
> problem #5).
Ok, so the problem is essentially
cause by the lack of contruction functions for the
allocator.
And placement new + ~T() + allocate() + deallocate()
is not a viable approach to avoid using construct()/destroy()?
-Thorsten
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk