Re: [Boost-users] Object pools?

Diederick C. Niehorster wrote:

the object should be guaranteed to not be destroyed if only pool or outside holder is destroyed, but should be guaranteed to be destroyed when both are destroyed.

The only way I've currently found to have the object destroyed, if the pool is already gone, is to have a static class registered with the boost::shared_ptr. This gives the static class the ability to destroy the object if the pool has unregistered itself. I don't like this as it creates a bottleneck on deletes. Ryan