https://svn.boost.org/trac10/ticket/2179 <p> Today shared_ptr works very well, but it makes it difficult for the C++ application to retain control over the lifetime of its objects. Variables in the interpreter which are hard to clear can prevent an object from being deleting. </p> <p> weak_ptr support would be the ideal solution. A application could hand out only weak_ptrs to Python. The object could then be deleted as normal. </p> <p> Attempting to use a weak_ptr in Python if the object has been released should throw. Python code which knows its objects might be deleted out from under it can catch this exception. </p> <p> See thread w/ Dave Abrahams titled "application exit and shared_ptr" in C++-sig. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/2179 Trac 1.4.3 Dave Abrahams Sat, 28 Nov 2009 18:38:29 GMT