From: Philippe A. Bouchard (philippeb_at_[hidden])
Date: 2002-10-09 11:22:02
I would like to know more about the concepts behind shared_cyclic_ptr.
I am convinced placed_ptr<> is optimized enough... deallocation optimization
was highly probably already defined by the Standards Committee. Before we
start, I was wondering if this possibility was included in some other form:
- record each heaped shared_ptr<> instanciation in a static list;
- record each heap allocation address in some static list;
- record each heap allocation size in a static list;
- when memory is exausted, figure out which shared_ptr<> is a member of a
heap block to isolate cycles.
This will help a lot, thanks.
BTW (moderators): "No more tree_traits<> dependencies under placed_ptr<>",
10/02/2002, is not in the archives anymore (?!?)
Philippe A. Bouchard
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk