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

"Last updated" date removed from the files that had them as they aren't being maintained.

Browse source 
Consistent use of 'proxy' rather than 'shadow' throughout


git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@6211 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
William S Fulton 2004-09-02 20:27:16 +00:00
commit 959136284a
26 changed files with 43 additions and 93 deletions
Download patch file Download diff file Expand all files Collapse all files

9
SWIG/Doc/Manual/Python.html
View file

@ -1782,7 +1782,7 @@ These wrappers can be found in the low-level extension module (e.g., <tt>_exampl
</p>
<p>
Using these wrappers, SWIG generates a high-level Python proxy class like this (shown
Using these wrappers, SWIG generates a high-level Python proxy class (also known as a shadow class) like this (shown
for Python 2.2):
</p>
@ -3847,14 +3847,11 @@ if ((SWIG_ConvertPtr($input,(void **) &amp;$1, $descriptor(Foo *),
Although the pointer handling functions are primarily intended for
manipulating low-level pointers, both functions are fully aware of
Python shadow classes (described shortly). Specifically,
Python proxy classes. Specifically,
<tt>SWIG_ConvertPtr()</tt> will retrieve a pointer from any object
that has a <tt>this</tt> attribute. In addition,
<tt>SWIG_NewPointerObj()</tt> can automatically generate a shadow
<tt>SWIG_NewPointerObj()</tt> can automatically generate a proxy
class object (if applicable).
<hr>
<address>SWIG 1.3 - Last Modified : August 7, 2002</address>
</body>
</html>