On Sat, Aug 16, 2008 at 1:50 AM, Clément Vasseur <[EMAIL PROTECTED]> wrote:
> - expose the `GC_GENERAL_REGISTER_DISAPPEARING_LINK' function in neko > in order to let the developper register a "disappearing link", which > will allow the finalization pass to figure out a correct order. > > - use `GC_REGISTER_FINALIZER_NO_ORDER' to register the abstract > finalizer, thus allowing the gc to call the finalizers in any order > and release the memory properly. I just saw a third solution you used in the mysql binding. It looks like you simulate `GC_GENERAL_REGISTER_DISAPPEARING_LINK' by incrementing the address by one, thus making it an invalid pointer. This is more clever than the libgc function because it does not require any additionnal storage. Is it the way you recommand to do it? -- Neko : One VM to run them all (http://nekovm.org)
