Hello. On Thu, Sep 23, 2010 at 10:43 AM, Andrew Whitworth <[email protected]> wrote: > Right, so we really have two options: > > 1) We have a "timely" destruction, which isn't timely and isn't > predictable or useful > 2) We explicitly kill PMCs when we want them dead, and risk keeping > references around for later. > > A third option would be to VTABLE_destroy the PMC and morph it into a > Null PMC in-place. Anybody still referencing it will get a Null PMC > exception, but won't crash. We still get freed resources, just not > freed PMC headers. The PMC_IS_NULL macro would have to grow a little, > of course.
I do like idea of morphing explicitly destroyed objects in Null PMC. Looks like it will solve problem with still-referenced PMCs. -- Bacek _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
