JNI without Jni_Lookup() ?

[Erik Poupaert <erik dot poupaert at skynet dot be>]

Since most java bindings are JNI, and therefore written in plain old C, it's a bit of
an uphill battle to do things in CNI and C++.

And in the end, why drag yet another language into the fray? What useful stuff is
there that you can do with C++ that you can't with C?

At present JNI has a performance disadvantage compared to CNI, because JNI methods
need to get looked up in hashtables, while CNI can be linked statically. Now the
self-evident question: why not leave the option open to link JNI sources statically,
just as CNI sources?

That would speed up all JNI-dependent source trees, reduce their sizes (avoids
the need to link whole-archive) and avoid having to maintain bindings in two
different, mutually redundant languages.