4 Apr
2016
4 Apr
'16
1:32 p.m.
On 04/04/2016 04:27 AM, Rob Stewart wrote:
That isn't quite an answer to his question. If I understand you correctly, the point of your library is to provide a means to manage groups of related memory allocations using a root_pointer. Each related memory allocation is, I presume, a node_pointer created from, or attached to, one root_pointer. Because node_ptrs are grouped and owned by a root_ptr, they are (can be?) destroyed, as a group, when the corresponding root_ptr is destroyed, regardless of cycles.
That doing so suffers no performance loss relative to shared_ptr is a bonus, not a reason.
[...]
I answered that on one paragraph above, didn't I?
Thanks Rob, that is a much better answer.