shadow->proxy terminlogy update
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@10398 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
parent
41220df85b
commit
76eaea911b
21 changed files with 26 additions and 27 deletions
|
|
@ -145,10 +145,10 @@ Shape.setNshapes(13); // Set a static data member
|
|||
<h2>General Comments</h2>
|
||||
|
||||
<ul>
|
||||
<li>This high-level interface using shadow classes is not the only way to handle C++ code.
|
||||
<li>This high-level interface using proxy classes is not the only way to handle C++ code.
|
||||
A low level interface using c functions to access member variables and member functions is the alternative SWIG
|
||||
approach. This entails passing around the c pointer or c++ 'this' pointer and as such it is not difficult to crash the JVM.
|
||||
The abstraction of the underlying pointer by the java shadow classes far better fits the java programming paradigm.
|
||||
The abstraction of the underlying pointer by the java proxy classes far better fits the java programming paradigm.
|
||||
|
||||
<p>
|
||||
<li>SWIG *does* know how to properly perform upcasting of objects in an inheritance
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue