Why are you planning an implementation of the JVM in perl?

(I think you meant "Perl" rather than "perl" ? )

What do you hope to gain by adding another level of virtual machine
(ie. adding perl's VM (byte codes) in addition to Java's byte codes).

It will be boatloads slower than one written in a compliled language,
so what advantage do you hope to gain by your efforts?

I know of open-source projects in C, C++, Oberon, and .NET - but not Perl.

Go for it! Perl has one big thing against it (an extra layer of translation
via bytecode) and one big thing for it (associative arrays - a VM spends a
lot of time doing various kinds of table lookups). My two eurocents worth
of advice would be:
 - go for a compile-and-execute approach rather than an interpreter; i.e.
compile the Java bytecode to Perl and throw that at the Perl engine. That
largely overcomes the "two layers of bytecode" problem.
 - use the Classpath libraries for your Java runtime. You'll probably need
to do your own implementation of java.lang.String, java.lang.Class, and a
couple of others, but for the rest you can build on the fine work that's
already been done - and maybe contribute as well ...

See you at the next open-source Java implementors' BOF ...

On 11-Nov-2003, "Mc Kiernan, Daniel Kian"
<Mc-Kiernan@bogus-subdomain.worldnet.att.net> wrote:

Great!