Ack. I sent that too soon. Correcting the obvious lack of clarity: On 20 July 2013 17:25, William ML Leslie <[email protected]> wrote: > You can see how you can use it to ensure resource finalisation order: > an object can't be eligable for finalisation if it is still referred > to by a weakref callback; in particular, a weakref callback can't > maintain a reference to the object it's supposed to be finalising > because that's a nearly trivial cycle that prevents disposal. It
It's not the cycle that prevents disposal, it's the fact that this map is a GC root, and the object is now reachable via a non-weak reference. -- William Leslie Notice: Likely much of this email is, by the nature of copyright, covered under copyright law. You absolutely may reproduce any part of it in accordance with the copyright law of the nation you are reading this in. Any attempt to deny you those rights would be illegal without prior contractual agreement. _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
