Add documentation
This commit is contained in:
parent
325056453a
commit
6c41db3b8c
1 changed files with 13 additions and 3 deletions
|
|
@ -3983,9 +3983,19 @@ inclusion of the other fragments.
|
||||||
|
|
||||||
<li>
|
<li>
|
||||||
<p>
|
<p>
|
||||||
A typemap can also use more than one fragment, but since the
|
A typemap can also use more than one fragment with the same syntax:
|
||||||
syntax is different, you need to specify the dependent fragments in a comma separated
|
</p>
|
||||||
list. Consider:
|
<div class="code">
|
||||||
|
<pre>
|
||||||
|
%typemap("in", "header", fragment="frag1", fragment="frag2", fragment="frag3") "";
|
||||||
|
</pre>
|
||||||
|
</div>
|
||||||
|
<p>
|
||||||
|
<em>New in SWIG 4.1.</em>
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<p>An older syntax allows multiple fragments to be specified in a comma
|
||||||
|
separated list inside a single keyword argument. Consider:
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<div class="code">
|
<div class="code">
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue