Proposal for CNI/JNI problems

I've been working on coming up with an "acceptable" solution for dealing with our current merger problems regarding the use of CNI and JNI. While it's important that Classpath continue to support JNI, CNI does have significant benefits, and I'd like to start porting Classpath to CNI, assuming we

Fwd: [Jikes] Version 1.11 available

Version 1.11 is now available. See News section for new policy on providing binaries. See http://oss.software.ibm.com/developerworks/opensource/cvs/jikes/jikes/src/ChangeLog for summary of recent changes. To get off the jikes list, send a message containing the word "unsubscribe" (i

Re: Proposal for CNI/JNI problems

Paul Fisher <[EMAIL PROTECTED]> writes: > While it's important that Classpath continue to support JNI, The first question is why? What is the goal? (Obviously JVMs should support JNI; that is not my question.) Presumably, the goal is that Classpath can be used as the standard Java library for