Small update to documentation in Typemaps.html, to warn about use of local variables in typemaps for multiple types.
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@10221 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
parent
cc59a22121
commit
560b18eb3f
2 changed files with 25 additions and 0 deletions
|
|
@ -1617,6 +1617,27 @@ Some typemaps do not recognize local variables (or they may simply not
|
|||
apply). At this time, only typemaps that apply to argument conversion support this.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<b>Note:</b>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
When declaring a typemap for multiple types,
|
||||
each type must have its own local variable declaration.
|
||||
</p>
|
||||
|
||||
<div class="code">
|
||||
<pre>
|
||||
%typemap(in) const std::string *, std::string * (std::string temp) // NO!
|
||||
// only std::string * has a local variable
|
||||
// const std::string * does not (oops)
|
||||
....
|
||||
|
||||
%typemap(in) const std::string * (std::string temp), std::string * (std::string temp) // Correct
|
||||
....
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
|
||||
<H3><a name="Typemaps_special_variables"></a>10.4.3 Special variables</H3>
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue