fix SWIG naming convention
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@11663 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
parent
1be8bd5d8e
commit
3932d02a2a
23 changed files with 43 additions and 43 deletions
|
|
@ -1137,7 +1137,7 @@ simply represented as opaque values using an especial python container object:
|
|||
|
||||
<div class="targetlang"><pre>
|
||||
>>> print f
|
||||
<Swig Object at _08a71808_p_FILE>
|
||||
<Swig Object of type 'FILE *' at 0xb7d6f470>
|
||||
</pre></div>
|
||||
|
||||
<p>
|
||||
|
|
@ -1147,7 +1147,7 @@ dereference the pointer from Python. Of course, that isn't much of a concern in
|
|||
</p>
|
||||
|
||||
<p>
|
||||
In older versions of Swig (1.3.22 or older), pointers were represented
|
||||
In older versions of SWIG (1.3.22 or older), pointers were represented
|
||||
using a plain string object. If you have an old package that still
|
||||
requires that representation, or you just feel nostalgic, you can
|
||||
always retrieve it by casting the pointer object to a string:
|
||||
|
|
@ -1171,7 +1171,7 @@ integer:
|
|||
|
||||
<p>
|
||||
However, the inverse operation is not possible, i.e., you can't build
|
||||
a Swig pointer object from a raw integer value.
|
||||
a SWIG pointer object from a raw integer value.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue