At 4:51 PM +0100 3/4/04, Leopold Toetsch wrote:
Dan Sugalski wrote:
It'd be simple enough to do--prepend a PObj front to the vtables
and allocate the vtables themselves out of a separate managed
arena, and do a bit of custom mark noting. This'd make collecting
up unused vtables easy enough.
Dan Sugalski [EMAIL PROTECTED] wrote:
At 4:51 PM +0100 3/4/04, Leopold Toetsch wrote:
Rather not. But if we have to allocate a separate vtable, we should
set a flag in the vtable-flags, mark the PMC as special, so that
destroy can free the vtable.
That works for one-off vtables, but doesn't
It'd be simple enough to do--prepend a PObj front to the vtables and
allocate the vtables themselves out of a separate managed arena, and
do a bit of custom mark noting. This'd make collecting up unused
vtables easy enough. The downside to this is it means we add in a
*lot* of extra pointer
Dan Sugalski wrote:
It'd be simple enough to do--prepend a PObj front to the vtables and
allocate the vtables themselves out of a separate managed arena, and do
a bit of custom mark noting. This'd make collecting up unused vtables
easy enough. The downside to this is it means we add in a *lot*
