Dan Sugalski <[EMAIL PROTECTED]> wrote: I get 1) - 7) and it totally matches my thoughts :)
> 8) We're probably going to have to rejig the string functions some, > and access them via a vtable off strings or something of the sort, so > we can swap in and out threadsafe memory allocation and string > allocation routines. Can you elaborate on that a bit more? Strings are (as any other managed parrot resources) living inside the separated memory pools. Where do you see problems? > 9) We need to add a share() entry to the vtable list for PMCs. To swap in the LOCK-protected vtable variant or to morph() SELF into a shared reference? > Type 1) Start a new thread with a new interpreter that shares > *nothing* with the original, not even any communication. faking fork() for Win32? [ snipped a lot ] > There'll be more, and soon, but let's hack into this part to start > with and we'll go from here. Actually, let's please address things as they arrive. The big picture is very reasonable and of ocurse necessary. OTOH there are many small design issues involved - I did address 2 of these recently - I'd be really glad, if you could have a look at these too ;) leo
