On 03/01/2016 08:14 AM, Phil Bouchard wrote:

Sorry I forgot that the header node is instantiated on the stack. Smart pointers pointing to objects on the stack doesn't work so therefore modifications to the Container API will be needed to support smart pointers.

Also once that works I could define some typedefs: namespace boost { namespace container { template <typename T> using block_list<T> = list; template <typename T> using block_vector<T> = vector; [...] } } Boost will then be the underlying library of choice for all other languages relying on the current state of garbage collectors. -Phil

On 03/01/2016 03:23 PM, Rob Stewart wrote:

On March 1, 2016 8:14:20 AM EST, Phil Bouchard wrote:

...

Sorry I forgot that the header node is instantiated on the stack.

Do you mean that the header node is part of the container object? If so, it may be allocated on the stack or the free store depending upon how the container itself was allocated.

Yes exactly.

On 03/01/2016 04:27 PM, Ion Gaztañaga wrote:

On 01/03/2016 14:14, Phil Bouchard wrote:

...

Sorry I forgot that the header node is instantiated on the stack. Smart pointers pointing to objects on the stack doesn't work so therefore modifications to the Container API will be needed to support smart pointers.

Supporting embedded end pointers is not only an option, but the choice of most STL implementations. It makes default constructors nothrow and improves performance. Any smart pointer should support pointing to those end nodes or it's just broken for STL-like containers.

You're right. I think there's a way for block_ptr<> to support weak references and I will get rid of the strange pointer-on-the-heap initialization optimization at the same time. Regards, -Phil

On 03/01/2016 10:40 PM, Phil Bouchard wrote:

On 03/01/2016 06:20 PM, Phil Bouchard wrote:

...

On 03/01/2016 04:27 PM, Ion Gaztañaga wrote:

...

Supporting embedded end pointers is not only an option, but the choice of most STL implementations. It makes default constructors nothrow and improves performance. Any smart pointer should support pointing to those end nodes or it's just broken for STL-like containers.

You're right. I think there's a way for block_ptr<> to support weak references and I will get rid of the strange pointer-on-the-heap initialization optimization at the same time.

I just added support for weak references but I still have problems with Boost containers: https://github.com/philippeb8/block_ptr/blob/master/example/block_ptr_test2....

Ok now everything works!! https://github.com/philippeb8/block_ptr/blob/master/example/block_ptr_test2.... So now block_ptr<> is Boost.Container compliant! I still need to fix an issue but it's moving forward! Thanks, -Phil