Nigel Sandever writes: > Maybe it would be possible (for me + others) to write the core of a win32 specific, > threaded VM interpreter that would take parrot byte code and run it. Thereby, > utilising all the good stuff that preceeds the VM interpreter, plus probably large > chunks of the parrot VM, but provides it with a more native compatible target.
You want to write a parrot? Um, good luck. One thing Uri mentioned was writing platform specific macro code, and he dismissed it with that it's "also a pain". While I agree that it's a pain, and it's about as maintainence-friendly as JIT, I don't think it has to be ruled out. Parrot is platform-independent, but that doesn't mean we can't take advantage of platform-specific instructions to make it faster on certain machines. Indeed, this is precisely what JIT is. But a lock on every PMC is still pretty heavy for those non-x86 platforms out there, and we should avoid it if we can. Luke > > That's something that obviously not a simple project and is beyond the scope of > this list. > > Thanks for taking the time to review this. > > Nigel Sandever. > >
