Re: [Sablevm-developer] Obsoleting sablevm-classpath NOW!

[Etienne G. <gag...@uq...>]

Stephen Crawley wrote:
> Sounds like Kissme, though in the Kissme case I call those classes
> kissme specific.  A very minor difference is still a difference.

I know, this is why I see the importance of the --with-vm=xxx option
and m4 system so that:

1- VMs like SableVM & Kissme can share 99% of the code of VM*.java classes.

2- The appropriate 1% gets compiled, depending on which VM is going to use
    the compiled code.

> Kissme currently has a couple of Java classes that implement the system
> class loader.

To be fair, SableVM adds a VirtualMachine.java class as a startup point, but
that class could easily be used by other VMs.  It modifies the provided
gnu.xxx system class loader a little.  [this is the kind of code fixes that
could be shared; the code has nothing "sablevm-specific" to it].

> Skimming through the JVM spec, I haven't found where it states that all
> package-private classes in a package must live in the same ZIP file.

Hmmm... JVMS 5.3 says defining CL + package name + class name uniquely
identify a class; I guess you're right...  There's no such obligation.
My error.  (SableVM implements 5.3).


-- 
Etienne M. Gagnon, Ph.D.             http://www.info.uqam.ca/~egagnon/
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/