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

New section numbering adding in Android chapter

Browse source 
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@12869 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
William S Fulton 2011-12-10 16:53:04 +00:00
commit d005a2cc3f
25 changed files with 783 additions and 757 deletions
Download patch file Download diff file Expand all files Collapse all files

24
Doc/Manual/Typemaps.html
View file

@ -73,6 +73,7 @@
<li><a href="#Typemaps_nn43">Typemaps for multiple target languages</a>
<li><a href="#Typemaps_optimal">Optimal code generation when returning by value</a>
<li><a href="#Typemaps_multi_argument_typemaps">Multi-argument typemaps</a>
<li><a href="#Typemaps_warnings">Typemap warnings</a>
<li><a href="#Typemaps_fragments">Typemap fragments</a>
<ul>
<li><a href="#Typemaps_fragment_type_specialization">Fragment type specialization</a>
@ -3599,13 +3600,14 @@ the arguments to make them consecutive will need to be written.
<H2><a name="Typemaps_warnings"></a>10.10 Typemap warnings</H2>
<p>
Warnings can be added to typemaps so that SWIG generates a warning message whenever the typemap is used.
See the information in the <a href="Warnings.html#Warnings_nn5">issuing warnings</a> section.
</p>
<H2><a name="Typemaps_fragments"></a>10.10 Typemap fragments</H2>
<H2><a name="Typemaps_fragments"></a>10.11 Typemap fragments</H2>
<p>
@ -3854,7 +3856,7 @@ fragment usage unless a desire to really get to grips
with some powerful but tricky macro and fragment usage that is used in parts of the SWIG typemap library.
</p>
<H3><a name="Typemaps_fragment_type_specialization"></a>10.10.1 Fragment type specialization</H3>
<H3><a name="Typemaps_fragment_type_specialization"></a>10.11.1 Fragment type specialization</H3>
<p>
@ -3887,7 +3889,7 @@ struct A {
</pre>
</div>
<H3><a name="Typemaps_automatic_specialization"></a>10.10.2 Fragments and automatic typemap specialization</H3>
<H3><a name="Typemaps_automatic_specialization"></a>10.11.2 Fragments and automatic typemap specialization</H3>
<p>
@ -3933,7 +3935,7 @@ The interested (or very brave) reader can take a look at the fragments.swg file
</p>
<H2><a name="Typemaps_runtime_type_checker"></a>10.11 The run-time type checker</H2>
<H2><a name="Typemaps_runtime_type_checker"></a>10.12 The run-time type checker</H2>
<p>
@ -3959,7 +3961,7 @@ language modules.</li>
<li>Modules can be unloaded from the type system.</li>
</ul>
<H3><a name="Typemaps_nn45"></a>10.11.1 Implementation</H3>
<H3><a name="Typemaps_nn45"></a>10.12.1 Implementation</H3>
<p>
@ -4145,7 +4147,7 @@ structures rather than creating new ones. These <tt>swig_module_info</tt>
structures are chained together in a circularly linked list.
</p>
<H3><a name="Typemaps_runtime_type_checker_usage"></a>10.11.2 Usage</H3>
<H3><a name="Typemaps_runtime_type_checker_usage"></a>10.12.2 Usage</H3>
<p>This section covers how to use these functions from typemaps. To learn how to
@ -4239,7 +4241,7 @@ probably just look at the output of SWIG to get a better sense for how types are
managed.
</p>
<H2><a name="Typemaps_overloading"></a>10.12 Typemaps and overloading</H2>
<H2><a name="Typemaps_overloading"></a>10.13 Typemaps and overloading</H2>
<p>
@ -4550,7 +4552,7 @@ Subsequent "in" typemaps would then perform more extensive type-checking.
</li>
</ul>
<H2><a name="Typemaps_nn48"></a>10.13 More about <tt>%apply</tt> and <tt>%clear</tt></H2>
<H2><a name="Typemaps_nn48"></a>10.14 More about <tt>%apply</tt> and <tt>%clear</tt></H2>
<p>
@ -4636,7 +4638,7 @@ example:
</div>
<H2><a name="Typemaps_nn47"></a>10.14 Passing data between typemaps</H2>
<H2><a name="Typemaps_nn47"></a>10.15 Passing data between typemaps</H2>
<p>
@ -4673,7 +4675,7 @@ sure that the typemaps sharing information have exactly the same types and names
</p>
<H2><a name="Typemaps_nn52"></a>10.15 C++ "this" pointer</H2>
<H2><a name="Typemaps_nn52"></a>10.16 C++ "this" pointer</H2>
<p>
@ -4733,7 +4735,7 @@ will also match the typemap. One work around is to create an interface file tha
the method, but gives the argument a name other than <tt>self</tt>.
</p>
<H2><a name="Typemaps_nn51"></a>10.16 Where to go for more information?</H2>
<H2><a name="Typemaps_nn51"></a>10.17 Where to go for more information?</H2>
<p>