Sorry for the extra message. Outlook - need I say more? Hello all,
I have started to port some of my code that relies on Dolphin's finalization. The idea is that one sends #beFinalizable to the object requiring finalization. Dolphin sets a flag on the object (in its header??) that the vm later notices. The end result is the object in question receives #finalize and cleans up its own mess; it can also "cheat death" but I doubt I have need for that level of control. My question is that the Squeak/Pharo design appears to be built on ObjetFinalizer instances that are associated with finalizable objects, each recording what to do when an object expires. If that's true, then I'm wondering why objects understand #finalize. That seems to conflict with #toFinalize:send:to:with:, which looks like it expects just enough information to do the cleanup for the expired object. Any idea what I might be missing here or pointers to required reading? I found something from 2003 (Squeak 3.7) which might be out of date, or maybe I'm just working too late :) Bill _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
