Peter Dimov wrote:
From: "Larry Evans" <[EMAIL PROTECTED]>
[snip]
This scan will also have to follow plain pointers.

Plain pointers would have to be followed by a real collector, but why should
a "simple cycle-breaker" bother?
The iplimits.txt file in the shared_cyclic_ptr files directory also illustrates
why raw pointers need to be followed.  Search for:

  2)"pointer cycle with raw cut" -

This also hints at what was lacking in Detlef's article: an explanation
of how to handle containers of smart pointers.  This is handled by the
shared_cyclic_container template defined in shared_cyclic_ptr.hpp.






_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Reply via email to