Posted by: Anonymous Coward
on February 28, 2004 06:03 AM
No, more like this:
Perl source --> Parrot bytecode --> Parrot VM Python source --> Parrot bytecode --> Parrot VM Java source --> Parrot bytecode --> Parrot VM BASIC source --> Parrot bytecode --> Parrot VM
And so on. Compilers for all these languages would be re-implemented to generate Parrot bytecode rather than bytecode for their respective native VMs. It's basically the same strategy as the<nobr> <wbr></nobr>.NET runtime, except with an open-source, register-based VM instead of a closed-source, stack-based VM.
It can certainly be done; Python has already been re-targeted for the Java VM ("Jython"); and Parrot is already running BASIC and partial implementations of Perl, Python, and several other languages.
Learn about Linux
Download Linux
Get Linux help
Re:Yay!
Posted by: Anonymous Coward on February 28, 2004 06:03 AMPerl source --> Parrot bytecode --> Parrot VM
Python source --> Parrot bytecode --> Parrot VM
Java source --> Parrot bytecode --> Parrot VM
BASIC source --> Parrot bytecode --> Parrot VM
And so on. Compilers for all these languages would be re-implemented to generate Parrot bytecode rather than bytecode for their respective native VMs. It's basically the same strategy as the<nobr> <wbr></nobr>.NET runtime, except with an open-source, register-based VM instead of a closed-source, stack-based VM.
It can certainly be done; Python has already been re-targeted for the Java VM ("Jython"); and Parrot is already running BASIC and partial implementations of Perl, Python, and several other languages.
#