I'm about to start welding in support for multiple interpreters, running
both serially and simultaneously, into Parrot. (With provisions for
starting and coordinating interpreters from other interpreters)
This is just a heads-up, since it probably means platforms without POSIX
thread support will need to provide some workarounds. (I'll be putting
together a generic low-level thread interface with stub routines/#defines
to make things easier) FWIW, I do *not* plan on supporting POSIX d4
threads--final draft or nothin'. (Or, rather, final draft or someone else
writes the wrappers...)
Whether threads of some sort will be required for Parrot's up in the air--I
want to wait and see what sort of performance impact there is before making
that decision.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
