jyapayne/swig
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

note about constants added and fix link

Browse source 
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@9857 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
William S Fulton 2007-06-25 21:32:54 +00:00
commit 36a33af3f6
1 changed files with 9 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

10
Doc/Manual/Java.html
View file

@ -888,8 +888,16 @@ public interface exampleConstants {
Note: declarations declared as <tt>const</tt> are wrapped as read-only variables and Note: declarations declared as <tt>const</tt> are wrapped as read-only variables and
will be accessed using a getter as described in the previous section. They will be accessed using a getter as described in the previous section. They
are not wrapped as constants. are not wrapped as constants.
The exception to this rule are static const integral values defined within a class/struct, where they are wrapped as constants, eg:.
</p> </p>
<div class="code"><pre>
struct Maths {
static const int FIVE = 5;
};
</pre></div>
<p> <p>
<b>Compatibility Note:</b> In SWIG-1.3.19 and earlier releases, the constants were generated into the module class and the constants interface didn't exist. <b>Compatibility Note:</b> In SWIG-1.3.19 and earlier releases, the constants were generated into the module class and the constants interface didn't exist.
Backwards compatibility is maintained as the module class implements the constants interface (even though some consider this type of interface implementation to be bad practice): Backwards compatibility is maintained as the module class implements the constants interface (even though some consider this type of interface implementation to be bad practice):
@ -2118,7 +2126,7 @@ This approach leads to minimal JNI code which makes for better performance as JN
SWIG favours generating Java code over JNI code as Java code is compiled into byte code and avoids the costly string operations needed in JNI code. SWIG favours generating Java code over JNI code as Java code is compiled into byte code and avoids the costly string operations needed in JNI code.
This approach has a downside though as the proxy class might get collected before the native method has completed. This approach has a downside though as the proxy class might get collected before the native method has completed.
You might notice above that there is an additional parameters with a underscore postfix, eg <tt>jarg1_</tt>. You might notice above that there is an additional parameters with a underscore postfix, eg <tt>jarg1_</tt>.
These are added in order to prevent <a href="java_pgcpp">premature garbage collection when marshalling proxy classes</a>. These are added in order to prevent <a href="#java_pgcpp">premature garbage collection when marshalling proxy classes</a>.
</p> </p>
<p> <p>