if there is still an outstanding reference, whether it be a top level object or a composed object, there won't be any garbage collection on that object.
When all references, top level or composed, are removed, garbage collection will occur. Write yourself a test case on your machine and try it. You'd be surprised what you can learn with experimenting. Dan On 2/18/09, Henry <[email protected]> wrote: > > Some dumb language can't GC cyclical references. CF is not one of them > right? > > Henry > > On Feb 18, 6:20 pm, Brian Kotek <[email protected]> wrote: >> Yes, as long as you don't go too far and end up where the last thread left >> off, with an object that is packed with delegating methods. >> >> There's actually nothing wrong with cyclical references. I wouldn't want >> them all over my code, but in some cases they are necessary. >> >> On Wed, Feb 18, 2009 at 8:57 PM, Henry <[email protected]> wrote: >> >> > Thanks Brain. So essentially you're saying, C can have a reference to >> > A directly, even though C also has B that has A? > > > -- "Come to the edge, he said. They said: We are afraid. Come to the edge, he said. They came. He pushed them and they flew." Guillaume Apollinaire quotes --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
