Scott Furman wrote:
>
> John Keiser wrote:
>
> > Does Electrical Fire currently work with JDK (and implement its native
> > methods)?
>
> Currently, to run EF you need to download the official JDK1.2 jar file.
>
> > In that case, it shouldn't take long to port. Japhar was
> > designed that way, too, and the port Aaron did didn't take very long at all.
> > A few renamed methods, mostly. If you look in
> > http://www.classpath.org/cvs/vm/reference, there is a code for all of the
> > ~10 classes you'll need to implement.
>
> I'm not sure what VMObject is for. If the VM already implements
> java.lang.Object, can VMObject simply be a trivial subclass of it ?
Actually, it works the other way around. Classpath implements
java.lang.Object, but because there are a few methods in
java.lang.Object that are VM specific, the VMObject class is provided by
the VM. It provides a few static final methods that Classpath's
java.lang.Object calls for things like wait() and notify().
The same thing goes for the other VMxxxx classes. The bulk of the work
is done by Classpath, but the few VM-specific methods are done by the
VM.
The other classes in vm/reference, such as Class and all the
java.lang.reflect classes, must be implemented completely by the VM.
Hope this clarifies things,
Stuart.
