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

clarification of what can go in the code segment of typemaps and when the preprocessor is used on typemap code

Browse source 
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@9581 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
William S Fulton 2006-11-24 23:08:36 +00:00
commit 4ddb9006c8
1 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
SWIG/Doc/Manual/Typemaps.html
View file

@ -700,8 +700,9 @@ case of multi-argument typemaps. In addition, each type pattern can be parameter
variables (parms). The purpose of these variables will be explained shortly. variables (parms). The purpose of these variables will be explained shortly.
</p> </p>
<p><em>code</em> specifies the C code used in the typemap. It can take any one of the following <p><em>code</em> specifies the code used in the typemap.
forms: Usually this is C/C++ code, but in the strongly typed target languages, such as Java and C#, this can contain target language code for certain typemaps.
It can take any one of the following forms:
</p> </p>
<div class="diagram"> <div class="diagram">
@ -713,6 +714,7 @@ code : { ... }
</div> </div>
<p> <p>
Note that the preprocessor will expand code within the {} delimiters, but not in the last two styles of delimiters.
Here are some examples of valid typemap specifications: Here are some examples of valid typemap specifications:
</p> </p>