Actually , if a linguistic way became available in RB by which a "parent" instance were able to instantiate a "child" class, assign the reference to one of its properties , and be able to specify that the the child automatically has "scope" access to all the properties and methods of its "container" without needing to have any reference back to the "parent" then we could avoid this common cyclic reference scenario altogether.
On 21/4/07 14:15, "Daniel Stenning" <[EMAIL PROTECTED]> wrote: > Handling memory leakage is something so common - > particularly for the ubiquitous "parent-child" problem - that it cries out > for an ELEGANT solution. Regards, Dan _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
