At 03:59 PM 9/20/2001 +0200, Arthur Bergman wrote:
>While it has been decided that perl should be using ithread like
>threading, I guess that is irelevant at the parrot level. Are you
>going to have one "virtual cpu" per thread with it's own set of registers
>or are you going to context switch the virtual cpu?
What we're going to do is fire up a new interpreter for each thread. (We
may have a pool of prebuilt interpreters hanging around for this
eventuality) Threading *is* essential at the parrot level, and there are
even a few (as yet undocumented) opcodes to deal with them, and some stuff
that's an integral part of the variable vtable code to deal with it.
Whether it's considered ithread-like or not's up in the air--it'll probably
look a lot like a mix.
I'm also seriously considering throwing *all* PerlIO code into separate
threads (one per file) as an aid to asynchrony.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
