That's very funny. I've done JNI integration with the JVM interfaces and the author of the headers did a beautiful job of staying architecture independent while providing binary-compatible COM interfaces for the dynamic bindings. In particular, there is a clean workaround of the differences in C++ compiler vtable approaches so that binary compatibility is preserved (and for C Language too).
I don't know if that also works on non-x86 platforms though, including x64, so what is done in C++ UNO might be necessary to avoid problems on different architectures and implementations of C/C++. Although I don't expect it to be useful for AOO, I have my eye on adaptations of the JVM interface header technique for making portable C/C++ use of COM binary interfaces in some other projects of mine. - Dennis -----Original Message----- From: Michael Stahl [mailto:[email protected]] Sent: Sunday, January 08, 2012 07:05 To: [email protected] Subject: Re: Java 7 and Apache OpenOffice [ ... ] now i have no idea why the heck OOo needs to know which JVM it's running with, but then again the C++ UNO stuff creates vtables out of whole cloth at runtime, so presumably the public JVM interfaces aren't good enough either :)
