On Thu, 13 Dec 2001 10:48, Paul Hammant wrote: > Peter, > > >>>The problem is that means that the Block has to manage when to > >>> invalidate the proxy. If it is done via BlockContext then Phoenix can > >>> manage when the proxies are invalidated and thus force it to > >>> invalidate at block shutdown. > >> > >>True, but if it is using the proxy internally, then GC will do yes? > > > >Not while it is still referenced somewhere else. The main reason I want to > >use this is to stop people using objects after their creator has been > >shutdown. These other people will still be referencing these objects and > > thus wont be GCed > > But if the alternative was to ask the coder to nullify or undo proxy > during stop() or destruct() methods for a block they it is just > equivalet to a massice tree being GC'd?
They could do that if they wanted but it requires that the programmers be fairly aware of the uses of these sorts of things. I would prefer that the container automagically did it for them. Reduces the likelihood of errors creeping in. -- Cheers, Pete ------------------------------------------------- "Sometimes its better to keep your mouth shut and let people think your an idiot, than to open it and remove all doubt." ------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
