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
|
|
@ -159,7 +159,7 @@ $example::Shapes_nshapes = 13; # Set a static data member
|
|||
<h2>General Comments</h2>
|
||||
|
||||
<ul>
|
||||
<li>This low-level interface is not the only way to handle C++ code. Shadow classes
|
||||
<li>This low-level interface is not the only way to handle C++ code. Proxy classes
|
||||
provide a much higher-level interface.
|
||||
|
||||
<p>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
use Inline SWIG => <<"END_CODE", SWIG_ARGS => '-c++ -shadow', CC => 'g++', LD=>'g++';
|
||||
use Inline SWIG => <<"END_CODE", SWIG_ARGS => '-c++ -proxy', CC => 'g++', LD=>'g++';
|
||||
class Foo {
|
||||
public:
|
||||
int meaning() { return 42; };
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# file: runme.pl
|
||||
|
||||
# This file illustrates the manipulation of C++ references in Perl.
|
||||
# This uses the low-level interface. Shadow classes work differently.
|
||||
# This uses the low-level interface. Proxy classes work differently.
|
||||
|
||||
use example;
|
||||
|
||||
|
|
|
|||
|
|
@ -108,7 +108,7 @@ approach would be to write a helper function like this:
|
|||
</blockquote>
|
||||
|
||||
<p>
|
||||
<li>If you use shadow classes and are careful, the SWIG generated wrappers can automatically
|
||||
<li>If you use proxy classes and are careful, the SWIG generated wrappers can automatically
|
||||
clean up the result of return-by-reference when the scripting variable goes out of scope.
|
||||
|
||||
<p>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue