Vladimir Lipsky <[EMAIL PROTECTED]> wrote: > From: "Leopold Toetsch" <[EMAIL PROTECTED]> > Sent: Wednesday, December 03, 2003 12:05 PM
>> The bug is already fixed. But we have to separate interpreter globals >> and real globals finally. Some time ago, I suggested to change the init >> functions slightly to take a parent interpreter argument: > Do you think you could clarify in what way it relates to separating > different sorts of globals. Thanks in advance. We have to know if we are constructing (or destroying) the first/last interpreter or not. Real globals go with the "main" interpreter, per interpreter globals go with each. It doesn't help in separating globals (this is a design decision) but its necessary when constructing/destructing interpreters. Parrot_base_vtables[] is now a real global. But when different threads are constructing different classes, we have to use separate master vtables. This means, that on construction of a new interpreter, we have to copy the existing Parrot_base_vtable[]. > 0x4C56 leo
