"Aaron M. Renn" <[EMAIL PROTECTED]> writes:
> It looks like the natDeflater.cc and natInflater.cc files that
> implement the native methods from this package use CNI and thus are
> Cygnus specific. Did anybody ever resolve anything on this?
First off, we need to create a branch to do the merger work on. I
don't have a problem with using HEAD, and making a tag for the state
of the tree prior to the merger work. Does that sound OK?
The JNI/CNI issue can be temporarily postponed. I suspect that we'll
end up using my C++ layer, because it'll get the job done, and it's
rather trivial to implement. It's not the optimal solution, but it
will permit us to generate JNI code from the majority of CNI code.
gcj can handle both JNI and CNI. So we can safely use a mixture of
JNI and CNI as we do the merge, and gcj as well as other VMs can still
make use of Classpath. (Kaffe now also has support for libraries that
use CNI.)
