diff options
Diffstat (limited to 'Doc/Manual/Java.html')
| -rw-r--r-- | Doc/Manual/Java.html | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/Doc/Manual/Java.html b/Doc/Manual/Java.html index 3b24c5ba8..03e3c9124 100644 --- a/Doc/Manual/Java.html +++ b/Doc/Manual/Java.html @@ -9068,6 +9068,11 @@ Here the default typemaps work for <tt>int</tt> and <tt>char *</tt>. </p> <p> +Note that if you're wanting to effectively <b>replace</b> the JNI code generated for a C/C++ function then you'll need to use <tt>%ignore</tt> as well +to tell SWIG not to automatically generate a JNI wrapper for it. +</p> + +<p> In summary the <tt>%native</tt> directive is telling SWIG to generate the Java code to access the JNI C code, but not the JNI C function itself. This directive is only really useful if you want to mix your own hand crafted JNI code and the SWIG generated code into one Java class or package. </p> @@ -9100,7 +9105,7 @@ This method normally calls the C++ destructor or <tt>free()</tt> for C code. <p> The generated code can be debugged using both a Java debugger and a C++ debugger using the usual debugging techniques. Breakpoints can be set in either Java or C++ code and so both can be debugged simultaneously. -Most debuggers do not understand both Java and C++, with one noteable exception of Sun Studio, +Most debuggers do not understand both Java and C++, with one notable exception of Sun Studio, where it is possible to step from Java code into a JNI method within one environment. </p> |