Re: Marking JNI funtions extern

[Tom Tromey <tromey at redhat dot com>]

>>>>> "Ranjit" == Ranjit Mathew <rmathew@gmail.com> writes:

Ranjit> However, most likely these were introduced to fit in
Ranjit> "__declspec(dllexport)" and "__stdcall" from the
Ranjit> Windoze DLL world

Yeah, I agree with your analysis.

Ranjit> If we really want "extern" in our declarations (why?),
Ranjit> we should modify the JNIEXPORT definition for POSIXy
Ranjit> systems appropriately.

I think there's no reason to bother.

BTW, Mark, I agree it would be great if kaffe started using the
Classpath jni.h.  There's no point in having different versions of
this file.  (Ideally in Classpath we'd get rid of the "jni.h.in" hack,
and in libgcj we'd pull some code into jni_md.h so that we can also be
completely in sync.)

Tom