Michael Klaus <[EMAIL PROTECTED]> writes: > > I think on the todo list (mental, group collective, etc.) is to take > > everything with a native method and create two versions... Foo and > > VMFoo. VMFoo could have native methods and JNI or someone else could > > provide VMFoo that is written in some completely different way. Does > > that help? > > It takes us a step further definitely :o) > > Just for clearance: > We got a directory structure like > <jnode>/src/classpath the core api packages from classpath.org > <jnode>/src/jnode out project specific packages > > Our build.xml compiles both roots into one 'classes' directory. > > In case of, java.io.File, we would > - create jnode/java/io/VMFile.java > - modify classpath/java/io/File.java to delegate all > OS-dependent parts to java.io.VMFile > - donate the File.java to your project so all other VMs can > be made fit to this > > Is that right?
I think so, but I'm now cc'ing the classpath list to make sure I got this correct. You might want to take a look at our requirements for contributing code at http://www.gnu.org/software/classpath/ in the hacking guide. Brian -- Brian Jones <[EMAIL PROTECTED]> _______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
