> JNI lets you pass to C/C++. From there you are on your own.

Signature
Tony Morris
http://xdweb.net/~dibblego/
>JNI doesn't "pass to C/C++".
>It passes to "native" code.
>How that code was compiled is irrelevant.
>The fact that the primary use of JNI is to call out to native code that has
>been compiled using C/C++ is also irrelevant.
That is not quite true. JNI passes using C/C++ calling conventions. If
the language you are passing to does not use C/C++ conventions, you
need a bit a C/C++ glue or need to warn the language to generate C
style calls, e.g. Pascal which pushes parms in the opposite order to
C.

Signature
Canadian Mind Products, Roedy Green.
Coaching, problem solving, economical contract programming.
See http://mindprod.com/jgloss/jgloss.html for The Java Glossary.
Roedy Green - 24 Jul 2004 06:07 GMT
>That is not quite true. JNI passes using C/C++ calling conventions. If
>the language you are passing to does not use C/C++ conventions, you
>need a bit a C/C++ glue or need to warn the language to generate C
>style calls, e.g. Pascal which pushes parms in the opposite order to
>C.
the other thing to consider is the headers for the JNI library are
provided only in C/C++ form. If you wanted to access them from
Pascal, for example, you would have to write your own equivalent of
Javah.

Signature
Canadian Mind Products, Roedy Green.
Coaching, problem solving, economical contract programming.
See http://mindprod.com/jgloss/jgloss.html for The Java Glossary.