On Sat, 2005-04-30 at 09:19 +0200, Leopold Toetsch wrote: > BTW shouldn't we really separate C<destroy> and C<finalize>? The latter > would be overridable by user code, the former frees allocate memory.
I think that's wise and I thought that was the plan. Certainly for *Struct PMCs I don't care when Parrot releases memory, but I want a chance to make sure that I can release unmanaged memory at some point. For filehandles I want to make sure that I can close them at some point, not necessarily have them collected. It's finalization that matters here, not destruction. -- c
