3 Sep
2013
3 Sep
'13
9:33 p.m.
On 9/3/2013 5:16 PM, Klaim - Joël Lamotte wrote:
All the rest is confuse to me so far, but then I have a quesiton: Can block_ptr be considered as a specific implementation of shared_ptr which allows cycles? If yes, what are the costs for the user, compared to shared_ptr?
It uses some base classes from shared_ptr but it is distinct from shared_ptr (you can't cast a shared_ptr to a block_ptr and vice-versa). block_ptr is a cycle manager on top of a shared_ptr but the sizeof(block_ptr) remains == to sizeof(shared_ptr). -Phil