Starting with Kore 0.0.7, I reworked the Java source code to create an
alternative class library for a virtual machine.
kore.alt1a.io <-- java.io
kore.alt1a.lang <-- java.lang
kore.alt1a.net <-- java.net
kore.alt1a.util <-- java.util
I think the JJOS module should have much better support for
cross-compiling. I want to build decaf on one computer and classes.zip on
another. In fact, I want to build, not one, but many flavors of classes.zip.
I want an experimental version of classes.zip for multiple process support.
I want a version with no native methods. I want a version to plug into an
off-the-shelf virtual machine for testing.
If classes.zip were treated more like a shared library on Linux, we would
have separate JJOS and CLASSES modules in CVS. When CLASSES creates
classes.zip, it must be *installed* into the JJOS directory. A symbolic
link from JJOS to CLASSES would be similar to a symbolic link to NASM.
If it were organized this way, JJOS would not be concerned with where the
classes.zip file came from. Is this possible?
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
