Posted by: Anonymous Coward
on February 27, 2004 11:31 PM
Pardon me? I don't seem to understand this.
Is this what Parrot is all about?
Pyhon Bytecode --> Perl --> Execution at runtime
Java Bytecode --> Perl --> Execution at runtime
Ruby Bytecode --> Perl --> Execution at runtime
In other words, you make an interpreter for which you make another interpreter for which you code your program for.
I thought Java was slow on its own, whitout another interpreter interpreting its own interpreter.
Wait! I got an idea. Lets write a Perl VM in Perl! That way Perl would really be ported to every platform. Who cares if that second VM would only run if you have a machine-os native VM and it would be really slow to run real world programs. Better yet, lets run our VM in another copy of our VM in another copy of our VM in another<nobr> <wbr></nobr>... in the real VM in some actual machine. Yes! that's it.
Or better yet, let's rewrite <A HREF="http://bochs.sourceforge.net/" TITLE="sourceforge.net">Bochs</a sourceforge.net> (a program wich emulates an i386/i486/Pentium/Pentium Pro/AMD64 based machine at the hardware and bios level so it can run multiple OS and it is written in C++ so it can be compiled for other hardware platforms) in Perl! That whay we can have all on that running on top of Bochs running on an aditional copy of our VM running on<nobr> <wbr></nobr>.. another copy of Bochs running on another Bochs running on an a really old Amiga!
Talk about SLOW.
<SERIOUS>
Actually, a Java to C++ compiler would be a more interesting project, if Sun decides to open source it.
Learn about Linux
Download Linux
Get Linux help
Re:Yay!
Posted by: Anonymous Coward on February 27, 2004 11:31 PMIs this what Parrot is all about?
Pyhon Bytecode --> Perl --> Execution at runtime
Java Bytecode --> Perl --> Execution at runtime
Ruby Bytecode --> Perl --> Execution at runtime
In other words, you make an interpreter for which you make another interpreter for which you code your program for.
I thought Java was slow on its own, whitout another interpreter interpreting its own interpreter.
Wait! I got an idea. Lets write a Perl VM in Perl! That way Perl would really be ported to every platform. Who cares if that second VM would only run if you have a machine-os native VM and it would be really slow to run real world programs. Better yet, lets run our VM in another copy of our VM in another copy of our VM in another<nobr> <wbr></nobr>... in the real VM in some actual machine. Yes! that's it.
Or better yet, let's rewrite <A HREF="http://bochs.sourceforge.net/" TITLE="sourceforge.net">Bochs</a sourceforge.net> (a program wich emulates an i386/i486/Pentium/Pentium Pro/AMD64 based machine at the hardware and bios level so it can run multiple OS and it is written in C++ so it can be compiled for other hardware platforms) in Perl! That whay we can have all on that running on top of Bochs running on an aditional copy of our VM running on<nobr> <wbr></nobr>.. another copy of Bochs running on another Bochs running on an a really old Amiga!
Talk about SLOW.
<SERIOUS>
Actually, a Java to C++ compiler would be a more interesting project, if Sun decides to open source it.
</SERIOUS>
#