On 6/12/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> > > It kinda has been in "Rule of
Thumb #5" ... The simple answer is that
> ownership wrt strong pointer implemenations that don't support cycles
> (like ref_ptr) is always directed. Therefore in the Caveat #4, either
> class A or class B must be designed to hold a ref_ptr to (ie own) the
> other.
... or a third class must be introduced into the design to break the
cycle.
Or... just use osg::observer_ptr<> in place of one of the ref_ptr<>...
Robert.
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
