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

fix docs, path provided by Olly

Browse source 
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk/SWIG@9047 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
Marcelo Matus 2006-04-11 01:40:20 +00:00
commit 52cfa52b83
12 changed files with 17 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

4
Doc/Manual/Python.html
View file

@ -1021,7 +1021,7 @@ dereference the pointer from Python. Of course, that isn't much of a concern in
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 retreive it by casting the pointer object to a string:
always retrieve it by casting the pointer object to a string:
</p>
<div class="targetlang"><pre>
@ -4583,7 +4583,7 @@ class object (if applicable).
<p>
Using docstrings in Python code is becoming more and more important
and more tools are coming on the scene that take advantage of them,
everything from full-blown documentaiton generators to class browsers
everything from full-blown documentation generators to class browsers
and popup call-tips in Python-aware IDEs. Given the way that SWIG
generates the proxy code by default, your users will normally get
something like <tt>"function_name(*args)"</tt> in the popup calltip of