Stuart Ballard <[EMAIL PROTECTED]> writes:
> Tom Tromey wrote:
> >
> > 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.
>
> Or a variant - a (perl?) script that would convert CNI into JNI at the
> source-code level, which could be simply omitted if CNI were to be used.
> Some extra annotations might be needed in the source in order for the
> script to identify code that needs to be processed.
Oh bugger, compared to the amount of Java out there, we might as well
just dup the work and have both versions... there's plenty of crap
that will be different between libgcj vs kaffe vs japhar vs etc in the
vm/* world.
Plus it's simple and changeable, also allowing for JNI or CNI specific
hacks... which is well just adding more complication if you try to do
it Paul's way or the Perl way, etc.
Brian
--
Brian Jones <[EMAIL PROTECTED]>
