Aaron> -- Identify a way to resolve the CNI versus JNI issue. JNI is the
Aaron> Java standard for calling native methods. Classpath needs to support
Aaron> this for standards compliance. CNI is the Cygnus Native Interface,
Aaron> an efficient method for calling native code, but one limited to use
Aaron> with gcj. Cygnus wishes to continue using this because it is more
Aaron> efficient than JNI in their implementation, and uses substantially
Aaron> easier and more readable native code. Proposed solutions to date:
Aaron> o Binary interface
Aaron> o A .in file that is pre-processed through a script to generate
Aaron> CNI or JNI as desired.
Aaron> o Multiple implementations with a compile time switch.
My understanding is that Paul is looking into this. Paul, am I right?
His idea, which isn't listed, is to use wrapper classes to make it
possible to write CNI code which is compiled by the C++ compiler into
JNI calls.
Aaron> -- java.security: Debug the implementation and get it working
Aaron> with Japhar and/or gcj. Mark Benvenuto ([EMAIL PROTECTED])
Aaron> wrote this, but I'm not sure that it is totally running.
libgcj has a partial java.security implementation. Mark got in touch
with Warren & me about doing a merge with the libgcj version.
Aaron> -- Figure out a way to generate a hardcopy manual for the Java
Aaron> class library from the embedded Javadocs. This probably
Aaron> involves writing a custom doclet and probably some
Aaron> supplementary documentation files into which the extracted
Aaron> Javadoc files are included.
Couldn't we make a doclet to generate texinfo?
T
