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

Clarify pythonprepend and pythonappend features when used on overloaded methods/constructors

Browse source 
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@13954 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
William S Fulton 2012-12-10 19:45:04 +00:00
commit 1ac275790d
1 changed files with 32 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

32
Doc/Manual/Python.html
View file

@ -3386,7 +3386,39 @@ public:
</pre> </pre>
</div> </div>
<p>
Note that when the underlying C++ method is overloaded, there is only one proxy Python method
for multiple C++ methods. In this case, only one of parsed methods is examined
for the feature. You are better off specifying the feature without the argument list to ensure it will get used,
as it will then get attached to all the overloaded C++ methods. For example:
</p>
<div class="code">
<pre>
%module example
// Add python code to bar()
%pythonprepend Foo::bar %{
#do something before C++ call
%}
%pythonappend Foo::bar %{
#do something after C++ call
%}
class Foo {
public:
int bar(int x);
int bar();
}
</pre>
</div>
<p>
The same applies for overloaded constructors.
</p>
<H3><a name="Python_nn43"></a>34.6.3 Class extension with %extend</H3> <H3><a name="Python_nn43"></a>34.6.3 Class extension with %extend</H3>