diff options
| author | William S Fulton <wsf@fultondesigns.co.uk> | 2015-12-22 07:54:57 +0000 |
|---|---|---|
| committer | William S Fulton <wsf@fultondesigns.co.uk> | 2015-12-30 22:22:32 +0000 |
| commit | 8288ac15a030b851c18dee2cf5e4e5769f0bc024 (patch) | |
| tree | cd16459ad1cbc3b94dd5a3869dfbab94a70f68d1 | |
| parent | abe42bbb162396b4440c096b33b2bd98514af84e (diff) | |
| download | swig-8288ac15a030b851c18dee2cf5e4e5769f0bc024.tar.gz | |
Correct links in html documentation using new version of makechap.py
Corrects position of heading text within A and H1, H2, ... elements.
41 files changed, 1262 insertions, 1262 deletions
diff --git a/Doc/Manual/Allegrocl.html b/Doc/Manual/Allegrocl.html index 8295bad1c..e76d67e4c 100644 --- a/Doc/Manual/Allegrocl.html +++ b/Doc/Manual/Allegrocl.html @@ -8,7 +8,7 @@ <body bgcolor="#ffffff"> -<H1><a name="Allegrocl"></a>18 SWIG and Allegro Common Lisp</H1> +<H1><a name="Allegrocl">18 SWIG and Allegro Common Lisp</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -135,10 +135,10 @@ be unhappy to see some enterprising folk use this work to add to it. </p> -<H2><a name="Allegrocl_nn2"></a>18.1 Basics</H2> +<H2><a name="Allegrocl_nn2">18.1 Basics</a></H2> -<H3><a name="Allegrocl_nn3"></a>18.1.1 Running SWIG</H3> +<H3><a name="Allegrocl_nn3">18.1.1 Running SWIG</a></H3> <p> @@ -360,7 +360,7 @@ need to link in the Allegro shared library. The library you create from the C++ wrapper will be what you then load into Allegro CL. </p> -<H3><a name="Allegrocl_nn4"></a>18.1.2 Command Line Options</H3> +<H3><a name="Allegrocl_nn4">18.1.2 Command Line Options</a></H3> <p> @@ -396,7 +396,7 @@ See <a href="#Allegrocl_nn47">Section 17.5 Identifier converter functions</a> for more details. </p> -<H3><a name="Allegrocl_nn5"></a>18.1.3 Inserting user code into generated files</H3> +<H3><a name="Allegrocl_nn5">18.1.3 Inserting user code into generated files</a></H3> <p> @@ -436,7 +436,7 @@ Note that the block <tt>%{ ... %}</tt> is effectively a shortcut for </p> -<H2><a name="Allegrocl_nn6"></a>18.2 Wrapping Overview</H2> +<H2><a name="Allegrocl_nn6">18.2 Wrapping Overview</a></H2> <p> @@ -446,7 +446,7 @@ New users to SWIG are encouraged to read interested in generating an interface to C++. </p> -<H3><a name="Allegrocl_nn7"></a>18.2.1 Function Wrapping</H3> +<H3><a name="Allegrocl_nn7">18.2.1 Function Wrapping</a></H3> <p> @@ -499,7 +499,7 @@ interested in generating an interface to C++. </pre> </div> -<H3><a name="Allegrocl_nn8"></a>18.2.2 Foreign Wrappers</H3> +<H3><a name="Allegrocl_nn8">18.2.2 Foreign Wrappers</a></H3> <p> @@ -512,7 +512,7 @@ interested in generating an interface to C++. typemap. </p> -<H3><a name="Allegrocl_nn9"></a>18.2.3 FFI Wrappers</H3> +<H3><a name="Allegrocl_nn9">18.2.3 FFI Wrappers</a></H3> <p> @@ -593,7 +593,7 @@ char *xxx(); ff:def-foreign-call's. </p> -<H3><a name="Allegrocl_nn10"></a>18.2.4 Non-overloaded Defuns</H3> +<H3><a name="Allegrocl_nn10">18.2.4 Non-overloaded Defuns</a></H3> <p> @@ -606,7 +606,7 @@ char *xxx(); this function can be manipulated via the <tt>lout</tt> typemap. </p> -<H3><a name="Allegrocl_nn11"></a>18.2.5 Overloaded Defuns</H3> +<H3><a name="Allegrocl_nn11">18.2.5 Overloaded Defuns</a></H3> <p> @@ -622,7 +622,7 @@ char *xxx(); can be manipulated via the <tt>lout</tt> typemap. </p> -<H3><a name="Allegrocl_nn12"></a>18.2.6 What about constant and variable access?</H3> +<H3><a name="Allegrocl_nn12">18.2.6 What about constant and variable access?</a></H3> <p> @@ -635,7 +635,7 @@ char *xxx(); into the foreign module. </p> -<H3><a name="Allegrocl_nn13"></a>18.2.7 Object Wrapping</H3> +<H3><a name="Allegrocl_nn13">18.2.7 Object Wrapping</a></H3> <p> @@ -657,7 +657,7 @@ char *xxx(); foreign function interface. </p> -<H2><a name="Allegrocl_nn14"></a>18.3 Wrapping Details</H2> +<H2><a name="Allegrocl_nn14">18.3 Wrapping Details</a></H2> <p> @@ -665,7 +665,7 @@ char *xxx(); translated into lisp. </p> -<H3><a name="Allegrocl_nn15"></a>18.3.1 Namespaces</H3> +<H3><a name="Allegrocl_nn15">18.3.1 Namespaces</a></H3> <p> @@ -742,7 +742,7 @@ namespace car { function such as <tt>(car '(1 2 3)</tt>. </p> -<H3><a name="Allegrocl_nn16"></a>18.3.2 Constants</H3> +<H3><a name="Allegrocl_nn16">18.3.2 Constants</a></H3> @@ -803,7 +803,7 @@ namespace car { not use the <tt>-nocwrap</tt> command-line option. </p> -<H3><a name="Allegrocl_nn17"></a>18.3.3 Variables</H3> +<H3><a name="Allegrocl_nn17">18.3.3 Variables</a></H3> <p> @@ -881,7 +881,7 @@ globalvar> (globalvar.nnn::glob_float) </pre> </div> -<H3><a name="Allegrocl_nn18"></a>18.3.4 Enumerations</H3> +<H3><a name="Allegrocl_nn18">18.3.4 Enumerations</a></H3> <p> @@ -957,7 +957,7 @@ EXPORT const int ACL_ENUM___FOO3__SWIG_0 = FOO3; </pre> </div> -<H3><a name="Allegrocl_nn19"></a>18.3.5 Arrays</H3> +<H3><a name="Allegrocl_nn19">18.3.5 Arrays</a></H3> <p> @@ -1105,10 +1105,10 @@ namespace BAR { </pre> </div> -<H3><a name="Allegrocl_nn20"></a>18.3.6 Classes and Structs and Unions (oh my!)</H3> +<H3><a name="Allegrocl_nn20">18.3.6 Classes and Structs and Unions (oh my!)</a></H3> -<H4><a name="Allegrocl_nn21"></a>18.3.6.1 CLOS wrapping of</H4> +<H4><a name="Allegrocl_nn21">18.3.6.1 CLOS wrapping of</a></H4> <p> @@ -1123,7 +1123,7 @@ namespace BAR { integer values. </p> -<H4><a name="Allegrocl_nn22"></a>18.3.6.2 CLOS Inheritance</H4> +<H4><a name="Allegrocl_nn22">18.3.6.2 CLOS Inheritance</a></H4> <p> @@ -1136,7 +1136,7 @@ namespace BAR { parameter. </p> -<H4><a name="Allegrocl_nn23"></a>18.3.6.3 Member fields and functions</H4> +<H4><a name="Allegrocl_nn23">18.3.6.3 Member fields and functions</a></H4> <p> @@ -1152,7 +1152,7 @@ namespace BAR { the interface does nothing for <tt>friend</tt> directives, </p> -<H4><a name="Allegrocl_nn24"></a>18.3.6.4 Why not directly access C++ classes using foreign types?</H4> +<H4><a name="Allegrocl_nn24">18.3.6.4 Why not directly access C++ classes using foreign types?</a></H4> <p> @@ -1170,11 +1170,11 @@ namespace BAR { use the more robust wrapper functions. </p> -<H3><a name="Allegrocl_nn25"></a>18.3.7 Templates</H3> +<H3><a name="Allegrocl_nn25">18.3.7 Templates</a></H3> -<H4><a name="Allegrocl_nn26"></a>18.3.7.1 Generating wrapper code for templates</H4> +<H4><a name="Allegrocl_nn26">18.3.7.1 Generating wrapper code for templates</a></H4> <p> @@ -1187,7 +1187,7 @@ namespace BAR { directive. </p> -<H4><a name="Allegrocl_nn27"></a>18.3.7.2 Implicit Template instantiation</H4> +<H4><a name="Allegrocl_nn27">18.3.7.2 Implicit Template instantiation</a></H4> <p> @@ -1197,7 +1197,7 @@ namespace BAR { class schema. </p> -<H3><a name="Allegrocl_nn28"></a>18.3.8 Typedef, Templates, and Synonym Types</H3> +<H3><a name="Allegrocl_nn28">18.3.8 Typedef, Templates, and Synonym Types</a></H3> <p> @@ -1277,7 +1277,7 @@ synonym> </pre> </div> -<H4><a name="Allegrocl_nn29"></a>18.3.8.1 Choosing a primary type</H4> +<H4><a name="Allegrocl_nn29">18.3.8.1 Choosing a primary type</a></H4> <p> @@ -1298,7 +1298,7 @@ synonym> </li> </ul> -<H3><a name="Allegrocl_nn30"></a>18.3.9 Function overloading/Parameter defaulting</H3> +<H3><a name="Allegrocl_nn30">18.3.9 Function overloading/Parameter defaulting</a></H3> <p> @@ -1461,7 +1461,7 @@ overload> </pre> </div> -<H3><a name="Allegrocl_nn31"></a>18.3.10 Operator wrapping and Operator overloading</H3> +<H3><a name="Allegrocl_nn31">18.3.10 Operator wrapping and Operator overloading</a></H3> <p> @@ -1607,7 +1607,7 @@ opoverload> </pre> </div> -<H3><a name="Allegrocl_nn32"></a>18.3.11 Varargs</H3> +<H3><a name="Allegrocl_nn32">18.3.11 Varargs</a></H3> <p> @@ -1628,7 +1628,7 @@ opoverload> with other ways such functions can be wrapped. </p> -<H3><a name="Allegrocl_nn33"></a>18.3.12 C++ Exceptions</H3> +<H3><a name="Allegrocl_nn33">18.3.12 C++ Exceptions</a></H3> <p> @@ -1640,7 +1640,7 @@ opoverload> implemented. </p> -<H3><a name="Allegrocl_nn34"></a>18.3.13 Pass by value, pass by reference</H3> +<H3><a name="Allegrocl_nn34">18.3.13 Pass by value, pass by reference</a></H3> <p> @@ -1652,7 +1652,7 @@ opoverload> newly defined types. </p> -<H2><a name="Allegrocl_nn35"></a>18.4 Typemaps</H2> +<H2><a name="Allegrocl_nn35">18.4 Typemaps</a></H2> <p> @@ -1663,7 +1663,7 @@ opoverload> on <a href="Typemaps.html#Typemaps">Typemaps</a> for more information. </p> -<H3><a name="Allegrocl_nn36"></a>18.4.1 Code Generation in the C++ Wrapper</H3> +<H3><a name="Allegrocl_nn36">18.4.1 Code Generation in the C++ Wrapper</a></H3> @@ -1693,7 +1693,7 @@ return-val wrapper-name(parm0, parm1, ..., parmN) </pre> </div> -<H4><a name="Allegrocl_nn37"></a>18.4.1.1 IN Typemap</H4> +<H4><a name="Allegrocl_nn37">18.4.1.1 IN Typemap</a></H4> <p> @@ -1728,7 +1728,7 @@ return-val wrapper-name(parm0, parm1, ..., parmN) </pre> </div> -<H4><a name="Allegrocl_nn38"></a>18.4.1.2 OUT Typemap</H4> +<H4><a name="Allegrocl_nn38">18.4.1.2 OUT Typemap</a></H4> <p> @@ -1752,7 +1752,7 @@ return-val wrapper-name(parm0, parm1, ..., parmN) </pre> </div> -<H4><a name="Allegrocl_nn39"></a>18.4.1.3 CTYPE Typemap</H4> +<H4><a name="Allegrocl_nn39">18.4.1.3 CTYPE Typemap</a></H4> <p> @@ -1784,7 +1784,7 @@ return-val wrapper-name(parm0, parm1, ..., parmN) these <a href="Typemaps.html#Typemaps_nn25">common typemaps</a> here. </p> -<H3><a name="Allegrocl_nn40"></a>18.4.2 Code generation in Lisp wrappers</H3> +<H3><a name="Allegrocl_nn40">18.4.2 Code generation in Lisp wrappers</a></H3> <p> @@ -1803,7 +1803,7 @@ return-val wrapper-name(parm0, parm1, ..., parmN) <a href="#Allegrocl_nn15">16.3.1 Namespaces</a> for details. </p> -<H4><a name="Allegrocl_nn41"></a>18.4.2.1 LIN Typemap</H4> +<H4><a name="Allegrocl_nn41">18.4.2.1 LIN Typemap</a></H4> <p> @@ -1846,7 +1846,7 @@ return-val wrapper-name(parm0, parm1, ..., parmN) </pre> </div> -<H4><a name="Allegrocl_nn42"></a>18.4.2.2 LOUT Typemap</H4> +<H4><a name="Allegrocl_nn42">18.4.2.2 LOUT Typemap</a></H4> <p> @@ -1889,7 +1889,7 @@ return-val wrapper-name(parm0, parm1, ..., parmN) </pre> </div> -<H4><a name="Allegrocl_nn43"></a>18.4.2.3 FFITYPE Typemap</H4> +<H4><a name="Allegrocl_nn43">18.4.2.3 FFITYPE Typemap</a></H4> @@ -1939,7 +1939,7 @@ return-val wrapper-name(parm0, parm1, ..., parmN) </pre> </div> -<H4><a name="Allegrocl_nn44"></a>18.4.2.4 LISPTYPE Typemap</H4> +<H4><a name="Allegrocl_nn44">18.4.2.4 LISPTYPE Typemap</a></H4> <p> @@ -1959,7 +1959,7 @@ return-val wrapper-name(parm0, parm1, ..., parmN) </pre> </div> -<H4><a name="Allegrocl_nn45"></a>18.4.2.5 LISPCLASS Typemap</H4> +<H4><a name="Allegrocl_nn45">18.4.2.5 LISPCLASS Typemap</a></H4> <p> @@ -1983,7 +1983,7 @@ return-val wrapper-name(parm0, parm1, ..., parmN) </pre> </div> -<H3><a name="Allegrocl_nn46"></a>18.4.3 Modifying SWIG behavior using typemaps</H3> +<H3><a name="Allegrocl_nn46">18.4.3 Modifying SWIG behavior using typemaps</a></H3> <p> @@ -2017,10 +2017,10 @@ return-val wrapper-name(parm0, parm1, ..., parmN) </pre> </div> -<H2><a name="Allegrocl_nn47"></a>18.5 Identifier Converter functions</H2> +<H2><a name="Allegrocl_nn47">18.5 Identifier Converter functions</a></H2> -<H3><a name="Allegrocl_nn48"></a>18.5.1 Creating symbols in the lisp environment</H3> +<H3><a name="Allegrocl_nn48">18.5.1 Creating symbols in the lisp environment</a></H3> <p> @@ -2041,11 +2041,11 @@ return-val wrapper-name(parm0, parm1, ..., parmN) of arguments. </p> -<H3><a name="Allegrocl_nn49"></a>18.5.2 Existing identifier-converter functions</H3> +<H3><a name="Allegrocl_nn49">18.5.2 Existing identifier-converter functions</a></H3> <p>Two basic identifier routines have been defined. -<H4><a name="Allegrocl_nn50"></a>18.5.2.1 identifier-convert-null</H4> +<H4><a name="Allegrocl_nn50">18.5.2.1 identifier-convert-null</a></H4> <p> @@ -2054,7 +2054,7 @@ return-val wrapper-name(parm0, parm1, ..., parmN) strings, from which a symbol will be created. </p> -<H4><a name="Allegrocl_nn51"></a>18.5.2.2 identifier-convert-lispify</H4> +<H4><a name="Allegrocl_nn51">18.5.2.2 identifier-convert-lispify</a></H4> <p> @@ -2063,7 +2063,7 @@ return-val wrapper-name(parm0, parm1, ..., parmN) same symbol transformations. </p> -<H4><a name="Allegrocl_nn52"></a>18.5.2.3 Default identifier to symbol conversions</H4> +<H4><a name="Allegrocl_nn52">18.5.2.3 Default identifier to symbol conversions</a></H4> <p> @@ -2072,7 +2072,7 @@ return-val wrapper-name(parm0, parm1, ..., parmN) default naming conventions. </p> -<H3><a name="Allegrocl_nn53"></a>18.5.3 Defining your own identifier-converter</H3> +<H3><a name="Allegrocl_nn53">18.5.3 Defining your own identifier-converter</a></H3> <p> @@ -2128,7 +2128,7 @@ indicating the number of arguments passed to the routine indicated by this identifier. </p> -<H3><a name="Allegrocl_nn54"></a>18.5.4 Instructing SWIG to use a particular identifier-converter</H3> +<H3><a name="Allegrocl_nn54">18.5.4 Instructing SWIG to use a particular identifier-converter</a></H3> <p> diff --git a/Doc/Manual/Android.html b/Doc/Manual/Android.html index c90da21b4..2973f1de1 100644 --- a/Doc/Manual/Android.html +++ b/Doc/Manual/Android.html @@ -5,7 +5,7 @@ <link rel="stylesheet" type="text/css" href="style.css"> </head> <body bgcolor="#FFFFFF"> -<H1><a name="Android"></a>19 SWIG and Android</H1> +<H1><a name="Android">19 SWIG and Android</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -30,7 +30,7 @@ This chapter describes SWIG's support of Android. -<H2><a name="Android_overview"></a>19.1 Overview</H2> +<H2><a name="Android_overview">19.1 Overview</a></H2> <p> @@ -40,10 +40,10 @@ Everything in the <a href="Java.html#Java">Java chapter</a> applies to generatin This chapter contains a few Android specific notes and examples. </p> -<H2><a name="Android_examples"></a>19.2 Android examples</H2> +<H2><a name="Android_examples">19.2 Android examples</a></H2> -<H3><a name="Android_examples_intro"></a>19.2.1 Examples introduction</H3> +<H3><a name="Android_examples_intro">19.2.1 Examples introduction</a></H3> <p> @@ -76,7 +76,7 @@ $ android list targets The following examples are shipped with SWIG under the Examples/android directory and include a Makefile to build and install each example. </p> -<H3><a name="Android_example_simple"></a>19.2.2 Simple C example</H3> +<H3><a name="Android_example_simple">19.2.2 Simple C example</a></H3> <p> @@ -398,7 +398,7 @@ Run the app again and this time you will see the output pictured below, showing <center><img src="android-simple.png" alt="Android screenshot of SwigSimple example"></center> -<H3><a name="Android_example_class"></a>19.2.3 C++ class example</H3> +<H3><a name="Android_example_class">19.2.3 C++ class example</a></H3> <p> @@ -746,7 +746,7 @@ Run the app to see the result of calling the C++ code from Java: <center><img src="android-class.png" alt="Android screenshot of SwigClass example"></center> -<H3><a name="Android_examples_other"></a>19.2.4 Other examples</H3> +<H3><a name="Android_examples_other">19.2.4 Other examples</a></H3> <p> @@ -758,7 +758,7 @@ Note that the 'extend' example is demonstrates the directors feature. Normally C++ exception handling and the STL is not available by default in the version of g++ shipped with Android, but this example turns these features on as described in the next section. </p> -<H2><a name="Android_stl"></a>19.3 C++ STL</H2> +<H2><a name="Android_stl">19.3 C++ STL</a></H2> <p> diff --git a/Doc/Manual/Arguments.html b/Doc/Manual/Arguments.html index 3b7713686..21da790b7 100644 --- a/Doc/Manual/Arguments.html +++ b/Doc/Manual/Arguments.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Arguments"></a>10 Argument Handling</H1> +<H1><a name="Arguments">10 Argument Handling</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -42,7 +42,7 @@ return multiple values through the arguments of a function. This chapter describes some of the techniques for doing this. </p> -<H2><a name="Arguments_nn2"></a>10.1 The typemaps.i library</H2> +<H2><a name="Arguments_nn2">10.1 The typemaps.i library</a></H2> <p> @@ -50,7 +50,7 @@ This section describes the <tt>typemaps.i</tt> library file--commonly used to change certain properties of argument conversion. </p> -<H3><a name="Arguments_nn3"></a>10.1.1 Introduction</H3> +<H3><a name="Arguments_nn3">10.1.1 Introduction</a></H3> <p> @@ -194,7 +194,7 @@ else. To clear a typemap, the <tt>%clear</tt> directive should be used. For e </pre> </div> -<H3><a name="Arguments_nn4"></a>10.1.2 Input parameters</H3> +<H3><a name="Arguments_nn4">10.1.2 Input parameters</a></H3> <p> @@ -247,7 +247,7 @@ When the function is used in the scripting language interpreter, it will work li result = add(3,4) </pre></div> -<H3><a name="Arguments_nn5"></a>10.1.3 Output parameters</H3> +<H3><a name="Arguments_nn5">10.1.3 Output parameters</a></H3> <p> @@ -314,7 +314,7 @@ iresult, dresult = foo(3.5, 2) </pre> </div> -<H3><a name="Arguments_nn6"></a>10.1.4 Input/Output parameters</H3> +<H3><a name="Arguments_nn6">10.1.4 Input/Output parameters</a></H3> <p> @@ -379,7 +379,7 @@ rather than directly overwriting the value of the original input object. SWIG. Backwards compatibility is preserved, but deprecated. </p> -<H3><a name="Arguments_nn7"></a>10.1.5 Using different names</H3> +<H3><a name="Arguments_nn7">10.1.5 Using different names</a></H3> <p> @@ -413,7 +413,7 @@ Typemap declarations are lexically scoped so a typemap takes effect from the poi file or a matching <tt>%clear</tt> declaration. </p> -<H2><a name="Arguments_nn8"></a>10.2 Applying constraints to input values</H2> +<H2><a name="Arguments_nn8">10.2 Applying constraints to input values</a></H2> <p> @@ -423,7 +423,7 @@ insure that a value is positive, or that a pointer is non-NULL. This can be accomplished including the <tt>constraints.i</tt> library file. </p> -<H3><a name="Arguments_nn9"></a>10.2.1 Simple constraint example</H3> +<H3><a name="Arguments_nn9">10.2.1 Simple constraint example</a></H3> <p> @@ -449,7 +449,7 @@ the arguments violate the constraint condition, a scripting language exception will be raised. As a result, it is possible to catch bad values, prevent mysterious program crashes and so on.</p> -<H3><a name="Arguments_nn10"></a>10.2.2 Constraint methods</H3> +<H3><a name="Arguments_nn10">10.2.2 Constraint methods</a></H3> <p> @@ -465,7 +465,7 @@ NONNULL Non-NULL pointer (pointers only). </pre></div> -<H3><a name="Arguments_nn11"></a>10.2.3 Applying constraints to new datatypes</H3> +<H3><a name="Arguments_nn11">10.2.3 Applying constraints to new datatypes</a></H3> <p> diff --git a/Doc/Manual/CCache.html b/Doc/Manual/CCache.html index 0ee94c172..88922a8ea 100644 --- a/Doc/Manual/CCache.html +++ b/Doc/Manual/CCache.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="CCache"></a>17 Using SWIG with ccache - ccache-swig(1) manpage</H1> +<H1><a name="CCache">17 Using SWIG with ccache - ccache-swig(1) manpage</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -34,7 +34,7 @@ <p> -<H2><a name="CCache_nn2"></a>17.1 NAME</H2> +<H2><a name="CCache_nn2">17.1 NAME</a></H2> <p> @@ -42,7 +42,7 @@ ccache-swig - a fast compiler cache <p> -<H2><a name="CCache_nn3"></a>17.2 SYNOPSIS</H2> +<H2><a name="CCache_nn3">17.2 SYNOPSIS</a></H2> <p> @@ -52,7 +52,7 @@ ccache-swig <compiler> [COMPILER OPTIONS] <p> <compiler> [COMPILER OPTIONS] <p> -<H2><a name="CCache_nn4"></a>17.3 DESCRIPTION</H2> +<H2><a name="CCache_nn4">17.3 DESCRIPTION</a></H2> <p> @@ -61,7 +61,7 @@ by caching previous compiles and detecting when the same compile is being done again. ccache-swig is ccache plus support for SWIG. ccache and ccache-swig are used interchangeably in this document. <p> -<H2><a name="CCache_nn5"></a>17.4 OPTIONS SUMMARY</H2> +<H2><a name="CCache_nn5">17.4 OPTIONS SUMMARY</a></H2> <p> @@ -81,7 +81,7 @@ Here is a summary of the options to ccache-swig. </pre> <p> -<H2><a name="CCache_nn6"></a>17.5 OPTIONS</H2> +<H2><a name="CCache_nn6">17.5 OPTIONS</a></H2> <p> @@ -123,7 +123,7 @@ rounded down to the nearest multiple of 16 kilobytes. <p> </dl> <p> -<H2><a name="CCache_nn7"></a>17.6 INSTALLATION</H2> +<H2><a name="CCache_nn7">17.6 INSTALLATION</a></H2> <p> @@ -155,7 +155,7 @@ This will work as long as /usr/local/bin comes before the path to gcc Note! Do not use a hard link, use a symbolic link. A hardlink will cause "interesting" problems. <p> -<H2><a name="CCache_nn8"></a>17.7 EXTRA OPTIONS</H2> +<H2><a name="CCache_nn8">17.7 EXTRA OPTIONS</a></H2> <p> @@ -175,7 +175,7 @@ file). By using --ccache-skip you can force an option to not be treated as an input file name and instead be passed along to the compiler as a command line option. <p> -<H2><a name="CCache_nn9"></a>17.8 ENVIRONMENT VARIABLES</H2> +<H2><a name="CCache_nn9">17.8 ENVIRONMENT VARIABLES</a></H2> <p> @@ -314,7 +314,7 @@ the use of '#pragma SWIG'. <p> </dl> <p> -<H2><a name="CCache_nn10"></a>17.9 CACHE SIZE MANAGEMENT</H2> +<H2><a name="CCache_nn10">17.9 CACHE SIZE MANAGEMENT</a></H2> <p> @@ -327,7 +327,7 @@ When these limits are reached ccache will reduce the cache to 20% below the numbers you specified in order to avoid doing the cache clean operation too often. <p> -<H2><a name="CCache_nn11"></a>17.10 CACHE COMPRESSION</H2> +<H2><a name="CCache_nn11">17.10 CACHE COMPRESSION</a></H2> <p> @@ -338,7 +338,7 @@ performance slowdown, it significantly increases the number of files that fit in the cache. You can turn off compression setting the CCACHE_NOCOMPRESS environment variable. <p> -<H2><a name="CCache_nn12"></a>17.11 HOW IT WORKS</H2> +<H2><a name="CCache_nn12">17.11 HOW IT WORKS</a></H2> <p> @@ -363,7 +363,7 @@ compiler output that you would get without the cache. If you ever discover a case where ccache changes the output of your compiler then please let me know. <p> -<H2><a name="CCache_nn13"></a>17.12 USING CCACHE WITH DISTCC</H2> +<H2><a name="CCache_nn13">17.12 USING CCACHE WITH DISTCC</a></H2> <p> @@ -377,7 +377,7 @@ option. You just need to set the environment variable CCACHE_PREFIX to 'distcc' and ccache will prefix the command line used with the compiler with the command 'distcc'. <p> -<H2><a name="CCache_nn14"></a>17.13 SHARING A CACHE</H2> +<H2><a name="CCache_nn14">17.13 SHARING A CACHE</a></H2> <p> @@ -406,7 +406,7 @@ following conditions need to be met: versions of ccache that do not support compression. </ul> <p> -<H2><a name="CCache_nn15"></a>17.14 HISTORY</H2> +<H2><a name="CCache_nn15">17.14 HISTORY</a></H2> <p> @@ -422,7 +422,7 @@ I wrote ccache because I wanted to get a bit more speed out of a compiler cache and I wanted to remove some of the limitations of the shell-script version. <p> -<H2><a name="CCache_nn16"></a>17.15 DIFFERENCES FROM COMPILERCACHE</H2> +<H2><a name="CCache_nn16">17.15 DIFFERENCES FROM COMPILERCACHE</a></H2> <p> @@ -440,7 +440,7 @@ are: <li> ccache avoids a double call to cpp on a cache miss </ul> <p> -<H2><a name="CCache_nn17"></a>17.16 CREDITS</H2> +<H2><a name="CCache_nn17">17.16 CREDITS</a></H2> <p> @@ -452,7 +452,7 @@ Thanks to the following people for their contributions to ccache <li> Paul Russell for many suggestions and the debian packaging </ul> <p> -<H2><a name="CCache_nn18"></a>17.17 AUTHOR</H2> +<H2><a name="CCache_nn18">17.17 AUTHOR</a></H2> <p> diff --git a/Doc/Manual/CPlusPlus11.html b/Doc/Manual/CPlusPlus11.html index b7e1d638c..021ad418d 100644 --- a/Doc/Manual/CPlusPlus11.html +++ b/Doc/Manual/CPlusPlus11.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="CPlusPlus11"></a>7 SWIG and C++11</H1> +<H1><a name="CPlusPlus11">7 SWIG and C++11</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -61,7 +61,7 @@ -<H2><a name="CPlusPlus11_introduction"></a>7.1 Introduction</H2> +<H2><a name="CPlusPlus11_introduction">7.1 Introduction</a></H2> <p>This chapter gives you a brief overview about the SWIG @@ -76,10 +76,10 @@ users are welcome to help by adapting the existing container interface files and as a patch for inclusion in future versions of SWIG. </p> -<H2><a name="CPlusPlus11_core_language_changes"></a>7.2 Core language changes</H2> +<H2><a name="CPlusPlus11_core_language_changes">7.2 Core language changes</a></H2> -<H3><a name="CPlusPlus11_rvalue_reference_and_move_semantics"></a>7.2.1 Rvalue reference and move semantics</H3> +<H3><a name="CPlusPlus11_rvalue_reference_and_move_semantics">7.2.1 Rvalue reference and move semantics</a></H3> <p> @@ -121,7 +121,7 @@ example.i:18: Warning 503: Can't wrap 'operator =' unless renamed to a valid ide </div> -<H3><a name="CPlusPlus11_generalized_constant_expressions"></a>7.2.2 Generalized constant expressions</H3> +<H3><a name="CPlusPlus11_generalized_constant_expressions">7.2.2 Generalized constant expressions</a></H3> <p>SWIG parses and identifies the keyword <tt>constexpr</tt>, but cannot fully utilise it. @@ -138,7 +138,7 @@ constexpr int YYY = XXX() + 100; When either of these is used from a target language, a runtime call is made to obtain the underlying constant. </p> -<H3><a name="CPlusPlus11_extern_template"></a>7.2.3 Extern template</H3> +<H3><a name="CPlusPlus11_extern_template">7.2.3 Extern template</a></H3> <p>SWIG correctly parses the keywords <tt>extern template</tt>. @@ -151,7 +151,7 @@ extern template class std::vector<int>; // C++11 explicit instantiation su %template(VectorInt) std::vector<int>; // SWIG instantiation </pre></div> -<H3><a name="CPlusPlus11_initializer_lists"></a>7.2.4 Initializer lists</H3> +<H3><a name="CPlusPlus11_initializer_lists">7.2.4 Initializer lists</a></H3> <p> @@ -283,7 +283,7 @@ Note that the default typemap for <tt>std::initializer_list</tt> does nothing bu and hence any user supplied typemaps will override it and suppress the warning. </p> -<H3><a name="CPlusPlus11_uniform_initialization"></a>7.2.5 Uniform initialization</H3> +<H3><a name="CPlusPlus11_uniform_initialization">7.2.5 Uniform initialization</a></H3> <p>The curly brackets {} for member initialization are fully @@ -316,7 +316,7 @@ AltStruct var2{2, 4.3}; // calls the constructor 142.15 </pre></div> -<H3><a name="CPlusPlus11_type_inference"></a>7.2.6 Type inference</H3> +<H3><a name="CPlusPlus11_type_inference">7.2.6 Type inference</a></H3> <p>SWIG supports <tt>decltype()</tt> with some limitations. Single @@ -333,13 +333,13 @@ int i; int j; decltype(i+j) k; // syntax error </pre></div> -<H3><a name="CPlusPlus11_range_based_for_loop"></a>7.2.7 Range-based for-loop</H3> +<H3><a name="CPlusPlus11_range_based_for_loop">7.2.7 Range-based for-loop</a></H3> <p>This feature is part of the implementation block only. SWIG ignores it.</p> -<H3><a name="CPlusPlus11_lambda_functions_and_expressions"></a>7.2.8 Lambda functions and expressions</H3> +<H3><a name="CPlusPlus11_lambda_functions_and_expressions">7.2.8 Lambda functions and expressions</a></H3> <p>SWIG correctly parses most of the Lambda functions syntax. For example:</p> @@ -365,7 +365,7 @@ auto six = [](int x, int y) { return x+y; }(4, 2); Better support should be available in a later release. </p> -<H3><a name="CPlusPlus11_alternate_function_syntax"></a>7.2.9 Alternate function syntax</H3> +<H3><a name="CPlusPlus11_alternate_function_syntax">7.2.9 Alternate function syntax</a></H3> <p>SWIG fully supports the new definition of functions. For example:</p> @@ -400,7 +400,7 @@ auto SomeStruct::FuncName(int x, int y) -> int { auto square(float a, float b) -> decltype(a); </pre></div> -<H3><a name="CPlusPlus11_object_construction_improvement"></a>7.2.10 Object construction improvement</H3> +<H3><a name="CPlusPlus11_object_construction_improvement">7.2.10 Object construction improvement</a></H3> <p> @@ -463,7 +463,7 @@ public: }; </pre></div> -<H3><a name="CPlusPlus11_explicit_overrides_final"></a>7.2.11 Explicit overrides and final</H3> +<H3><a name="CPlusPlus11_explicit_overrides_final">7.2.11 Explicit overrides and final</a></H3> <p> @@ -487,12 +487,12 @@ struct DerivedStruct : BaseStruct { </pre></div> -<H3><a name="CPlusPlus11_null_pointer_constant"></a>7.2.12 Null pointer constant</H3> +<H3><a name="CPlusPlus11_null_pointer_constant">7.2.12 Null pointer constant</a></H3> <p>The <tt>nullptr</tt> constant is mostly unimportant in wrappers. In the few places it has an effect, it is treated like <tt>NULL</tt>.</p> -<H3><a name="CPlusPlus11_strongly_typed_enumerations"></a>7.2.13 Strongly typed enumerations</H3> +<H3><a name="CPlusPlus11_strongly_typed_enumerations">7.2.13 Strongly typed enumerations</a></H3> <p>SWIG supports strongly typed enumerations and parses the new <tt>enum class</tt> syntax and forward declarator for the enums, such as:</p> @@ -548,7 +548,7 @@ The equivalent in Java is: System.out.println(Color.RainbowColors.Red.swigValue() + " " + Color.WarmColors.Red.swigValue() + " " + Color.PrimeColors.Red.swigValue()); </pre></div> -<H3><a name="CPlusPlus11_double_angle_brackets"></a>7.2.14 Double angle brackets</H3> +<H3><a name="CPlusPlus11_double_angle_brackets">7.2.14 Double angle brackets</a></H3> <p>SWIG correctly parses the symbols >> as closing the @@ -559,7 +559,7 @@ shift operator >> otherwise.</p> std::vector<std::vector<int>> myIntTable; </pre></div> -<H3><a name="CPlusPlus11_explicit_conversion_operators"></a>7.2.15 Explicit conversion operators</H3> +<H3><a name="CPlusPlus11_explicit_conversion_operators">7.2.15 Explicit conversion operators</a></H3> <p>SWIG correctly parses the keyword <tt>explicit</tt> for operators in addition to constructors now. @@ -602,7 +602,7 @@ Conversion operators either with or without <tt>explicit</tt> need renaming to a them available as a normal proxy method. </p> -<H3><a name="CPlusPlus11_alias_templates"></a>7.2.16 Alias templates</H3> +<H3><a name="CPlusPlus11_alias_templates">7.2.16 Alias templates</a></H3> <p> @@ -656,7 +656,7 @@ example.i:17: Warning 341: The 'using' keyword in type aliasing is not fully sup typedef void (*PFD)(double); // The old style </pre></div> -<H3><a name="CPlusPlus11_unrestricted_unions"></a>7.2.17 Unrestricted unions</H3> +<H3><a name="CPlusPlus11_unrestricted_unions">7.2.17 Unrestricted unions</a></H3> <p>SWIG fully supports any type inside a union even if it does not @@ -682,7 +682,7 @@ union P { } p1; </pre></div> -<H3><a name="CPlusPlus11_variadic_templates"></a>7.2.18 Variadic templates</H3> +<H3><a name="CPlusPlus11_variadic_templates">7.2.18 Variadic templates</a></H3> <p>SWIG supports the variadic templates syntax (inside the <> @@ -717,7 +717,7 @@ const int SIZE = sizeof...(ClassName<int, int>); In the above example <tt>SIZE</tt> is of course wrapped as a constant. </p> -<H3><a name="CPlusPlus11_new_string_literals"></a>7.2.19 New string literals</H3> +<H3><a name="CPlusPlus11_new_string_literals">7.2.19 New string literals</a></H3> <p>SWIG supports wide string and Unicode string constants and raw string literals.</p> @@ -747,7 +747,7 @@ Note: There is a bug currently where SWIG's preprocessor incorrectly parses an o inside raw string literals. </p> -<H3><a name="CPlusPlus11_user_defined_literals"></a>7.2.20 User-defined literals</H3> +<H3><a name="CPlusPlus11_user_defined_literals">7.2.20 User-defined literals</a></H3> <p> @@ -814,7 +814,7 @@ OutputType var2 = 1234_suffix; OutputType var3 = 3.1416_suffix; </pre></div> -<H3><a name="CPlusPlus11_thread_local_storage"></a>7.2.21 Thread-local storage</H3> +<H3><a name="CPlusPlus11_thread_local_storage">7.2.21 Thread-local storage</a></H3> <p>SWIG correctly parses the <tt>thread_local</tt> keyword. For example, variables @@ -834,7 +834,7 @@ A variable will be thread local if accessed from different threads from the targ same way that it will be thread local if accessed from C++ code. </p> -<H3><a name="CPlusPlus11_defaulted_deleted"></a>7.2.22 Explicitly defaulted functions and deleted functions</H3> +<H3><a name="CPlusPlus11_defaulted_deleted">7.2.22 Explicitly defaulted functions and deleted functions</a></H3> <p>SWIG handles explicitly defaulted functions, that is, <tt>= default</tt> added to a function declaration. Deleted definitions, which are also called deleted functions, have <tt>= delete</tt> added to the function declaration. @@ -872,12 +872,12 @@ This is a C++ compile time check and SWIG does not make any attempt to detect if so in this case it is entirely possible to pass an int instead of a double to <tt>f</tt> from Java, Python etc. </p> -<H3><a name="CPlusPlus11_type_long_long_int"></a>7.2.23 Type long long int</H3> +<H3><a name="CPlusPlus11_type_long_long_int">7.2.23 Type long long int</a></H3> <p>SWIG correctly parses and uses the new <tt>long long</tt> type already introduced in C99 some time ago.</p> -<H3><a name="CPlusPlus11_static_assertions"></a>7.2.24 Static assertions</H3> +<H3><a name="CPlusPlus11_static_assertions">7.2.24 Static assertions</a></H3> <p> @@ -892,7 +892,7 @@ struct Check { }; </pre></div> -<H3><a name="CPlusPlus11_sizeof"></a>7.2.25 Allow sizeof to work on members of classes without an explicit object</H3> +<H3><a name="CPlusPlus11_sizeof">7.2.25 Allow sizeof to work on members of classes without an explicit object</a></H3> <p> @@ -913,7 +913,7 @@ const int SIZE = sizeof(A::member); // does not work with C++03. Okay with C++11 8 </pre></div> -<H3><a name="CPlusPlus11_noexcept"></a>7.2.26 Exception specifications and noexcept</H3> +<H3><a name="CPlusPlus11_noexcept">7.2.26 Exception specifications and noexcept</a></H3> <p> @@ -929,7 +929,7 @@ int noex2(int) noexcept(true); int noex3(int, bool) noexcept(false); </pre></div> -<H3><a name="CPlusPlus11_alignment"></a>7.2.27 Control and query object alignment</H3> +<H3><a name="CPlusPlus11_alignment">7.2.27 Control and query object alignment</a></H3> <p> @@ -961,7 +961,7 @@ Use the preprocessor to work around this for now: </pre></div> -<H3><a name="CPlusPlus11_attributes"></a>7.2.28 Attributes</H3> +<H3><a name="CPlusPlus11_attributes">7.2.28 Attributes</a></H3> <p> @@ -974,10 +974,10 @@ int [[attr1]] i [[attr2, attr3]]; [[noreturn, nothrow]] void f [[noreturn]] (); </pre></div> -<H2><a name="CPlusPlus11_standard_library_changes"></a>7.3 Standard library changes</H2> +<H2><a name="CPlusPlus11_standard_library_changes">7.3 Standard library changes</a></H2> -<H3><a name="CPlusPlus11_threading_facilities"></a>7.3.1 Threading facilities</H3> +<H3><a name="CPlusPlus11_threading_facilities">7.3.1 Threading facilities</a></H3> <p>SWIG does not currently wrap or use any of the new threading @@ -985,7 +985,7 @@ classes introduced (thread, mutex, locks, condition variables, task). The main r SWIG target languages offer their own threading facilities so there is limited use for them. </p> -<H3><a name="CPlusPlus11_tuple_types"></a>7.3.2 Tuple types</H3> +<H3><a name="CPlusPlus11_tuple_types">7.3.2 Tuple types</a></H3> <p> @@ -993,7 +993,7 @@ SWIG does not provide library files for the new tuple types yet. Variadic template support requires further work to provide substantial tuple wrappers. </p> -<H3><a name="CPlusPlus11_hash_tables"></a>7.3.3 Hash tables</H3> +<H3><a name="CPlusPlus11_hash_tables">7.3.3 Hash tables</a></H3> <p> @@ -1001,14 +1001,14 @@ The new hash tables in the STL are <tt>unordered_set</tt>, <tt>unordered_multise These are not available in SWIG, but in principle should be easily implemented by adapting the current STL containers. </p> -<H3><a name="CPlusPlus11_regular_expressions"></a>7.3.4 Regular expressions</H3> +<H3><a name="CPlusPlus11_regular_expressions">7.3.4 Regular expressions</a></H3> <p> While SWIG could provide wrappers for the new C++11 regular expressions classes, there is little need as the target languages have their own regular expression facilities. </p> -<H3><a name="CPlusPlus11_general_purpose_smart_pointers"></a>7.3.5 General-purpose smart pointers</H3> +<H3><a name="CPlusPlus11_general_purpose_smart_pointers">7.3.5 General-purpose smart pointers</a></H3> <p> @@ -1017,12 +1017,12 @@ Please see the <a href="Library.html#Library_std_shared_ptr">shared_ptr smart po There is no special smart pointer handling available for <tt>std::weak_ptr</tt> and <tt>std::unique_ptr</tt> yet. </p> -<H3><a name="CPlusPlus11_extensible_random_number_facility"></a>7.3.6 Extensible random number facility</H3> +<H3><a name="CPlusPlus11_extensible_random_number_facility">7.3.6 Extensible random number facility</a></H3> <p>This feature extends and standardizes the standard library only and does not effect the C++ language nor SWIG.</p> -<H3><a name="CPlusPlus11_wrapper_reference"></a>7.3.7 Wrapper reference</H3> +<H3><a name="CPlusPlus11_wrapper_reference">7.3.7 Wrapper reference</a></H3> <p> @@ -1033,7 +1033,7 @@ Users would need to write their own typemaps if wrapper references are being use </p> -<H3><a name="CPlusPlus11_polymorphous_wrappers_for_function_objects"></a>7.3.8 Polymorphous wrappers for function objects</H3> +<H3><a name="CPlusPlus11_polymorphous_wrappers_for_function_objects">7.3.8 Polymorphous wrappers for function objects</a></H3> <p> @@ -1064,7 +1064,7 @@ t = Test() b = t(1,2) # invoke C++ function object </pre></div> -<H3><a name="CPlusPlus11_type_traits_for_metaprogramming"></a>7.3.9 Type traits for metaprogramming</H3> +<H3><a name="CPlusPlus11_type_traits_for_metaprogramming">7.3.9 Type traits for metaprogramming</a></H3> <p>The type_traits functions to support C++ metaprogramming is useful at compile time and is aimed specifically at C++ development:</p> @@ -1114,7 +1114,7 @@ Then the appropriate algorithm can be called for the subset of types given by th 2 </pre></div> -<H3><a name="CPlusPlus11_uniform_method_for_computing_return_type_of_function_objects"></a>7.3.10 Uniform method for computing return type of function objects</H3> +<H3><a name="CPlusPlus11_uniform_method_for_computing_return_type_of_function_objects">7.3.10 Uniform method for computing return type of function objects</a></H3> <p> diff --git a/Doc/Manual/CSharp.html b/Doc/Manual/CSharp.html index 76590d1cc..e6829aabc 100644 --- a/Doc/Manual/CSharp.html +++ b/Doc/Manual/CSharp.html @@ -5,7 +5,7 @@ <link rel="stylesheet" type="text/css" href="style.css"> </head> <body bgcolor="#FFFFFF"> -<H1><a name="CSharp"></a>20 SWIG and C#</H1> +<H1><a name="CSharp">20 SWIG and C#</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -53,7 +53,7 @@ -<H2><a name="CSharp_introduction"></a>20.1 Introduction</H2> +<H2><a name="CSharp_introduction">20.1 Introduction</a></H2> <p> @@ -73,7 +73,7 @@ The <a href="http://msdn.microsoft.com">Microsoft Developer Network (MSDN)</a> h Monodoc, available from the Mono project, has a very useful section titled <a href="http://www.mono-project.com/docs/advanced/pinvoke/">Interop with native libraries</a>. </p> -<H3><a name="CSharp_introduction_swig2_compatibility"></a>20.1.1 SWIG 2 Compatibility</H3> +<H3><a name="CSharp_introduction_swig2_compatibility">20.1.1 SWIG 2 Compatibility</a></H3> <p> @@ -81,7 +81,7 @@ In order to minimize name collisions between names generated based on input to S </p> -<H3><a name="CSharp_commandline"></a>20.1.2 Additional command line options</H3> +<H3><a name="CSharp_commandline">20.1.2 Additional command line options</a></H3> <p> @@ -133,7 +133,7 @@ Note that the file extension (.cs) will not be automatically added and needs to Due to possible compiler limits it is not advisable to use <tt>-outfile</tt> for large projects. </p> -<H2><a name="CSharp_differences_java"></a>20.2 Differences to the Java module</H2> +<H2><a name="CSharp_differences_java">20.2 Differences to the Java module</a></H2> <p> @@ -546,7 +546,7 @@ Windows users can also get the examples working using a <a href="http://www.cygwin.com">Cygwin</a> or <a href="http://www.mingw.org">MinGW</a> environment for automatic configuration of the example makefiles. Any one of the three C# compilers (Portable.NET, Mono or Microsoft) can be detected from within a Cygwin or Mingw environment if installed in your path. -<H2><a name="CSharp_void_pointers"></a>20.3 Void pointers</H2> +<H2><a name="CSharp_void_pointers">20.3 Void pointers</a></H2> <p> @@ -564,7 +564,7 @@ void * f(void *v); </pre> </div> -<H2><a name="CSharp_arrays"></a>20.4 C# Arrays</H2> +<H2><a name="CSharp_arrays">20.4 C# Arrays</a></H2> <p> @@ -576,7 +576,7 @@ with one of the following three approaches; namely the SWIG C arrays library, P/ pinned arrays. </p> -<H3><a name="CSharp_arrays_swig_library"></a>20.4.1 The SWIG C arrays library</H3> +<H3><a name="CSharp_arrays_swig_library">20.4.1 The SWIG C arrays library</a></H3> <p> @@ -613,7 +613,7 @@ example.print_array(c.cast()); // Pass to C </div> -<H3><a name="CSharp_arrays_pinvoke_default_array_marshalling"></a>20.4.2 Managed arrays using P/Invoke default array marshalling</H3> +<H3><a name="CSharp_arrays_pinvoke_default_array_marshalling">20.4.2 Managed arrays using P/Invoke default array marshalling</a></H3> <p> @@ -740,7 +740,7 @@ and intermediary class method </div> -<H3><a name="CSharp_arrays_pinning"></a>20.4.3 Managed arrays using pinning</H3> +<H3><a name="CSharp_arrays_pinning">20.4.3 Managed arrays using pinning</a></H3> <p> @@ -835,7 +835,7 @@ public static extern void myArrayCopy(global::System.IntPtr jarg1, global::Syste -<H2><a name="CSharp_exceptions"></a>20.5 C# Exceptions</H2> +<H2><a name="CSharp_exceptions">20.5 C# Exceptions</a></H2> <p> @@ -932,7 +932,7 @@ set so should only be used when a C# exception is not created. </p> -<H3><a name="CSharp_exception_example_check_typemap"></a>20.5.1 C# exception example using "check" typemap</H3> +<H3><a name="CSharp_exception_example_check_typemap">20.5.1 C# exception example using "check" typemap</a></H3> <p> @@ -1114,7 +1114,7 @@ method and C# code does not handle pending exceptions via the canthrow attribute Actually it will issue this warning for any function beginning with <tt>SWIG_CSharpSetPendingException</tt>. </P> -<H3><a name="CSharp_exception_example_percent_exception"></a>20.5.2 C# exception example using %exception</H3> +<H3><a name="CSharp_exception_example_percent_exception">20.5.2 C# exception example using %exception</a></H3> <p> @@ -1180,7 +1180,7 @@ The managed code generated does check for the pending exception as mentioned ear </pre> </div> -<H3><a name="CSharp_exception_example_exception_specifications"></a>20.5.3 C# exception example using exception specifications</H3> +<H3><a name="CSharp_exception_example_exception_specifications">20.5.3 C# exception example using exception specifications</a></H3> <p> @@ -1237,7 +1237,7 @@ SWIGEXPORT void SWIGSTDCALL CSharp_evensonly(int jarg1) { Multiple catch handlers are generated should there be more than one exception specifications declared. </p> -<H3><a name="CSharp_custom_application_exception"></a>20.5.4 Custom C# ApplicationException example</H3> +<H3><a name="CSharp_custom_application_exception">20.5.4 Custom C# ApplicationException example</a></H3> <p> @@ -1371,7 +1371,7 @@ try { </pre> </div> -<H2><a name="CSharp_directors"></a>20.6 C# Directors</H2> +<H2><a name="CSharp_directors">20.6 C# Directors</a></H2> <p> @@ -1384,7 +1384,7 @@ The following sections provide information on the C# director implementation and However, the <a href="Java.html#Java_directors">Java directors</a> section should also be read in order to gain more insight into directors. </p> -<H3><a name="CSharp_directors_example"></a>20.6.1 Directors example</H3> +<H3><a name="CSharp_directors_example">20.6.1 Directors example</a></H3> <p> @@ -1505,7 +1505,7 @@ CSharpDerived - UIntMethod(123) </pre> </div> -<H3><a name="CSharp_directors_implementation"></a>20.6.2 Directors implementation</H3> +<H3><a name="CSharp_directors_implementation">20.6.2 Directors implementation</a></H3> <p> @@ -1688,7 +1688,7 @@ void SwigDirector_Base::BaseBoolMethod(Base const &b, bool flag) { </pre> </div> -<H3><a name="CSharp_director_caveats"></a>20.6.3 Director caveats</H3> +<H3><a name="CSharp_director_caveats">20.6.3 Director caveats</a></H3> <p> @@ -1736,7 +1736,7 @@ However, a call from C# to <tt>CSharpDefaults.DefaultMethod()</tt> will of cours should pass the call on to <tt>CSharpDefaults.DefaultMethod(int)</tt>using the C++ default value, as shown above. </p> -<H2><a name="CSharp_multiple_modules"></a>20.7 Multiple modules</H2> +<H2><a name="CSharp_multiple_modules">20.7 Multiple modules</a></H2> <p> @@ -1771,7 +1771,7 @@ the <tt>[System.ComponentModel.EditorBrowsable(System.ComponentModel.EditorBrows if you don't want users to easily stumble upon these so called 'internal workings' of the wrappers. </p> -<H2><a name="CSharp_typemap_examples"></a>20.8 C# Typemap examples</H2> +<H2><a name="CSharp_typemap_examples">20.8 C# Typemap examples</a></H2> This section includes a few examples of typemaps. For more examples, you @@ -1779,7 +1779,7 @@ might look at the files "<tt>csharp.swg</tt>" and "<tt>typemaps.i</tt>" in the SWIG library. -<H3><a name="CSharp_memory_management_member_variables"></a>20.8.1 Memory management when returning references to member variables</H3> +<H3><a name="CSharp_memory_management_member_variables">20.8.1 Memory management when returning references to member variables</a></H3> <p> @@ -1903,7 +1903,7 @@ public class Bike : global::System.IDisposable { Note the <tt>addReference</tt> call. </p> -<H3><a name="CSharp_memory_management_objects"></a>20.8.2 Memory management for objects passed to the C++ layer</H3> +<H3><a name="CSharp_memory_management_objects">20.8.2 Memory management for objects passed to the C++ layer</a></H3> <p> @@ -2022,7 +2022,7 @@ The 'cscode' typemap simply adds in the specified code into the C# proxy class. </div> -<H3><a name="CSharp_date_marshalling"></a>20.8.3 Date marshalling using the csin typemap and associated attributes</H3> +<H3><a name="CSharp_date_marshalling">20.8.3 Date marshalling using the csin typemap and associated attributes</a></H3> <p> @@ -2308,7 +2308,7 @@ public class example { </pre> </div> -<H3><a name="CSharp_date_properties"></a>20.8.4 A date example demonstrating marshalling of C# properties</H3> +<H3><a name="CSharp_date_properties">20.8.4 A date example demonstrating marshalling of C# properties</a></H3> <p> @@ -2408,7 +2408,7 @@ Some points to note: <li>The 'csin' typemap has 'pre', 'post' and 'cshin' attributes, and these are all ignored in the property set. The code in these attributes must instead be replicated within the 'csvarin' typemap. The line creating the <tt>temp$csinput</tt> variable is such an example; it is identical to what is in the 'pre' attribute. </ul> -<H3><a name="CSharp_date_pre_post_directors"></a>20.8.5 Date example demonstrating the 'pre' and 'post' typemap attributes for directors</H3> +<H3><a name="CSharp_date_pre_post_directors">20.8.5 Date example demonstrating the 'pre' and 'post' typemap attributes for directors</a></H3> <p> @@ -2470,7 +2470,7 @@ Pay special attention to the memory management issues, using these attributes. </p> -<H3><a name="CSharp_partial_classes"></a>20.8.6 Turning wrapped classes into partial classes</H3> +<H3><a name="CSharp_partial_classes">20.8.6 Turning wrapped classes into partial classes</a></H3> <p> @@ -2570,7 +2570,7 @@ demonstrating that the class contains methods calling both unmanaged code - <tt> The following example is an alternative approach to adding managed code to the generated proxy class. </p> -<H3><a name="CSharp_extending_proxy_class"></a>20.8.7 Extending proxy classes with additional C# code</H3> +<H3><a name="CSharp_extending_proxy_class">20.8.7 Extending proxy classes with additional C# code</a></H3> <p> @@ -2609,7 +2609,7 @@ public class ExtendMe : global::System.IDisposable { </pre> </div> -<H3><a name="CSharp_enum_underlying_type"></a>20.8.8 Underlying type for enums</H3> +<H3><a name="CSharp_enum_underlying_type">20.8.8 Underlying type for enums</a></H3> <P> diff --git a/Doc/Manual/Chicken.html b/Doc/Manual/Chicken.html index 82861c31c..88cff55a9 100644 --- a/Doc/Manual/Chicken.html +++ b/Doc/Manual/Chicken.html @@ -8,7 +8,7 @@ <body bgcolor="#ffffff"> -<H1><a name="Chicken"></a>21 SWIG and Chicken</H1> +<H1><a name="Chicken">21 SWIG and Chicken</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -72,7 +72,7 @@ </p> -<H2><a name="Chicken_nn2"></a>21.1 Preliminaries</H2> +<H2><a name="Chicken_nn2">21.1 Preliminaries</a></H2> <p> @@ -89,7 +89,7 @@ directory for the basic steps to run SWIG CHICKEN. </p> -<H3><a name="Chicken_nn3"></a>21.1.1 Running SWIG in C mode</H3> +<H3><a name="Chicken_nn3">21.1.1 Running SWIG in C mode</a></H3> <p> @@ -122,7 +122,7 @@ object files and linked into your project. </p> -<H3><a name="Chicken_nn4"></a>21.1.2 Running SWIG in C++ mode</H3> +<H3><a name="Chicken_nn4">21.1.2 Running SWIG in C++ mode</a></H3> <p> @@ -151,10 +151,10 @@ object files and linked into your project. </p> -<H2><a name="Chicken_nn5"></a>21.2 Code Generation</H2> +<H2><a name="Chicken_nn5">21.2 Code Generation</a></H2> -<H3><a name="Chicken_nn6"></a>21.2.1 Naming Conventions</H3> +<H3><a name="Chicken_nn6">21.2.1 Naming Conventions</a></H3> <p> @@ -170,7 +170,7 @@ <tt>%rename</tt> SWIG directive in the SWIG interface file. </p> -<H3><a name="Chicken_nn7"></a>21.2.2 Modules</H3> +<H3><a name="Chicken_nn7">21.2.2 Modules</a></H3> <p> @@ -192,7 +192,7 @@ (uses <i>modulename</i>))</code> CHICKEN Scheme form. </p> -<H3><a name="Chicken_nn8"></a>21.2.3 Constants and Variables</H3> +<H3><a name="Chicken_nn8">21.2.3 Constants and Variables</a></H3> <p> @@ -229,7 +229,7 @@ for info on how to apply the %feature. </p> -<H3><a name="Chicken_nn9"></a>21.2.4 Functions</H3> +<H3><a name="Chicken_nn9">21.2.4 Functions</a></H3> <p> @@ -248,7 +248,7 @@ parameters). The return values can then be accessed with <code>(call-with-values)</code>. </p> -<H3><a name="Chicken_nn10"></a>21.2.5 Exceptions</H3> +<H3><a name="Chicken_nn10">21.2.5 Exceptions</a></H3> <p>The SWIG chicken module has support for exceptions thrown from @@ -290,7 +290,7 @@ </pre></div> -<H2><a name="Chicken_nn11"></a>21.3 TinyCLOS</H2> +<H2><a name="Chicken_nn11">21.3 TinyCLOS</a></H2> <p> @@ -333,7 +333,7 @@ </p> -<H2><a name="Chicken_nn12"></a>21.4 Linkage</H2> +<H2><a name="Chicken_nn12">21.4 Linkage</a></H2> <p> @@ -354,7 +354,7 @@ </p> -<H3><a name="Chicken_nn13"></a>21.4.1 Static binary or shared library linked at compile time</H3> +<H3><a name="Chicken_nn13">21.4.1 Static binary or shared library linked at compile time</a></H3> <p>We can easily use csc to build a static binary.</p> @@ -395,7 +395,7 @@ in which case the test script does not need to be linked with example.so. The t be run with <tt>csi</tt>. </p> -<H3><a name="Chicken_nn14"></a>21.4.2 Building chicken extension libraries</H3> +<H3><a name="Chicken_nn14">21.4.2 Building chicken extension libraries</a></H3> <p>Building a shared library like in the above section only works if the library @@ -453,7 +453,7 @@ distributed and used by anyone, even if SWIG is not installed.</p> <p>See the <tt>Examples/chicken/egg</tt> directory in the SWIG source for an example that builds two eggs, one using the first method and one using the second method.</p> -<H3><a name="Chicken_nn15"></a>21.4.3 Linking multiple SWIG modules with TinyCLOS</H3> +<H3><a name="Chicken_nn15">21.4.3 Linking multiple SWIG modules with TinyCLOS</a></H3> <p>Linking together multiple modules that share type information using the <code>%import</code> @@ -477,7 +477,7 @@ with <code>(declare (uses ...))</code>. To create an extension library or an egg, just create a <tt>module_load.scm</tt> file that <code>(declare (uses ...))</code> all the modules.</p> -<H2><a name="Chicken_nn16"></a>21.5 Typemaps</H2> +<H2><a name="Chicken_nn16">21.5 Typemaps</a></H2> <p> @@ -486,7 +486,7 @@ all the modules.</p> <code>Lib/chicken/chicken.swg</code>. </p> -<H2><a name="Chicken_nn17"></a>21.6 Pointers</H2> +<H2><a name="Chicken_nn17">21.6 Pointers</a></H2> <p> @@ -519,7 +519,7 @@ all the modules.</p> type. flags is either zero or SWIG_POINTER_DISOWN (see below). </p> -<H3><a name="Chicken_collection"></a>21.6.1 Garbage collection</H3> +<H3><a name="Chicken_collection">21.6.1 Garbage collection</a></H3> <p>If the owner flag passed to <code>SWIG_NewPointerObj</code> is 1, <code>NewPointerObj</code> will add a @@ -550,7 +550,7 @@ all the modules.</p> must be called manually. </p> -<H2><a name="Chicken_nn18"></a>21.7 Unsupported features and known problems</H2> +<H2><a name="Chicken_nn18">21.7 Unsupported features and known problems</a></H2> <ul> @@ -560,7 +560,7 @@ all the modules.</p> <a href="SWIGPlus.html#SWIGPlus_default_args">%feature(compactdefaultargs)</a>.</li> </ul> -<H3><a name="Chicken_nn19"></a>21.7.1 TinyCLOS problems with Chicken version <= 1.92</H3> +<H3><a name="Chicken_nn19">21.7.1 TinyCLOS problems with Chicken version <= 1.92</a></H3> <p>In Chicken versions equal to or below 1.92, TinyCLOS has a limitation such that generic methods do not properly work on methods diff --git a/Doc/Manual/Contract.html b/Doc/Manual/Contract.html index 35bc874ef..660daf9fc 100644 --- a/Doc/Manual/Contract.html +++ b/Doc/Manual/Contract.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Contract"></a>13 Contracts</H1> +<H1><a name="Contract">13 Contracts</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -38,7 +38,7 @@ When one of the rules is violated by a script, a runtime exception is generated rather than having the program continue to execute. </p> -<H2><a name="Contract_nn2"></a>13.1 The %contract directive</H2> +<H2><a name="Contract_nn2">13.1 The %contract directive</a></H2> <p> @@ -94,7 +94,7 @@ RuntimeError: Contract violation: require: (arg1>=0) </pre> </div> -<H2><a name="Contract_nn3"></a>13.2 %contract and classes</H2> +<H2><a name="Contract_nn3">13.2 %contract and classes</a></H2> <p> @@ -173,7 +173,7 @@ specified for the derived class all must hold. In the above example, this means that both the arguments to <tt>Spam::bar</tt> must be positive. </p> -<H2><a name="Contract_nn4"></a>13.3 Constant aggregation and %aggregate_check</H2> +<H2><a name="Contract_nn4">13.3 Constant aggregation and %aggregate_check</a></H2> <p> @@ -262,7 +262,7 @@ Regrettably, there is no automatic way to perform similar checks with enums valu release. </p> -<H2><a name="Contract_nn5"></a>13.4 Notes</H2> +<H2><a name="Contract_nn5">13.4 Notes</a></H2> <p> diff --git a/Doc/Manual/Customization.html b/Doc/Manual/Customization.html index 8e26a7e8a..9ab0a6269 100644 --- a/Doc/Manual/Customization.html +++ b/Doc/Manual/Customization.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Customization"></a>12 Customization Features</H1> +<H1><a name="Customization">12 Customization Features</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -45,7 +45,7 @@ of exception handling is presented. Then, a more general-purpose customization mechanism known as "features" is described. </p> -<H2><a name="Customization_exception"></a>12.1 Exception handling with %exception</H2> +<H2><a name="Customization_exception">12.1 Exception handling with %exception</a></H2> <p> @@ -100,7 +100,7 @@ for exception handling. That directive is deprecated--<tt>%exception</tt> provides the same functionality, but is substantially more flexible. </p> -<H3><a name="Customization_nn3"></a>12.1.1 Handling exceptions in C code</H3> +<H3><a name="Customization_nn3">12.1.1 Handling exceptions in C code</a></H3> <p> @@ -166,7 +166,7 @@ Each target language has its own approach to creating a runtime error/exception and for Perl it is the <tt>croak</tt> method shown above. </p> -<H3><a name="Customization_nn4"></a>12.1.2 Exception handling with longjmp()</H3> +<H3><a name="Customization_nn4">12.1.2 Exception handling with longjmp()</a></H3> <p> @@ -240,7 +240,7 @@ Note: This implementation is only intended to illustrate the general idea. To m modify it to handle nested <tt>try</tt> declarations. </p> -<H3><a name="Customization_nn5"></a>12.1.3 Handling C++ exceptions</H3> +<H3><a name="Customization_nn5">12.1.3 Handling C++ exceptions</a></H3> <p> @@ -275,7 +275,7 @@ class OutOfMemory {}; </pre> </div> -<H3><a name="Customization_allowexcept"></a>12.1.4 Exception handlers for variables</H3> +<H3><a name="Customization_allowexcept">12.1.4 Exception handlers for variables</a></H3> <p> @@ -300,7 +300,7 @@ The <tt>%allowexception</tt> feature works like any other feature and so can be </pre> </div> -<H3><a name="Customization_nn6"></a>12.1.5 Defining different exception handlers</H3> +<H3><a name="Customization_nn6">12.1.5 Defining different exception handlers</a></H3> <p> @@ -437,7 +437,7 @@ declarations. However, it never really worked that well and the new %exception directive is much better. </p> -<H3><a name="Customization_exception_special_variables"></a>12.1.6 Special variables for %exception</H3> +<H3><a name="Customization_exception_special_variables">12.1.6 Special variables for %exception</a></H3> <p> @@ -540,7 +540,7 @@ Below shows the expansions for the 1st of the overloaded <tt>something</tt> wrap </pre></div> -<H3><a name="Customization_nn7"></a>12.1.7 Using The SWIG exception library</H3> +<H3><a name="Customization_nn7">12.1.7 Using The SWIG exception library</a></H3> <p> @@ -595,7 +595,7 @@ SWIG_NullReferenceError The <tt>SWIG_exception()</tt> function can also be used in typemaps. </p> -<H2><a name="Customization_ownership"></a>12.2 Object ownership and %newobject</H2> +<H2><a name="Customization_ownership">12.2 Object ownership and %newobject</a></H2> <p> @@ -752,7 +752,7 @@ char *strdup(const char *s); The results might not be what you expect. </p> -<H2><a name="Customization_features"></a>12.3 Features and the %feature directive</H2> +<H2><a name="Customization_features">12.3 Features and the %feature directive</a></H2> <p> @@ -834,7 +834,7 @@ The following are all equivalent: The syntax in the first variation will generate the <tt>{ }</tt> delimiters used whereas the other variations will not. </p> -<H3><a name="Customization_feature_attributes"></a>12.3.1 Feature attributes</H3> +<H3><a name="Customization_feature_attributes">12.3.1 Feature attributes</a></H3> <p> @@ -875,7 +875,7 @@ In the following example, <tt>MyExceptionClass</tt> is the name of the Java clas Further details can be obtained from the <a href="Java.html#Java_exception_handling">Java exception handling</a> section. </p> -<H3><a name="Customization_feature_flags"></a>12.3.2 Feature flags</H3> +<H3><a name="Customization_feature_flags">12.3.2 Feature flags</a></H3> <p> @@ -973,7 +973,7 @@ in the <tt>swig.swg</tt> Library file. The following shows the alternative synta The concept of clearing features is discussed next. </p> -<H3><a name="Customization_clearing_features"></a>12.3.3 Clearing features</H3> +<H3><a name="Customization_clearing_features">12.3.3 Clearing features</a></H3> <p> @@ -1066,7 +1066,7 @@ The three macros below show this for the "except" feature: </pre> </div> -<H3><a name="Customization_features_default_args"></a>12.3.4 Features and default arguments</H3> +<H3><a name="Customization_features_default_args">12.3.4 Features and default arguments</a></H3> <p> @@ -1141,7 +1141,7 @@ specifying or not specifying default arguments in a feature is not applicable as in SWIG-1.3.23 when the approach to wrapping methods with default arguments was changed. </p> -<H3><a name="Customization_features_example"></a>12.3.5 Feature example</H3> +<H3><a name="Customization_features_example">12.3.5 Feature example</a></H3> <p> diff --git a/Doc/Manual/D.html b/Doc/Manual/D.html index 984b81bb8..8007ccbb6 100644 --- a/Doc/Manual/D.html +++ b/Doc/Manual/D.html @@ -6,7 +6,7 @@ <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body bgcolor="#FFFFFF"> -<H1><a name="D"></a>22 SWIG and D</H1> +<H1><a name="D">22 SWIG and D</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -41,7 +41,7 @@ -<H2><a name="D_introduction"></a>22.1 Introduction</H2> +<H2><a name="D_introduction">22.1 Introduction</a></H2> <p>From the <a href="http://www.digitalmars.com/d/">D Programming Language</a> web site: <em>D is a systems programming language. Its focus is on combining the power and high performance of C and C++ with the programmer productivity of modern languages like Ruby and Python. [...] The D language is statically typed and compiles directly to machine code.</em> As such, it is not very surprising that D is able to directly <a href="http://www.digitalmars.com/d/1.0/interfaceToC.html">interface with C libraries</a>. Why would a SWIG module for D be needed then in the first place?</p> @@ -53,7 +53,7 @@ <p>To help addressing these issues, the SWIG C# module has been forked to support D. Is has evolved quite a lot since then, but there are still many similarities, so if you do not find what you are looking for on this page, it might be worth having a look at the chapter on <a href="CSharp.html#CSharp">C#</a> (and also on <a href="Java.html#Java">Java</a>, since the C# module was in turn forked from it).</p> -<H2><a name="D_command_line_invocation"></a>22.2 Command line invocation</H2> +<H2><a name="D_command_line_invocation">22.2 Command line invocation</a></H2> <p>To activate the D module, pass the <tt>-d</tt> option to SWIG at the command line. The same standard command line switches as with any other language module are available, plus the following D specific ones:</p> @@ -83,10 +83,10 @@ </dl> -<H2><a name="D_typemaps"></a>22.3 Typemaps</H2> +<H2><a name="D_typemaps">22.3 Typemaps</a></H2> -<H3><a name="D_typemap_name_comparison"></a>22.3.1 C# <-> D name comparison</H3> +<H3><a name="D_typemap_name_comparison">22.3.1 C# <-> D name comparison</a></H3> <p>If you already know the SWIG C# module, you might find the following name comparison table useful:</p> @@ -112,7 +112,7 @@ </pre></div> -<H3><a name="D_ctype_imtype_dtype"></a>22.3.2 ctype, imtype, dtype</H3> +<H3><a name="D_ctype_imtype_dtype">22.3.2 ctype, imtype, dtype</a></H3> <p>Mapping of types between the C/C++ library, the C/C++ library wrapper exposing the C functions, the D wrapper module importing these functions and the D proxy code.</p> @@ -120,7 +120,7 @@ <p>The <tt>ctype</tt> typemap is used to determine the types to use in the C wrapper functions. The types from the <tt>imtype</tt> typemap are used in the extern(C) declarations of these functions in the intermediary D module. The <tt>dtype</tt> typemap contains the D types used in the D proxy module/class.</p> -<H3><a name="D_in_out_directorin_direcetorout"></a>22.3.3 in, out, directorin, directorout</H3> +<H3><a name="D_in_out_directorin_direcetorout">22.3.3 in, out, directorin, directorout</a></H3> <p>Used for converting between the types for C/C++ and D when generating the code for the wrapper functions (on the C++ side).</p> @@ -130,7 +130,7 @@ <p>The <tt>directorin</tt> typemap is used to convert parameters to the type used in the D director callback function, its return value is processed by <tt>directorout</tt> (see below).</p> -<H3><a name="D_din_dout_ddirectorin_ddirectorout"></a>22.3.4 din, dout, ddirectorin, ddirectorout</H3> +<H3><a name="D_din_dout_ddirectorin_ddirectorout">22.3.4 din, dout, ddirectorin, ddirectorout</a></H3> <p>Typemaps for code generation in D proxy and type wrapper classes.</p> @@ -157,13 +157,13 @@ dtype DClass.method(dtype a)</pre></div> -<H3><a name="D_typecheck_typemaps"></a>22.3.5 typecheck typemaps</H3> +<H3><a name="D_typecheck_typemaps">22.3.5 typecheck typemaps</a></H3> <p>Because, unlike many scripting languages supported by SWIG, D does not need any dynamic dispatch helper to access an overloaded function, the purpose of these is merely to issue a warning for overloaded C++ functions that cannot be overloaded in D (as more than one C++ type maps to a single D type).</p> -<H3><a name="D_code_injection_typemaps"></a>22.3.6 Code injection typemaps</H3> +<H3><a name="D_code_injection_typemaps">22.3.6 Code injection typemaps</a></H3> <p>These typemaps are used for generating the skeleton of proxy classes for C++ types.</p> @@ -175,7 +175,7 @@ <p><a name="D_class_code_typemaps"></a><tt>dconstructor</tt>, <tt>ddestructor</tt>, <tt>ddispose</tt> and <tt>ddispose_derived</tt> are used to generate the class constructor, destructor and <tt>dispose()</tt> method, respectively. The auxiliary code for handling the pointer to the C++ object is stored in <tt>dbody</tt> and <tt>dbody_derived</tt>. You can override them for specific types.</p> -<H3><a name="D_special_variables"></a>22.3.7 Special variable macros</H3> +<H3><a name="D_special_variables">22.3.7 Special variable macros</a></H3> <p>The standard SWIG special variables are available for use within typemaps as described in the <a href="Typemaps.html#Typemaps">Typemaps documentation</a>, for example <tt>$1</tt>, <tt>$input</tt>, <tt>$result</tt> etc.</p> @@ -295,7 +295,7 @@ $importtype(AnotherInterface) </dl> -<H2><a name="D_features"></a>22.4 <tt>%feature</tt>s</H2> +<H2><a name="D_features">22.4 <tt>%feature</tt>s</a></H2> <p>The D module defines a number of directives which modify the <a href="Customization.html#Customization_features">SWIG features</a> set globally or for a specific declaration:</p> @@ -325,7 +325,7 @@ struct A { </dl> -<H2><a name="D_pragmas"></a>22.5 Pragmas</H2> +<H2><a name="D_pragmas">22.5 Pragmas</a></H2> <p>There are a few SWIG pragmas specific to the D module, which you can use to influence the D code SWIG generates:</p> @@ -364,7 +364,7 @@ struct A { </dl> -<H2><a name="D_exceptions"></a>22.6 D Exceptions</H2> +<H2><a name="D_exceptions">22.6 D Exceptions</a></H2> <p>Out of the box, C++ exceptions are fundamentally incompatible to their equivalent in the D world and cannot simply be propagated to a calling D method. There is, however, an easy way to solve this problem: Just catch the exception in the C/C++ wrapper layer, pass the contents to D, and make the wrapper code rethrow the exception in the D world.</p> @@ -374,7 +374,7 @@ struct A { <p>As this feature is implemented in exactly the same way it is for C#, please see the <a href="CSharp.html#CSharp_exceptions">C# documentation</a> for a more detailed explanation.</p> -<H2><a name="D_directors"></a>22.7 D Directors</H2> +<H2><a name="D_directors">22.7 D Directors</a></H2> <p>When the directors feature is activated, SWIG generates extra code on both the C++ and the D side to enable cross-language polymorphism. Essentially, this means that if you subclass a proxy class in D, C++ code can access any overridden virtual methods just as if you created a derived class in C++.</p> @@ -383,16 +383,16 @@ struct A { </p> -<H2><a name="D_other_features"></a>22.8 Other features</H2> +<H2><a name="D_other_features">22.8 Other features</a></H2> -<H3><a name="D_nspace"></a>22.8.1 Extended namespace support (<tt>nspace</tt>)</H3> +<H3><a name="D_nspace">22.8.1 Extended namespace support (<tt>nspace</tt>)</a></H3> <p>By default, SWIG flattens all C++ namespaces into a single target language namespace, but as for Java and C#, the <a href="SWIGPlus.html#SWIGPlus_nspace"><tt>nspace</tt></a> feature is supported for D. If it is active, C++ namespaces are mapped to D packages/modules. Note, however, that like for the other languages, <em>free</em> variables and functions are not supported yet; currently, they are all allows written to the main proxy D module.</p> -<H3><a name="D_native_pointer_support"></a>22.8.2 Native pointer support</H3> +<H3><a name="D_native_pointer_support">22.8.2 Native pointer support</a></H3> <p>Contrary to many of the scripting languages supported by SWIG, D fully supports C-style pointers. The D module thus includes a custom mechanism to wrap C pointers directly as D pointers where applicable, that is, if the type that is pointed to is represented the same in C and D (on the bit-level), dubbed a <em>primitive type</em> below.</p> @@ -404,7 +404,7 @@ struct A { <p>To determine if a type should be considered primitive, the <tt>cprimitive</tt> attribute on its <tt>dtype</tt> attribute is used. For example, the <tt>dtype</tt> typemap for <tt>float</tt> has <tt>cprimitive="1"</tt>, so the code from the <tt>nativepointer</tt> attribute is taken into account e.g. for <tt>float **</tt> or the function pointer <tt>float (*)(float *)</tt>.</p> -<H3><a name="D_operator_overloading"></a>22.8.3 Operator overloading</H3> +<H3><a name="D_operator_overloading">22.8.3 Operator overloading</a></H3> <p>The D module comes with basic operator overloading support for both D1 and D2. There are, however, a few limitations arising from conceptual differences between C++ and D:</p> @@ -416,7 +416,7 @@ struct A { <p>There are also some cases where the operators can be translated to D, but the differences in the implementation details are big enough that a rather involved scheme would be required for automatic wrapping them, which has not been implemented yet. This affects, for example, the array subscript operator, <tt>[]</tt>, in combination with assignments - while <tt>operator []</tt> in C++ simply returns a reference which is then written to, D resorts to a separate <tt>opIndexAssign</tt> method -, or implicit casting (which was introduced in D2 via <tt>alias this</tt>). Despite the lack of automatic support, manually handling these cases should be perfectly possible.</p> -<H3><a name="D_test_suite"></a>22.8.4 Running the test-suite</H3> +<H3><a name="D_test_suite">22.8.4 Running the test-suite</a></H3> <p>As with any other language, the SWIG test-suite can be built for D using the <tt>*-d-test-suite</tt> targets of the top-level Makefile. By default, D1 is targeted, to build it with D2, use the optional <tt>D_VERSION</tt> variable, e.g. <tt>make check-d-test-suite D_VERSION=2</tt>.</p> @@ -424,14 +424,14 @@ struct A { <p>Note: If you want to use GDC on Linux or another platform which requires you to link <tt>libdl</tt> for dynamically loading the shared library, you might have to add <tt>-ldl</tt> manually to the <tt>d_compile</tt> target in <tt>Examples/Makefile</tt>, because GDC does not currently honor the <tt>pragma(lib,...)</tt> statement.</p> -<H2><a name="D_typemap_examples"></a>22.9 D Typemap examples</H2> +<H2><a name="D_typemap_examples">22.9 D Typemap examples</a></H2> <p>There are no D-specific typemap examples yet. However, with the above <a href="D.html#D_typemap_name_comparison">name comparison table</a>, you should be able to get an idea what can be done by looking at the <a href="CSharp.html#CSharp_typemap_examples">corresponding C# section</a>.</p> -<H2><a name="D_planned_features"></a>22.10 Work in progress and planned features</H2> +<H2><a name="D_planned_features">22.10 Work in progress and planned features</a></H2> <p>There are a couple of features which are not implemented yet, but would be very useful and might be added in the near future:</p> diff --git a/Doc/Manual/Extending.html b/Doc/Manual/Extending.html index 59c63403d..7519dca94 100644 --- a/Doc/Manual/Extending.html +++ b/Doc/Manual/Extending.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Extending"></a>41 Extending SWIG to support new languages</H1> +<H1><a name="Extending">41 Extending SWIG to support new languages</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -75,7 +75,7 @@ -<H2><a name="Extending_nn2"></a>41.1 Introduction</H2> +<H2><a name="Extending_nn2">41.1 Introduction</a></H2> <p> @@ -91,7 +91,7 @@ Also, this chapter is not meant to be a hand-holding tutorial. As a starting po you should probably look at one of SWIG's existing modules. </p> -<H2><a name="Extending_nn3"></a>41.2 Prerequisites</H2> +<H2><a name="Extending_nn3">41.2 Prerequisites</a></H2> <p> @@ -121,7 +121,7 @@ obvious, but almost all SWIG directives as well as the low-level generation of wrapper code are driven by C++ datatypes. </p> -<H2><a name="Extending_nn4"></a>41.3 The Big Picture</H2> +<H2><a name="Extending_nn4">41.3 The Big Picture</a></H2> <p> @@ -158,7 +158,7 @@ role in making the system work. For example, both typemaps and declaration anno based on pattern matching and interact heavily with the underlying type system. </p> -<H2><a name="Extending_nn5"></a>41.4 Execution Model</H2> +<H2><a name="Extending_nn5">41.4 Execution Model</a></H2> <p> @@ -203,7 +203,7 @@ latter stage of compilation. The next few sections briefly describe some of these stages. </p> -<H3><a name="Extending_nn6"></a>41.4.1 Preprocessing</H3> +<H3><a name="Extending_nn6">41.4.1 Preprocessing</a></H3> <p> @@ -284,7 +284,7 @@ been expanded as well as everything else that goes into the low-level construction of the wrapper code. </p> -<H3><a name="Extending_nn7"></a>41.4.2 Parsing</H3> +<H3><a name="Extending_nn7">41.4.2 Parsing</a></H3> <p> @@ -385,7 +385,7 @@ returning a <tt>foo</tt> and taking types <tt>a</tt> and <tt>b</tt> as arguments). </p> -<H3><a name="Extending_nn8"></a>41.4.3 Parse Trees</H3> +<H3><a name="Extending_nn8">41.4.3 Parse Trees</a></H3> <p> @@ -640,7 +640,7 @@ $ swig -c++ -python -debug-module 4 example.i </pre> </div> -<H3><a name="Extending_nn9"></a>41.4.4 Attribute namespaces</H3> +<H3><a name="Extending_nn9">41.4.4 Attribute namespaces</a></H3> <p> @@ -659,7 +659,7 @@ that matches the name of the target language. For example, <tt>python:foo</tt> <tt>perl:foo</tt>. </p> -<H3><a name="Extending_nn10"></a>41.4.5 Symbol Tables</H3> +<H3><a name="Extending_nn10">41.4.5 Symbol Tables</a></H3> <p> @@ -750,7 +750,7 @@ example.i:5. Previous declaration is foo_i(int ) </pre> </div> -<H3><a name="Extending_nn11"></a>41.4.6 The %feature directive</H3> +<H3><a name="Extending_nn11">41.4.6 The %feature directive</a></H3> <p> @@ -806,7 +806,7 @@ For example, the exception code above is simply stored without any modifications. </p> -<H3><a name="Extending_nn12"></a>41.4.7 Code Generation</H3> +<H3><a name="Extending_nn12">41.4.7 Code Generation</a></H3> <p> @@ -928,7 +928,7 @@ public : The role of these functions is described shortly. </p> -<H3><a name="Extending_nn13"></a>41.4.8 SWIG and XML</H3> +<H3><a name="Extending_nn13">41.4.8 SWIG and XML</a></H3> <p> @@ -941,7 +941,7 @@ internal data structures, it may be useful to keep XML in the back of your mind as a model. </p> -<H2><a name="Extending_nn14"></a>41.5 Primitive Data Structures</H2> +<H2><a name="Extending_nn14">41.5 Primitive Data Structures</a></H2> <p> @@ -987,7 +987,7 @@ typedef Hash Typetab; </pre> </div> -<H3><a name="Extending_nn15"></a>41.5.1 Strings</H3> +<H3><a name="Extending_nn15">41.5.1 Strings</a></H3> <p> @@ -1128,7 +1128,7 @@ Returns the number of replacements made (if any). </div> -<H3><a name="Extending_nn16"></a>41.5.2 Hashes</H3> +<H3><a name="Extending_nn16">41.5.2 Hashes</a></H3> <p> @@ -1205,7 +1205,7 @@ Returns the list of hash table keys. </div> -<H3><a name="Extending_nn17"></a>41.5.3 Lists</H3> +<H3><a name="Extending_nn17">41.5.3 Lists</a></H3> <p> @@ -1294,7 +1294,7 @@ If <tt>t</tt> is not a standard object, it is assumed to be a <tt>char *</tt> and is used to create a String object. </div> -<H3><a name="Extending_nn18"></a>41.5.4 Common operations</H3> +<H3><a name="Extending_nn18">41.5.4 Common operations</a></H3> The following operations are applicable to all datatypes. @@ -1349,7 +1349,7 @@ objects and report errors. Gets the line number associated with <tt>x</tt>. </div> -<H3><a name="Extending_nn19"></a>41.5.5 Iterating over Lists and Hashes</H3> +<H3><a name="Extending_nn19">41.5.5 Iterating over Lists and Hashes</a></H3> To iterate over the elements of a list or a hash table, the following functions are used: @@ -1394,7 +1394,7 @@ for (j = First(j); j.item; j= Next(j)) { </div> -<H3><a name="Extending_nn20"></a>41.5.6 I/O</H3> +<H3><a name="Extending_nn20">41.5.6 I/O</a></H3> Special I/O functions are used for all internal I/O. These operations @@ -1528,7 +1528,7 @@ Printf(f, "%s\n", s); Similarly, the preprocessor and parser all operate on string-files. </p> -<H2><a name="Extending_nn21"></a>41.6 Navigating and manipulating parse trees</H2> +<H2><a name="Extending_nn21">41.6 Navigating and manipulating parse trees</a></H2> Parse trees are built as collections of hash tables. Each node is a hash table in which @@ -1662,7 +1662,7 @@ Deletes a node from the parse tree. Deletion reconnects siblings and properly u the parent so that sibling nodes are unaffected. </div> -<H2><a name="Extending_nn22"></a>41.7 Working with attributes</H2> +<H2><a name="Extending_nn22">41.7 Working with attributes</a></H2> <p> @@ -1779,7 +1779,7 @@ the attribute is optional. <tt>Swig_restore()</tt> must always be called after function. </div> -<H2><a name="Extending_nn23"></a>41.8 Type system</H2> +<H2><a name="Extending_nn23">41.8 Type system</a></H2> <p> @@ -1788,7 +1788,7 @@ pointers, references, and pointers to members. A detailed discussion of type theory is impossible here. However, let's cover the highlights. </p> -<H3><a name="Extending_nn24"></a>41.8.1 String encoding of types</H3> +<H3><a name="Extending_nn24">41.8.1 String encoding of types</a></H3> <p> @@ -1889,7 +1889,7 @@ make the final type, the two parts are just joined together using string concatenation. </p> -<H3><a name="Extending_nn25"></a>41.8.2 Type construction</H3> +<H3><a name="Extending_nn25">41.8.2 Type construction</a></H3> <p> @@ -2058,7 +2058,7 @@ Returns the prefix of a type. For example, if <tt>ty</tt> is <tt>ty</tt> is unmodified. </div> -<H3><a name="Extending_nn26"></a>41.8.3 Type tests</H3> +<H3><a name="Extending_nn26">41.8.3 Type tests</a></H3> <p> @@ -2145,7 +2145,7 @@ Checks if <tt>ty</tt> is a varargs type. Checks if <tt>ty</tt> is a templatized type. </div> -<H3><a name="Extending_nn27"></a>41.8.4 Typedef and inheritance</H3> +<H3><a name="Extending_nn27">41.8.4 Typedef and inheritance</a></H3> <p> @@ -2247,7 +2247,7 @@ Fully reduces <tt>ty</tt> according to typedef rules. Resulting datatype will consist only of primitive typenames. </div> -<H3><a name="Extending_nn28"></a>41.8.5 Lvalues</H3> +<H3><a name="Extending_nn28">41.8.5 Lvalues</a></H3> <p> @@ -2284,7 +2284,7 @@ Literal y; // type = 'Literal', ltype='p.char' </pre> </div> -<H3><a name="Extending_nn29"></a>41.8.6 Output functions</H3> +<H3><a name="Extending_nn29">41.8.6 Output functions</a></H3> <p> @@ -2346,7 +2346,7 @@ SWIG, but is most commonly associated with type-descriptor objects that appear in wrappers (e.g., <tt>SWIGTYPE_p_double</tt>). </div> -<H2><a name="Extending_nn30"></a>41.9 Parameters</H2> +<H2><a name="Extending_nn30">41.9 Parameters</a></H2> <p> @@ -2445,7 +2445,7 @@ included. Used to emit prototypes. Returns the number of required (non-optional) arguments in <tt>p</tt>. </div> -<H2><a name="Extending_nn31"></a>41.10 Writing a Language Module</H2> +<H2><a name="Extending_nn31">41.10 Writing a Language Module</a></H2> <p> @@ -2460,7 +2460,7 @@ describes the creation of a minimal Python module. You should be able to extra this to other languages. </p> -<H3><a name="Extending_nn32"></a>41.10.1 Execution model</H3> +<H3><a name="Extending_nn32">41.10.1 Execution model</a></H3> <p> @@ -2470,7 +2470,7 @@ the parsing of command line options, all aspects of code generation are controll different methods of the <tt>Language</tt> that must be defined by your module. </p> -<H3><a name="Extending_starting_out"></a>41.10.2 Starting out</H3> +<H3><a name="Extending_starting_out">41.10.2 Starting out</a></H3> <p> @@ -2578,7 +2578,7 @@ that activates your module. For example, <tt>swig -python foo.i</tt>. The messages from your new module should appear. </p> -<H3><a name="Extending_nn34"></a>41.10.3 Command line options</H3> +<H3><a name="Extending_nn34">41.10.3 Command line options</a></H3> <p> @@ -2637,7 +2637,7 @@ to mark the option as valid. If you forget to do this, SWIG will terminate wit unrecognized command line option error. </p> -<H3><a name="Extending_nn35"></a>41.10.4 Configuration and preprocessing</H3> +<H3><a name="Extending_nn35">41.10.4 Configuration and preprocessing</a></H3> <p> @@ -2686,7 +2686,7 @@ an implementation file <tt>python.cxx</tt> and a configuration file <tt>python.swg</tt>. </p> -<H3><a name="Extending_nn36"></a>41.10.5 Entry point to code generation</H3> +<H3><a name="Extending_nn36">41.10.5 Entry point to code generation</a></H3> <p> @@ -2744,7 +2744,7 @@ int Python::top(Node *n) { </pre> </div> -<H3><a name="Extending_nn37"></a>41.10.6 Module I/O and wrapper skeleton</H3> +<H3><a name="Extending_nn37">41.10.6 Module I/O and wrapper skeleton</a></H3> <!-- please report bugs in this section to mgossage --> @@ -2892,7 +2892,7 @@ functionWrapper : void Shape_y_set(Shape *self,double y) </pre> </div> -<H3><a name="Extending_nn38"></a>41.10.7 Low-level code generators</H3> +<H3><a name="Extending_nn38">41.10.7 Low-level code generators</a></H3> <!-- please report bugs in this section to mgossage --> @@ -3046,7 +3046,7 @@ but without the typemaps, there is still work to do. </p> -<H3><a name="Extending_configuration_files"></a>41.10.8 Configuration files</H3> +<H3><a name="Extending_configuration_files">41.10.8 Configuration files</a></H3> <!-- please report bugs in this section to ttn --> @@ -3190,7 +3190,7 @@ politely displays the ignoring language message. </dl> -<H3><a name="Extending_nn40"></a>41.10.9 Runtime support</H3> +<H3><a name="Extending_nn40">41.10.9 Runtime support</a></H3> <p> @@ -3199,7 +3199,7 @@ Discuss the kinds of functions typically needed for SWIG runtime support (e.g. the SWIG files that implement those functions. </p> -<H3><a name="Extending_nn41"></a>41.10.10 Standard library files</H3> +<H3><a name="Extending_nn41">41.10.10 Standard library files</a></H3> <p> @@ -3218,7 +3218,7 @@ The following are the minimum that are usually supported: Please copy these and modify for any new language. </p> -<H3><a name="Extending_nn42"></a>41.10.11 User examples</H3> +<H3><a name="Extending_nn42">41.10.11 User examples</a></H3> <p> @@ -3247,7 +3247,7 @@ during this process, see the section on <a href="#Extending_configuration_files" files</a>. </p> -<H3><a name="Extending_test_suite"></a>41.10.12 Test driven development and the test-suite</H3> +<H3><a name="Extending_test_suite">41.10.12 Test driven development and the test-suite</a></H3> <p> @@ -3306,7 +3306,7 @@ It is therefore essential that the runtime tests are written in a manner that di but error/exception out with an error message on stderr on failure. </p> -<H4><a name="Extending_running_test_suite"></a>41.10.12.1 Running the test-suite</H4> +<H4><a name="Extending_running_test_suite">41.10.12.1 Running the test-suite</a></H4> <p> @@ -3498,7 +3498,7 @@ It can be run in the same way as the other language test-suites, replacing [lang The test cases used and the way it works is described in <tt>Examples/test-suite/errors/Makefile.in</tt>. </p> -<H3><a name="Extending_nn43"></a>41.10.13 Documentation</H3> +<H3><a name="Extending_nn43">41.10.13 Documentation</a></H3> <p> @@ -3530,7 +3530,7 @@ Some topics that you'll want to be sure to address include: if available. </ul> -<H3><a name="Extending_prerequisites"></a>41.10.14 Prerequisites for adding a new language module to the SWIG distribution</H3> +<H3><a name="Extending_prerequisites">41.10.14 Prerequisites for adding a new language module to the SWIG distribution</a></H3> <p> @@ -3587,7 +3587,7 @@ should be added should there be an area not already covered by the existing tests. </p> -<H3><a name="Extending_coding_style_guidelines"></a>41.10.15 Coding style guidelines</H3> +<H3><a name="Extending_coding_style_guidelines">41.10.15 Coding style guidelines</a></H3> <p> @@ -3611,7 +3611,7 @@ The generated C/C++ code should also follow this style as close as possible. How should be avoided as unlike the SWIG developers, users will never have consistent tab settings. </p> -<H2><a name="Extending_debugging_options"></a>41.11 Debugging Options</H2> +<H2><a name="Extending_debugging_options">41.11 Debugging Options</a></H2> <p> @@ -3638,7 +3638,7 @@ There are various command line options which can aid debugging a SWIG interface The complete list of command line options for SWIG are available by running <tt>swig -help</tt>. </p> -<H2><a name="Extending_nn46"></a>41.12 Guide to parse tree nodes</H2> +<H2><a name="Extending_nn46">41.12 Guide to parse tree nodes</a></H2> <p> @@ -4046,7 +4046,7 @@ extern "X" { ... } declaration. </pre> </div> -<H2><a name="Extending_further_info"></a>41.13 Further Development Information</H2> +<H2><a name="Extending_further_info">41.13 Further Development Information</a></H2> <p> diff --git a/Doc/Manual/Go.html b/Doc/Manual/Go.html index f60e4d3f5..2fff4edf5 100644 --- a/Doc/Manual/Go.html +++ b/Doc/Manual/Go.html @@ -5,7 +5,7 @@ <link rel="stylesheet" type="text/css" href="style.css"> </head> <body bgcolor="#FFFFFF"> -<H1><a name="Go"></a>23 SWIG and Go</H1> +<H1><a name="Go">23 SWIG and Go</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -56,7 +56,7 @@ the Go programming language see <a href="http://golang.org/">golang.org</a>. </p> -<H2><a name="Go_overview"></a>23.1 Overview</H2> +<H2><a name="Go_overview">23.1 Overview</a></H2> <p> @@ -85,7 +85,7 @@ type-safe as well. In case of type issues the build will fail and hence SWIG's are not used. </p> -<H2><a name="Go_examples"></a>23.2 Examples</H2> +<H2><a name="Go_examples">23.2 Examples</a></H2> <p> @@ -100,7 +100,7 @@ SWIG interface file extension for backwards compatibility with Go 1. </p> -<H2><a name="Go_running_swig"></a>23.3 Running SWIG with Go</H2> +<H2><a name="Go_running_swig">23.3 Running SWIG with Go</a></H2> <p> @@ -180,7 +180,7 @@ sequence for this approach would look like this: </pre></div> -<H3><a name="Go_commandline"></a>23.3.1 Go-specific Commandline Options</H3> +<H3><a name="Go_commandline">23.3.1 Go-specific Commandline Options</a></H3> <p> @@ -263,7 +263,7 @@ swig -go -help </table> -<H3><a name="Go_outputs"></a>23.3.2 Generated Wrapper Files</H3> +<H3><a name="Go_outputs">23.3.2 Generated Wrapper Files</a></H3> <p>There are two different approaches to generating wrapper files, @@ -307,7 +307,7 @@ combined with the compiled MODULE.go using go tool pack. </ul> -<H2><a name="Go_basic_tour"></a>23.4 A tour of basic C/C++ wrapping</H2> +<H2><a name="Go_basic_tour">23.4 A tour of basic C/C++ wrapping</a></H2> <p> @@ -317,7 +317,7 @@ modifications have to occur. This section briefly covers the essential aspects of this wrapping. </p> -<H3><a name="Go_package"></a>23.4.1 Go Package Name</H3> +<H3><a name="Go_package">23.4.1 Go Package Name</a></H3> <p> @@ -327,7 +327,7 @@ directive. You may override this by using SWIG's <tt>-package</tt> command line option. </p> -<H3><a name="Go_names"></a>23.4.2 Go Names</H3> +<H3><a name="Go_names">23.4.2 Go Names</a></H3> <p> @@ -359,7 +359,7 @@ followed by that name, and the destructor will be named <tt>Delete</tt> followed by that name. </p> -<H3><a name="Go_constants"></a>23.4.3 Go Constants</H3> +<H3><a name="Go_constants">23.4.3 Go Constants</a></H3> <p> @@ -367,7 +367,7 @@ C/C++ constants created via <tt>#define</tt> or the <tt>%constant</tt> directive become Go constants, declared with a <tt>const</tt> declaration. -<H3><a name="Go_enumerations"></a>23.4.4 Go Enumerations</H3> +<H3><a name="Go_enumerations">23.4.4 Go Enumerations</a></H3> <p> @@ -377,7 +377,7 @@ usual). The values of the enumeration will become variables in Go; code should avoid modifying those variables. </p> -<H3><a name="Go_classes"></a>23.4.5 Go Classes</H3> +<H3><a name="Go_classes">23.4.5 Go Classes</a></H3> <p> @@ -455,7 +455,7 @@ returns a go interface. If the returned pointer can be null, you can check for this by calling the Swigcptr() method. </p> -<H4><a name="Go_class_memory"></a>23.4.5.1 Go Class Memory Management</H4> +<H4><a name="Go_class_memory">23.4.5.1 Go Class Memory Management</a></H4> <p> @@ -577,7 +577,7 @@ func (o *GoClassName) Close() { </pre> </div> -<H4><a name="Go_class_inheritance"></a>23.4.5.2 Go Class Inheritance</H4> +<H4><a name="Go_class_inheritance">23.4.5.2 Go Class Inheritance</a></H4> <p> @@ -589,7 +589,7 @@ Doing the reverse will require an explicit type assertion, which will be checked dynamically. </p> -<H3><a name="Go_templates"></a>23.4.6 Go Templates</H3> +<H3><a name="Go_templates">23.4.6 Go Templates</a></H3> <p> @@ -598,7 +598,7 @@ wrappers for a particular template instantation. To do this, use the <tt>%template</tt> directive. -<H3><a name="Go_director_classes"></a>23.4.7 Go Director Classes</H3> +<H3><a name="Go_director_classes">23.4.7 Go Director Classes</a></H3> <p> @@ -616,7 +616,7 @@ completely to avoid common pitfalls with directors in Go. </p> -<H4><a name="Go_director_example_cpp_code"></a>23.4.7.1 Example C++ code</H4> +<H4><a name="Go_director_example_cpp_code">23.4.7.1 Example C++ code</a></H4> <p> @@ -688,7 +688,7 @@ be found in <a href="#Go_director_foobargo_class">the end of the guide</a>. </p> -<H4><a name="Go_director_enable"></a>23.4.7.2 Enable director feature</H4> +<H4><a name="Go_director_enable">23.4.7.2 Enable director feature</a></H4> <p> @@ -723,7 +723,7 @@ documentation on directors. </p> -<H4><a name="Go_director_ctor_dtor"></a>23.4.7.3 Constructor and destructor</H4> +<H4><a name="Go_director_ctor_dtor">23.4.7.3 Constructor and destructor</a></H4> <p> @@ -776,7 +776,7 @@ embedding</a>. </p> -<H4><a name="Go_director_overriding"></a>23.4.7.4 Override virtual methods</H4> +<H4><a name="Go_director_overriding">23.4.7.4 Override virtual methods</a></H4> <p> @@ -842,7 +842,7 @@ the Go methods. </p> -<H4><a name="Go_director_base_methods"></a>23.4.7.5 Call base methods</H4> +<H4><a name="Go_director_base_methods">23.4.7.5 Call base methods</a></H4> <p> @@ -879,7 +879,7 @@ be found in <a href="#Go_director_foobargo_class">the end of the guide</a>. </p> -<H4><a name="Go_director_subclass"></a>23.4.7.6 Subclass via embedding</H4> +<H4><a name="Go_director_subclass">23.4.7.6 Subclass via embedding</a></H4> <p> @@ -947,7 +947,7 @@ class. </p> -<H4><a name="Go_director_finalizer"></a>23.4.7.7 Memory management with runtime.SetFinalizer</H4> +<H4><a name="Go_director_finalizer">23.4.7.7 Memory management with runtime.SetFinalizer</a></H4> <p> @@ -1012,7 +1012,7 @@ before using <tt>runtime.SetFinalizer</tt> to know all of its gotchas. </p> -<H4><a name="Go_director_foobargo_class"></a>23.4.7.8 Complete FooBarGo example class</H4> +<H4><a name="Go_director_foobargo_class">23.4.7.8 Complete FooBarGo example class</a></H4> <p> @@ -1141,7 +1141,7 @@ SWIG/Examples/go/director/</a>. </p> -<H3><a name="Go_primitive_type_mappings"></a>23.4.8 Default Go primitive type mappings</H3> +<H3><a name="Go_primitive_type_mappings">23.4.8 Default Go primitive type mappings</a></H3> <p> @@ -1248,7 +1248,7 @@ that typemap, or add new values, to control how C/C++ types are mapped into Go types. </p> -<H3><a name="Go_output_arguments"></a>23.4.9 Output arguments</H3> +<H3><a name="Go_output_arguments">23.4.9 Output arguments</a></H3> <p>Because of limitations in the way output arguments are processed in swig, @@ -1301,7 +1301,7 @@ void f(char *output); </pre> </div> -<H3><a name="Go_adding_additional_code"></a>23.4.10 Adding additional go code</H3> +<H3><a name="Go_adding_additional_code">23.4.10 Adding additional go code</a></H3> <p>Often the APIs generated by swig are not very natural in go, especially if @@ -1396,7 +1396,7 @@ func bar() { </pre> </div> -<H3><a name="Go_typemaps"></a>23.4.11 Go typemaps</H3> +<H3><a name="Go_typemaps">23.4.11 Go typemaps</a></H3> <p> diff --git a/Doc/Manual/Guile.html b/Doc/Manual/Guile.html index 4c1126c7f..b424df6e2 100644 --- a/Doc/Manual/Guile.html +++ b/Doc/Manual/Guile.html @@ -8,7 +8,7 @@ <body bgcolor="#ffffff"> -<H1><a name="Guile"></a>24 SWIG and Guile</H1> +<H1><a name="Guile">24 SWIG and Guile</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -47,7 +47,7 @@ <p> This section details guile-specific support in SWIG. -<H2><a name="Guile_nn1"></a>24.1 Supported Guile Versions</H2> +<H2><a name="Guile_nn1">24.1 Supported Guile Versions</a></H2> <p> @@ -61,7 +61,7 @@ improved performance. This is currently not tested with swig so your mileage may vary. To be safe set environment variable GUILE_AUTO_COMPILE to 0 when using swig generated guile code. -<H2><a name="Guile_nn2"></a>24.2 Meaning of "Module"</H2> +<H2><a name="Guile_nn2">24.2 Meaning of "Module"</a></H2> <p> @@ -69,7 +69,7 @@ There are three different concepts of "module" involved, defined separately for SWIG, Guile, and Libtool. To avoid horrible confusion, we explicitly prefix the context, e.g., "guile-module". -<H2><a name="Guile_nn3"></a>24.3 Old GH Guile API</H2> +<H2><a name="Guile_nn3">24.3 Old GH Guile API</a></H2> <p>Guile 1.8 and older could be interfaced using two different api's, the SCM @@ -80,7 +80,7 @@ or the GH API. The GH interface to guile is deprecated. Read more about why in version of SWIG that can still generate guile GH wrapper code is 2.0.9. Please use that version if you really need the GH wrapper code. -<H2><a name="Guile_nn4"></a>24.4 Linkage</H2> +<H2><a name="Guile_nn4">24.4 Linkage</a></H2> <p> @@ -88,7 +88,7 @@ Guile support is complicated by a lack of user community cohesiveness, which manifests in multiple shared-library usage conventions. A set of policies implementing a usage convention is called a <b>linkage</b>. -<H3><a name="Guile_nn5"></a>24.4.1 Simple Linkage</H3> +<H3><a name="Guile_nn5">24.4.1 Simple Linkage</a></H3> <p> @@ -193,7 +193,7 @@ placed between the <code>define-module</code> form and the <code>SWIG_init</code> via a preprocessor define to avoid symbol clashes. For this case, however, passive linkage is available. -<H3><a name="Guile_nn6"></a>24.4.2 Passive Linkage</H3> +<H3><a name="Guile_nn6">24.4.2 Passive Linkage</a></H3> <p>Passive linkage is just like simple linkage, but it generates an @@ -203,7 +203,7 @@ package name (see below). <p>You should use passive linkage rather than simple linkage when you are using multiple modules. -<H3><a name="Guile_nn7"></a>24.4.3 Native Guile Module Linkage</H3> +<H3><a name="Guile_nn7">24.4.3 Native Guile Module Linkage</a></H3> <p>SWIG can also generate wrapper code that does all the Guile module @@ -244,7 +244,7 @@ Newer Guile versions have a shorthand procedure for this: </div> </ul> -<H3><a name="Guile_nn8"></a>24.4.4 Old Auto-Loading Guile Module Linkage</H3> +<H3><a name="Guile_nn8">24.4.4 Old Auto-Loading Guile Module Linkage</a></H3> <p>Guile used to support an autoloading facility for object-code @@ -270,7 +270,7 @@ option, SWIG generates an exported module initialization function with an appropriate name. -<H3><a name="Guile_nn9"></a>24.4.5 Hobbit4D Linkage</H3> +<H3><a name="Guile_nn9">24.4.5 Hobbit4D Linkage</a></H3> <p> @@ -295,7 +295,7 @@ my/lib/libfoo.so.X.Y.Z and friends. This scheme is still very experimental; the (hobbit4d link) conventions are not well understood. </p> -<H2><a name="Guile_nn10"></a>24.5 Underscore Folding</H2> +<H2><a name="Guile_nn10">24.5 Underscore Folding</a></H2> <p> @@ -307,7 +307,7 @@ complained so far. <code>%rename</code> to specify the Guile name of the wrapped functions and variables (see CHANGES). -<H2><a name="Guile_nn11"></a>24.6 Typemaps</H2> +<H2><a name="Guile_nn11">24.6 Typemaps</a></H2> <p> @@ -399,7 +399,7 @@ constant will appear as a scheme variable. See <a href="Customization.html#Customization_features">Features and the %feature directive</a> for info on how to apply the %feature.</p> -<H2><a name="Guile_nn12"></a>24.7 Representation of pointers as smobs</H2> +<H2><a name="Guile_nn12">24.7 Representation of pointers as smobs</a></H2> <p> @@ -420,7 +420,7 @@ representing the expected pointer type. See also If the Scheme object passed was not a SWIG smob representing a compatible pointer, a <code>wrong-type-arg</code> exception is raised. -<H3><a name="Guile_nn14"></a>24.7.1 Smobs</H3> +<H3><a name="Guile_nn14">24.7.1 Smobs</a></H3> <p> @@ -439,7 +439,7 @@ structure describing this type. If a generated GOOPS module has been loaded, sm the corresponding GOOPS class.</p> -<H3><a name="Guile_nn15"></a>24.7.2 Garbage Collection</H3> +<H3><a name="Guile_nn15">24.7.2 Garbage Collection</a></H3> <p>Garbage collection is a feature of Guile since version 1.6. As SWIG now requires Guile > 1.8, @@ -453,7 +453,7 @@ is exactly like described in <a href="Customization.html#Customization_ownership Object ownership and %newobject</a> in the SWIG manual. All typemaps use an $owner var, and the guile module replaces $owner with 0 or 1 depending on feature:new.</p> -<H2><a name="Guile_nn16"></a>24.8 Exception Handling</H2> +<H2><a name="Guile_nn16">24.8 Exception Handling</a></H2> <p> @@ -479,7 +479,7 @@ mapping: The default when not specified here is to use "swig-error". See Lib/exception.i for details. -<H2><a name="Guile_nn17"></a>24.9 Procedure documentation</H2> +<H2><a name="Guile_nn17">24.9 Procedure documentation</a></H2> <p>If invoked with the command-line option <code>-procdoc @@ -514,7 +514,7 @@ like this: typemap argument <code>doc</code>. See <code>Lib/guile/typemaps.i</code> for details. -<H2><a name="Guile_nn18"></a>24.10 Procedures with setters</H2> +<H2><a name="Guile_nn18">24.10 Procedures with setters</a></H2> <p>For global variables, SWIG creates a single wrapper procedure @@ -542,7 +542,7 @@ struct members, the procedures <code>(<var>struct</var>-<var>member</var>-get pointer)</code> and <code>(<var>struct-member</var>-set pointer value)</code> are <em>not</em> generated. -<H2><a name="Guile_nn19"></a>24.11 GOOPS Proxy Classes</H2> +<H2><a name="Guile_nn19">24.11 GOOPS Proxy Classes</a></H2> <p>SWIG can also generate classes and generic functions for use with @@ -688,7 +688,7 @@ Notice that <Foo> is used before it is defined. The fix is to just put th <code>%import "foo.h"</code> before the <code>%inline</code> block. </p> -<H3><a name="Guile_nn20"></a>24.11.1 Naming Issues</H3> +<H3><a name="Guile_nn20">24.11.1 Naming Issues</a></H3> <p>As you can see in the example above, there are potential naming conflicts. The default exported @@ -725,7 +725,7 @@ guile-modules. For example,</p> (use-modules ((Test) #:renamer (symbol-prefix-proc 'goops:))) </pre></div> -<H3><a name="Guile_nn21"></a>24.11.2 Linking</H3> +<H3><a name="Guile_nn21">24.11.2 Linking</a></H3> <p>The guile-modules generated above all need to be linked together. GOOPS support requires diff --git a/Doc/Manual/Introduction.html b/Doc/Manual/Introduction.html index dc68bff43..db35d8425 100644 --- a/Doc/Manual/Introduction.html +++ b/Doc/Manual/Introduction.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Introduction"></a>2 Introduction</H1> +<H1><a name="Introduction">2 Introduction</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -31,7 +31,7 @@ -<H2><a name="Introduction_nn2"></a>2.1 What is SWIG?</H2> +<H2><a name="Introduction_nn2">2.1 What is SWIG?</a></H2> <p> @@ -71,7 +71,7 @@ small; especially the research and development work that is commonly found in scientific and engineering projects. However, nowadays SWIG is known to be used in many large open source and commercial projects. -<H2><a name="Introduction_nn3"></a>2.2 Why use SWIG?</H2> +<H2><a name="Introduction_nn3">2.2 Why use SWIG?</a></H2> <p> @@ -143,7 +143,7 @@ it provides a wide variety of customization features that let you change almost every aspect of the language bindings. This is the main reason why SWIG has such a large user manual ;-). -<H2><a name="Introduction_nn4"></a>2.3 A SWIG example</H2> +<H2><a name="Introduction_nn4">2.3 A SWIG example</a></H2> <p> @@ -174,7 +174,7 @@ variable <tt>My_variable</tt> from Tcl. You start by making a SWIG interface file as shown below (by convention, these files carry a .i suffix) : -<H3><a name="Introduction_nn5"></a>2.3.1 SWIG interface file</H3> +<H3><a name="Introduction_nn5">2.3.1 SWIG interface file</a></H3> <div class="code"><pre> @@ -199,7 +199,7 @@ module that will be created by SWIG. The <tt>%{ %}</tt> block provides a location for inserting additional code, such as C header files or additional C declarations, into the generated C wrapper code. -<H3><a name="Introduction_nn6"></a>2.3.2 The swig command</H3> +<H3><a name="Introduction_nn6">2.3.2 The swig command</a></H3> <p> @@ -233,7 +233,7 @@ and variables declared in the SWIG interface. A look at the file <tt>example_wrap.c</tt> reveals a hideous mess. However, you almost never need to worry about it. -<H3><a name="Introduction_nn7"></a>2.3.3 Building a Perl5 module</H3> +<H3><a name="Introduction_nn7">2.3.3 Building a Perl5 module</a></H3> <p> @@ -259,7 +259,7 @@ unix > </pre></div> -<H3><a name="Introduction_nn8"></a>2.3.4 Building a Python module</H3> +<H3><a name="Introduction_nn8">2.3.4 Building a Python module</a></H3> <p> @@ -283,7 +283,7 @@ Type "copyright", "credits" or "license" for more information. 7.5 </pre></div> -<H3><a name="Introduction_nn9"></a>2.3.5 Shortcuts</H3> +<H3><a name="Introduction_nn9">2.3.5 Shortcuts</a></H3> <p> @@ -309,7 +309,7 @@ print $example::My_variable + 4.5, "\n"; 7.5 </pre></div> -<H2><a name="Introduction_nn10"></a>2.4 Supported C/C++ language features</H2> +<H2><a name="Introduction_nn10">2.4 Supported C/C++ language features</a></H2> <p> @@ -348,7 +348,7 @@ wrapping simple C++ code. In fact, SWIG is able to handle C++ code that stresses the very limits of many C++ compilers. -<H2><a name="Introduction_nn11"></a>2.5 Non-intrusive interface building</H2> +<H2><a name="Introduction_nn11">2.5 Non-intrusive interface building</a></H2> <p> @@ -360,7 +360,7 @@ interface and reuse the code in other applications. It is also possible to support different types of interfaces depending on the application. </p> -<H2><a name="Introduction_build_system"></a>2.6 Incorporating SWIG into a build system</H2> +<H2><a name="Introduction_build_system">2.6 Incorporating SWIG into a build system</a></H2> <p> @@ -418,7 +418,7 @@ which will invoke SWIG and compile the generated C++ files into _example.so (UNI For other target languages on Windows a dll, instead of a .pyd file, is usually generated. </p> -<H2><a name="Introduction_nn12"></a>2.7 Hands off code generation</H2> +<H2><a name="Introduction_nn12">2.7 Hands off code generation</a></H2> <p> @@ -431,7 +431,7 @@ it allows others to forget about the low-level implementation details. </p> -<H2><a name="Introduction_nn13"></a>2.8 SWIG and freedom</H2> +<H2><a name="Introduction_nn13">2.8 SWIG and freedom</a></H2> <p> diff --git a/Doc/Manual/Java.html b/Doc/Manual/Java.html index b953eb518..9b18c4aa9 100644 --- a/Doc/Manual/Java.html +++ b/Doc/Manual/Java.html @@ -5,7 +5,7 @@ <link rel="stylesheet" type="text/css" href="style.css"> </head> <body bgcolor="#FFFFFF"> -<H1><a name="Java"></a>25 SWIG and Java</H1> +<H1><a name="Java">25 SWIG and Java</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -161,7 +161,7 @@ It covers most SWIG features, but certain low-level details are covered in less </p> -<H2><a name="Java_overview"></a>25.1 Overview</H2> +<H2><a name="Java_overview">25.1 Overview</a></H2> <p> @@ -196,7 +196,7 @@ Various customisation tips and techniques using SWIG directives are covered. The latter sections cover the advanced techniques of using typemaps for complete control of the wrapping process. </p> -<H2><a name="Java_preliminaries"></a>25.2 Preliminaries</H2> +<H2><a name="Java_preliminaries">25.2 Preliminaries</a></H2> <p> @@ -216,7 +216,7 @@ This is the commonly used method to load JNI code so your system will more than Android uses Java JNI and also works with SWIG. Please read the <a href="Android.html#Android">Android chapter</a> in conjunction with this one if you are targeting Android. </p> -<H3><a name="Java_running_swig"></a>25.2.1 Running SWIG</H3> +<H3><a name="Java_running_swig">25.2.1 Running SWIG</a></H3> <p> @@ -275,7 +275,7 @@ The following sections have further practical examples and details on how you mi compiling and using the generated files. </p> -<H3><a name="Java_commandline"></a>25.2.2 Additional Commandline Options</H3> +<H3><a name="Java_commandline">25.2.2 Additional Commandline Options</a></H3> <p> @@ -312,7 +312,7 @@ swig -java -help Their use will become clearer by the time you have finished reading this section on SWIG and Java. </p> -<H3><a name="Java_getting_right_headers"></a>25.2.3 Getting the right header files</H3> +<H3><a name="Java_getting_right_headers">25.2.3 Getting the right header files</a></H3> <p> @@ -327,7 +327,7 @@ They are usually in directories like this:</p> <p> The exact location may vary on your machine, but the above locations are typical. </p> -<H3><a name="Java_compiling_dynamic"></a>25.2.4 Compiling a dynamic module</H3> +<H3><a name="Java_compiling_dynamic">25.2.4 Compiling a dynamic module</a></H3> <p> @@ -362,7 +362,7 @@ The name of the shared library output file is important. If the name of your SWIG module is "<tt>example</tt>", the name of the corresponding shared library file should be "<tt>libexample.so</tt>" (or equivalent depending on your machine, see <a href="#Java_dynamic_linking_problems">Dynamic linking problems</a> for more information). The name of the module is specified using the <tt>%module</tt> directive or <tt>-module</tt> command line option.</p> -<H3><a name="Java_using_module"></a>25.2.5 Using your module</H3> +<H3><a name="Java_using_module">25.2.5 Using your module</a></H3> <p> @@ -397,7 +397,7 @@ $ If it doesn't work have a look at the following section which discusses problems loading the shared library. </p> -<H3><a name="Java_dynamic_linking_problems"></a>25.2.6 Dynamic linking problems</H3> +<H3><a name="Java_dynamic_linking_problems">25.2.6 Dynamic linking problems</a></H3> <p> @@ -484,7 +484,7 @@ The following section also contains some C++ specific linking problems and solut </p> -<H3><a name="Java_compilation_problems_cpp"></a>25.2.7 Compilation problems and compiling with C++</H3> +<H3><a name="Java_compilation_problems_cpp">25.2.7 Compilation problems and compiling with C++</a></H3> <p> @@ -536,7 +536,7 @@ Finally make sure the version of JDK header files matches the version of Java th </p> -<H3><a name="Java_building_windows"></a>25.2.8 Building on Windows</H3> +<H3><a name="Java_building_windows">25.2.8 Building on Windows</a></H3> <p> @@ -545,7 +545,7 @@ You will want to produce a DLL that can be loaded by the Java Virtual Machine. This section covers the process of using SWIG with Microsoft Visual C++ 6 although the procedure may be similar with other compilers. In order for everything to work, you will need to have a JDK installed on your machine in order to read the JNI header files.</p> -<H4><a name="Java_visual_studio"></a>25.2.8.1 Running SWIG from Visual Studio</H4> +<H4><a name="Java_visual_studio">25.2.8.1 Running SWIG from Visual Studio</a></H4> <p> @@ -584,7 +584,7 @@ To run the native code in the DLL (example.dll), make sure that it is in your pa If the library fails to load have a look at <a href="#Java_dynamic_linking_problems">Dynamic linking problems</a>. </p> -<H4><a name="Java_nmake"></a>25.2.8.2 Using NMAKE</H4> +<H4><a name="Java_nmake">25.2.8.2 Using NMAKE</a></H4> <p> @@ -643,7 +643,7 @@ Of course you may want to make changes for it to work for C++ by adding in the - </p> -<H2><a name="Java_basic_tour"></a>25.3 A tour of basic C/C++ wrapping</H2> +<H2><a name="Java_basic_tour">25.3 A tour of basic C/C++ wrapping</a></H2> <p> @@ -653,7 +653,7 @@ variables are wrapped with JavaBean type getters and setters and so forth. This section briefly covers the essential aspects of this wrapping. </p> -<H3><a name="Java_module_packages_classes"></a>25.3.1 Modules, packages and generated Java classes</H3> +<H3><a name="Java_module_packages_classes">25.3.1 Modules, packages and generated Java classes</a></H3> <p> @@ -689,7 +689,7 @@ swig -java -package com.bloggs.swig -outdir com/bloggs/swig example.i SWIG won't create the directory, so make sure it exists beforehand. </p> -<H3><a name="Java_functions"></a>25.3.2 Functions</H3> +<H3><a name="Java_functions">25.3.2 Functions</a></H3> <p> @@ -723,7 +723,7 @@ System.out.println(example.fact(4)); </pre></div> -<H3><a name="Java_global_variables"></a>25.3.3 Global variables</H3> +<H3><a name="Java_global_variables">25.3.3 Global variables</a></H3> <p> @@ -810,7 +810,7 @@ extern char *path; // Read-only (due to %immutable) </div> -<H3><a name="Java_constants"></a>25.3.4 Constants</H3> +<H3><a name="Java_constants">25.3.4 Constants</a></H3> <p> @@ -950,7 +950,7 @@ Or if you decide this practice isn't so bad and your own class implements <tt>ex </p> -<H3><a name="Java_enumerations"></a>25.3.5 Enumerations</H3> +<H3><a name="Java_enumerations">25.3.5 Enumerations</a></H3> <p> @@ -964,7 +964,7 @@ The final two approaches use simple integers for each enum item. Before looking at the various approaches for wrapping named C/C++ enums, anonymous enums are considered. </p> -<H4><a name="Java_anonymous_enums"></a>25.3.5.1 Anonymous enums</H4> +<H4><a name="Java_anonymous_enums">25.3.5.1 Anonymous enums</a></H4> <p> @@ -1027,7 +1027,7 @@ As in the case of constants, you can access them through either the module class </p> -<H4><a name="Java_typesafe_enums"></a>25.3.5.2 Typesafe enums</H4> +<H4><a name="Java_typesafe_enums">25.3.5.2 Typesafe enums</a></H4> <p> @@ -1121,7 +1121,7 @@ When upgrading to JDK 1.5 or later, proper Java enums could be used instead, wit The following section details proper Java enum generation. </p> -<H4><a name="Java_proper_enums"></a>25.3.5.3 Proper Java enums</H4> +<H4><a name="Java_proper_enums">25.3.5.3 Proper Java enums</a></H4> <p> @@ -1174,7 +1174,7 @@ The additional support methods need not be generated if none of the enum items h <a href="#Java_simpler_enum_classes">Simpler Java enums for enums without initializers</a> section. </p> -<H4><a name="Java_typeunsafe_enums"></a>25.3.5.4 Type unsafe enums</H4> +<H4><a name="Java_typeunsafe_enums">25.3.5.4 Type unsafe enums</a></H4> <p> @@ -1222,7 +1222,7 @@ Note that unlike typesafe enums, this approach requires users to mostly use diff Thus the upgrade path to proper enums provided in JDK 1.5 is more painful. </p> -<H4><a name="Java_simple_enums"></a>25.3.5.5 Simple enums</H4> +<H4><a name="Java_simple_enums">25.3.5.5 Simple enums</a></H4> <p> @@ -1241,7 +1241,7 @@ SWIG-1.3.21 and earlier versions wrapped all enums using this approach. The type unsafe approach is preferable to this one and this simple approach is only included for backwards compatibility with these earlier versions of SWIG. </p> -<H3><a name="Java_pointers"></a>25.3.6 Pointers</H3> +<H3><a name="Java_pointers">25.3.6 Pointers</a></H3> <p> @@ -1329,7 +1329,7 @@ C-style cast may return a bogus result whereas as the C++-style cast will return a NULL pointer if the conversion can't be performed. </p> -<H3><a name="Java_structures"></a>25.3.7 Structures</H3> +<H3><a name="Java_structures">25.3.7 Structures</a></H3> <p> @@ -1497,7 +1497,7 @@ x.setA(3); // Modify x.a - this is the same as b.f.a </div> -<H3><a name="Java_classes"></a>25.3.8 C++ classes</H3> +<H3><a name="Java_classes">25.3.8 C++ classes</a></H3> <p> @@ -1560,7 +1560,7 @@ int bar = Spam.getBar(); </div> -<H3><a name="Java_inheritance"></a>25.3.9 C++ inheritance</H3> +<H3><a name="Java_inheritance">25.3.9 C++ inheritance</a></H3> <p> @@ -1621,7 +1621,7 @@ Note that Java does not support multiple inheritance so any multiple inheritance A warning is given when multiple inheritance is detected and only the first base class is used. </p> -<H3><a name="Java_pointers_refs_arrays"></a>25.3.10 Pointers, references, arrays and pass by value</H3> +<H3><a name="Java_pointers_refs_arrays">25.3.10 Pointers, references, arrays and pass by value</a></H3> <p> @@ -1676,7 +1676,7 @@ to hold the result and a pointer is returned (Java will release this memory when the returned object's finalizer is run by the garbage collector). </p> -<H4><a name="Java_null_pointers"></a>25.3.10.1 Null pointers</H4> +<H4><a name="Java_null_pointers">25.3.10.1 Null pointers</a></H4> <p> @@ -1700,7 +1700,7 @@ For <tt>spam1</tt> and <tt>spam4</tt> above the Java <tt>null</tt> gets translat The converse also occurs, that is, NULL pointers are translated into <tt>null</tt> Java objects when returned from a C/C++ function. </p> -<H3><a name="Java_overloaded_functions"></a>25.3.11 C++ overloaded functions</H3> +<H3><a name="Java_overloaded_functions">25.3.11 C++ overloaded functions</a></H3> <p> @@ -1815,7 +1815,7 @@ void spam(unsigned short); // Ignored </pre> </div> -<H3><a name="Java_default_arguments"></a>25.3.12 C++ default arguments</H3> +<H3><a name="Java_default_arguments">25.3.12 C++ default arguments</a></H3> <p> @@ -1858,7 +1858,7 @@ Further details on default arguments and how to restore this approach are given </p> -<H3><a name="Java_namespaces"></a>25.3.13 C++ namespaces</H3> +<H3><a name="Java_namespaces">25.3.13 C++ namespaces</a></H3> <p> @@ -1948,7 +1948,7 @@ If the resulting use of the nspace feature and hence packages results in a proxy you will need to open up the visibility for the pointer constructor and <tt>getCPtr</tt> method from the default 'protected' to 'public' with the <tt>SWIG_JAVABODY_PROXY</tt> macro. See <a href="#Java_code_typemaps">Java code typemaps</a>. </p> -<H3><a name="Java_templates"></a>25.3.14 C++ templates</H3> +<H3><a name="Java_templates">25.3.14 C++ templates</a></H3> <p> @@ -1997,10 +1997,10 @@ Obviously, there is more to template wrapping than shown in this example. More details can be found in the <a href="SWIGPlus.html#SWIGPlus">SWIG and C++</a> chapter. </p> -<H3><a name="Java_smart_pointers"></a>25.3.15 C++ Smart Pointers</H3> +<H3><a name="Java_smart_pointers">25.3.15 C++ Smart Pointers</a></H3> -<H4><a name="Java_smart_pointers_shared_ptr"></a>25.3.15.1 The shared_ptr Smart Pointer</H4> +<H4><a name="Java_smart_pointers_shared_ptr">25.3.15.1 The shared_ptr Smart Pointer</a></H4> <p> @@ -2011,7 +2011,7 @@ in the <a href="Library.html#Library_std_shared_ptr">shared_ptr smart pointer</a </p> -<H4><a name="Java_smart_pointers_generic"></a>25.3.15.2 Generic Smart Pointers</H4> +<H4><a name="Java_smart_pointers_generic">25.3.15.2 Generic Smart Pointers</a></H4> <p> @@ -2095,7 +2095,7 @@ Foo f = p.__deref__(); // Returns underlying Foo * </pre> </div> -<H2><a name="Java_further_details"></a>25.4 Further details on the generated Java classes</H2> +<H2><a name="Java_further_details">25.4 Further details on the generated Java classes</a></H2> <p> @@ -2110,7 +2110,7 @@ Finally enum classes are covered. First, the crucial intermediary JNI class is considered. </p> -<H3><a name="Java_imclass"></a>25.4.1 The intermediary JNI class</H3> +<H3><a name="Java_imclass">25.4.1 The intermediary JNI class</a></H3> <p> @@ -2230,7 +2230,7 @@ If <tt>name</tt> is the same as <tt>modulename</tt> then the module class name g from <tt>modulename</tt> to <tt>modulenameModule</tt>. </p> -<H4><a name="Java_imclass_pragmas"></a>25.4.1.1 The intermediary JNI class pragmas</H4> +<H4><a name="Java_imclass_pragmas">25.4.1.1 The intermediary JNI class pragmas</a></H4> <p> @@ -2312,7 +2312,7 @@ For example, let's change the intermediary JNI class access to just the default All the methods in the intermediary JNI class will then not be callable outside of the package as the method modifiers have been changed from public access to default access. This is useful if you want to prevent users calling these low level functions. </p> -<H3><a name="Java_module_class"></a>25.4.2 The Java module class</H3> +<H3><a name="Java_module_class">25.4.2 The Java module class</a></H3> <p> @@ -2343,7 +2343,7 @@ example.egg(new Foo()); The primary reason for having the module class wrapping the calls in the intermediary JNI class is to implement static type checking. In this case only a <tt>Foo</tt> can be passed to the <tt>egg</tt> function, whereas any <tt>long</tt> can be passed to the <tt>egg</tt> function in the intermediary JNI class. </p> -<H4><a name="Java_module_class_pragmas"></a>25.4.2.1 The Java module class pragmas</H4> +<H4><a name="Java_module_class_pragmas">25.4.2.1 The Java module class pragmas</a></H4> <p> @@ -2394,7 +2394,7 @@ See <a href="#Java_imclass_pragmas">The intermediary JNI class pragmas</a> secti </p> -<H3><a name="Java_proxy_classes"></a>25.4.3 Java proxy classes</H3> +<H3><a name="Java_proxy_classes">25.4.3 Java proxy classes</a></H3> <p> @@ -2470,7 +2470,7 @@ int y = f.spam(5, new Foo()); </pre> </div> -<H4><a name="Java_memory_management"></a>25.4.3.1 Memory management</H4> +<H4><a name="Java_memory_management">25.4.3.1 Memory management</a></H4> <p> @@ -2632,7 +2632,7 @@ and </p> -<H4><a name="Java_inheritance_mirroring"></a>25.4.3.2 Inheritance</H4> +<H4><a name="Java_inheritance_mirroring">25.4.3.2 Inheritance</a></H4> <p> @@ -2748,7 +2748,7 @@ However, true cross language polymorphism can be achieved using the <a href="#Ja </p> -<H4><a name="Java_proxy_classes_gc"></a>25.4.3.3 Proxy classes and garbage collection</H4> +<H4><a name="Java_proxy_classes_gc">25.4.3.3 Proxy classes and garbage collection</a></H4> <p> @@ -2831,7 +2831,7 @@ The section on <a href="#Java_typemaps">Java typemaps</a> details how to specify See the <a href="http://www.devx.com/Java/Article/30192">How to Handle Java Finalization's Memory-Retention Issues</a> article for alternative approaches to managing memory by avoiding finalizers altogether. </p> -<H4><a name="Java_pgcpp"></a>25.4.3.4 The premature garbage collection prevention parameter for proxy class marshalling</H4> +<H4><a name="Java_pgcpp">25.4.3.4 The premature garbage collection prevention parameter for proxy class marshalling</a></H4> <p> @@ -2953,7 +2953,7 @@ For example: <b>Compatibility note:</b> The generation of this additional parameter did not occur in versions prior to SWIG-1.3.30. </p> -<H4><a name="Java_multithread_libraries"></a>25.4.3.5 Single threaded applications and thread safety</H4> +<H4><a name="Java_multithread_libraries">25.4.3.5 Single threaded applications and thread safety</a></H4> <p> @@ -3041,7 +3041,7 @@ for (int i=0; i<100000; i++) { </pre></div> -<H3><a name="Java_type_wrapper_classes"></a>25.4.4 Type wrapper classes</H3> +<H3><a name="Java_type_wrapper_classes">25.4.4 Type wrapper classes</a></H3> <p> @@ -3128,7 +3128,7 @@ public static void spam(SWIGTYPE_p_int x, SWIGTYPE_p_int y, int z) { ... } </div> -<H3><a name="Java_enum_classes"></a>25.4.5 Enum classes</H3> +<H3><a name="Java_enum_classes">25.4.5 Enum classes</a></H3> <p> @@ -3137,7 +3137,7 @@ The <a href="#Java_enumerations">Enumerations</a> section discussed these but om The following sub-sections detail the various types of enum classes that can be generated. </p> -<H4><a name="Java_typesafe_enums_classes"></a>25.4.5.1 Typesafe enum classes</H4> +<H4><a name="Java_typesafe_enums_classes">25.4.5.1 Typesafe enum classes</a></H4> <p> @@ -3221,7 +3221,7 @@ The <tt>swigValue</tt> method is used for marshalling in the other direction. The <tt>toString</tt> method is overridden so that the enum name is available. </p> -<H4><a name="Java_proper_enums_classes"></a>25.4.5.2 Proper Java enum classes</H4> +<H4><a name="Java_proper_enums_classes">25.4.5.2 Proper Java enum classes</a></H4> <p> @@ -3299,7 +3299,7 @@ These needn't be generated if the enum being wrapped does not have any initializ <a href="#Java_simpler_enum_classes">Simpler Java enums for enums without initializers</a> section describes how typemaps can be used to achieve this. </p> -<H4><a name="Java_typeunsafe_enums_classes"></a>25.4.5.3 Type unsafe enum classes</H4> +<H4><a name="Java_typeunsafe_enums_classes">25.4.5.3 Type unsafe enum classes</a></H4> <p> @@ -3330,7 +3330,7 @@ public final class Beverage { </pre> </div> -<H2><a name="Java_directors"></a>25.5 Cross language polymorphism using directors</H2> +<H2><a name="Java_directors">25.5 Cross language polymorphism using directors</a></H2> <p> @@ -3352,7 +3352,7 @@ The upshot is that C++ classes can be extended in Java and from C++ these extens Neither C++ code nor Java code needs to know where a particular method is implemented: the combination of proxy classes, director classes, and C wrapper functions transparently takes care of all the cross-language method routing. </p> -<H3><a name="Java_enabling_directors"></a>25.5.1 Enabling directors</H3> +<H3><a name="Java_enabling_directors">25.5.1 Enabling directors</a></H3> <p> @@ -3420,7 +3420,7 @@ public: </pre> </div> -<H3><a name="Java_directors_classes"></a>25.5.2 Director classes</H3> +<H3><a name="Java_directors_classes">25.5.2 Director classes</a></H3> <p> @@ -3447,7 +3447,7 @@ If the correct implementation is in Java, the Java API is used to call the metho </p> -<H3><a name="Java_directors_overhead"></a>25.5.3 Overhead and code bloat</H3> +<H3><a name="Java_directors_overhead">25.5.3 Overhead and code bloat</a></H3> <p> @@ -3465,7 +3465,7 @@ This situation can be optimized by selectively enabling director methods (using </p> -<H3><a name="Java_directors_example"></a>25.5.4 Simple directors example</H3> +<H3><a name="Java_directors_example">25.5.4 Simple directors example</a></H3> <p> @@ -3530,7 +3530,7 @@ DirectorDerived::upcall_method() invoked. </pre> </div> -<H3><a name="Java_directors_threading"></a>25.5.5 Director threading issues</H3> +<H3><a name="Java_directors_threading">25.5.5 Director threading issues</a></H3> <p> @@ -3550,7 +3550,7 @@ Macros can be defined on the commandline when compiling your C++ code, or altern </pre> </div> -<H3><a name="Java_directors_performance"></a>25.5.6 Director performance tuning</H3> +<H3><a name="Java_directors_performance">25.5.6 Director performance tuning</a></H3> <p> @@ -3571,7 +3571,7 @@ However, if all director methods are expected to usually be overridden by Java s The disadvantage is that invocation of director methods from C++ when Java doesn't actually override the method will require an additional call up into Java and back to C++. As such, this option is only useful when overrides are extremely common and instantiation is frequent enough that its performance is critical. </p> -<H3><a name="Java_exceptions_from_directors"></a>25.5.7 Java exceptions from directors</H3> +<H3><a name="Java_exceptions_from_directors">25.5.7 Java exceptions from directors</a></H3> <p> @@ -3879,7 +3879,7 @@ See the <a href="#Java_exception_handling">Exception handling with %exception an section for more on converting C++ exceptions to Java exceptions. </p> -<H2><a name="Java_allprotected"></a>25.6 Accessing protected members</H2> +<H2><a name="Java_allprotected">25.6 Accessing protected members</a></H2> <p> @@ -3975,7 +3975,7 @@ class MyProtectedBase extends ProtectedBase -<H2><a name="Java_common_customization"></a>25.7 Common customization features</H2> +<H2><a name="Java_common_customization">25.7 Common customization features</a></H2> <p> @@ -3987,7 +3987,7 @@ be awkward. This section describes some common SWIG features that are used to improve the interface to existing C/C++ code. </p> -<H3><a name="Java_helper_functions"></a>25.7.1 C/C++ helper functions</H3> +<H3><a name="Java_helper_functions">25.7.1 C/C++ helper functions</a></H3> <p> @@ -4053,7 +4053,7 @@ hard to implement. It is possible to improve on this using Java code, typemaps, customization features as covered in later sections, but sometimes helper functions are a quick and easy solution to difficult cases. </p> -<H3><a name="Java_class_extension"></a>25.7.2 Class extension with %extend</H3> +<H3><a name="Java_class_extension">25.7.2 Class extension with %extend</a></H3> <p> @@ -4116,7 +4116,7 @@ Vector(2,3,4) in any way---the extensions only show up in the Java interface. </p> -<H3><a name="Java_exception_handling"></a>25.7.3 Exception handling with %exception and %javaexception</H3> +<H3><a name="Java_exception_handling">25.7.3 Exception handling with %exception and %javaexception</a></H3> <p> @@ -4275,7 +4275,7 @@ to raise exceptions. See the <a href="Library.html#Library">SWIG Library</a> ch The typemap example <a href="#Java_exception_typemap">Handling C++ exception specifications as Java exceptions</a> provides further exception handling capabilities. </p> -<H3><a name="Java_method_access"></a>25.7.4 Method access with %javamethodmodifiers</H3> +<H3><a name="Java_method_access">25.7.4 Method access with %javamethodmodifiers</a></H3> <p> @@ -4301,7 +4301,7 @@ protected static void protect_me() { </pre> </div> -<H2><a name="Java_tips_techniques"></a>25.8 Tips and techniques</H2> +<H2><a name="Java_tips_techniques">25.8 Tips and techniques</a></H2> <p> @@ -4311,7 +4311,7 @@ strings and arrays. This chapter discusses the common techniques for solving these problems. </p> -<H3><a name="Java_input_output_parameters"></a>25.8.1 Input and output parameters using primitive pointers and references</H3> +<H3><a name="Java_input_output_parameters">25.8.1 Input and output parameters using primitive pointers and references</a></H3> <p> @@ -4485,7 +4485,7 @@ void foo(Bar *OUTPUT); will not have the intended effect since <tt>typemaps.i</tt> does not define an OUTPUT rule for <tt>Bar</tt>. </p> -<H3><a name="Java_simple_pointers"></a>25.8.2 Simple pointers</H3> +<H3><a name="Java_simple_pointers">25.8.2 Simple pointers</a></H3> <p> @@ -4551,7 +4551,7 @@ System.out.println("3 + 4 = " + result); See the <a href="Library.html#Library">SWIG Library</a> chapter for further details. </p> -<H3><a name="Java_c_arrays"></a>25.8.3 Wrapping C arrays with Java arrays</H3> +<H3><a name="Java_c_arrays">25.8.3 Wrapping C arrays with Java arrays</a></H3> <p> @@ -4618,7 +4618,7 @@ Please be aware that the typemaps in this library are not efficient as all the e There is an alternative approach using the SWIG array library and this is covered in the next section. </p> -<H3><a name="Java_unbounded_c_arrays"></a>25.8.4 Unbounded C Arrays</H3> +<H3><a name="Java_unbounded_c_arrays">25.8.4 Unbounded C Arrays</a></H3> <p> @@ -4763,7 +4763,7 @@ well suited for applications in which you need to create buffers, package binary data, etc. </p> -<H3><a name="Java_binary_char"></a>25.8.5 Binary data vs Strings</H3> +<H3><a name="Java_binary_char">25.8.5 Binary data vs Strings</a></H3> <p> @@ -4807,7 +4807,7 @@ len: 5 data: 68 69 0 6a 6b </pre></div> -<H3><a name="Java_heap_allocations"></a>25.8.6 Overriding new and delete to allocate from Java heap</H3> +<H3><a name="Java_heap_allocations">25.8.6 Overriding new and delete to allocate from Java heap</a></H3> <p> @@ -4924,7 +4924,7 @@ model and use these functions in place of malloc and free in your own code. </p> -<H2><a name="Java_typemaps"></a>25.9 Java typemaps</H2> +<H2><a name="Java_typemaps">25.9 Java typemaps</a></H2> <p> @@ -4945,7 +4945,7 @@ Before proceeding, it should be stressed that typemaps are not a required part of using SWIG---the default wrapping behavior is enough in most cases. Typemaps are only used if you want to change some aspect of the generated code. -<H3><a name="Java_default_primitive_type_mappings"></a>25.9.1 Default primitive type mappings</H3> +<H3><a name="Java_default_primitive_type_mappings">25.9.1 Default primitive type mappings</a></H3> <p> @@ -5097,7 +5097,7 @@ However, the mappings allow the full range of values for each C type from Java. </p> -<H3><a name="Java_default_non_primitive_typemaps"></a>25.9.2 Default typemaps for non-primitive types</H3> +<H3><a name="Java_default_non_primitive_typemaps">25.9.2 Default typemaps for non-primitive types</a></H3> <p> @@ -5112,7 +5112,7 @@ So in summary, the C/C++ pointer to non-primitive types is cast into the 64 bit The Java type is either the proxy class or type wrapper class. </p> -<H3><a name="Java_jvm64"></a>25.9.3 Sixty four bit JVMs</H3> +<H3><a name="Java_jvm64">25.9.3 Sixty four bit JVMs</a></H3> <p> @@ -5125,7 +5125,7 @@ Unfortunately it won't of course hold true for JNI code. </p> -<H3><a name="Java_what_is_typemap"></a>25.9.4 What is a typemap?</H3> +<H3><a name="Java_what_is_typemap">25.9.4 What is a typemap?</a></H3> <p> @@ -5248,7 +5248,7 @@ int c = example.count('e',"Hello World"); </pre> </div> -<H3><a name="Java_typemaps_c_to_java_types"></a>25.9.5 Typemaps for mapping C/C++ types to Java types</H3> +<H3><a name="Java_typemaps_c_to_java_types">25.9.5 Typemaps for mapping C/C++ types to Java types</a></H3> <p> @@ -5517,7 +5517,7 @@ These are listed below: </table> -<H3><a name="Java_typemap_attributes"></a>25.9.6 Java typemap attributes</H3> +<H3><a name="Java_typemap_attributes">25.9.6 Java typemap attributes</a></H3> <p> @@ -5563,7 +5563,7 @@ The "javain" typemap has the optional 'pre', 'post' and 'pgcppname' attributes. Note that when the 'pre' or 'post' attributes are specified and the associated type is used in a constructor, a constructor helper function is generated. This is necessary as the Java proxy constructor wrapper makes a call to a support constructor using a <i>this</i> call. In Java the <i>this</i> call must be the first statement in the constructor body. The constructor body thus calls the helper function and the helper function instead makes the JNI call, ensuring the 'pre' code is called before the JNI call is made. There is a <a href="#Java_date_marshalling">Date marshalling</a> example showing 'pre', 'post' and 'pgcppname' attributes in action. </p> -<H3><a name="Java_special_variables"></a>25.9.7 Java special variables</H3> +<H3><a name="Java_special_variables">25.9.7 Java special variables</a></H3> <p> @@ -5714,7 +5714,7 @@ This special variable expands to the intermediary class name. Usually this is th unless the jniclassname attribute is specified in the <a href="Java.html#Java_module_directive">%module directive</a>. </p> -<H3><a name="Java_typemaps_for_c_and_cpp"></a>25.9.8 Typemaps for both C and C++ compilation</H3> +<H3><a name="Java_typemaps_for_c_and_cpp">25.9.8 Typemaps for both C and C++ compilation</a></H3> <p> @@ -5751,7 +5751,7 @@ If you do not intend your code to be targeting both C and C++ then your typemaps </p> -<H3><a name="Java_code_typemaps"></a>25.9.9 Java code typemaps</H3> +<H3><a name="Java_code_typemaps">25.9.9 Java code typemaps</a></H3> <p> @@ -5989,7 +5989,7 @@ to make the method and constructor public: </pre> </div> -<H3><a name="Java_directors_typemaps"></a>25.9.10 Director specific typemaps</H3> +<H3><a name="Java_directors_typemaps">25.9.10 Director specific typemaps</a></H3> <p> @@ -6253,7 +6253,7 @@ The basic strategy here is to provide a default package typemap for the majority </div> -<H2><a name="Java_typemap_examples"></a>25.10 Typemap Examples</H2> +<H2><a name="Java_typemap_examples">25.10 Typemap Examples</a></H2> <p> @@ -6263,7 +6263,7 @@ the SWIG library. </p> -<H3><a name="Java_simpler_enum_classes"></a>25.10.1 Simpler Java enums for enums without initializers</H3> +<H3><a name="Java_simpler_enum_classes">25.10.1 Simpler Java enums for enums without initializers</a></H3> <p> @@ -6342,7 +6342,7 @@ This would be done by using the original versions of these typemaps in "enums.sw </p> -<H3><a name="Java_exception_typemap"></a>25.10.2 Handling C++ exception specifications as Java exceptions</H3> +<H3><a name="Java_exception_typemap">25.10.2 Handling C++ exception specifications as Java exceptions</a></H3> <p> @@ -6467,7 +6467,7 @@ We could alternatively have used <tt>%rename</tt> to rename <tt>what()</tt> into </p> -<H3><a name="Java_nan_exception_typemap"></a>25.10.3 NaN Exception - exception handling for a particular type</H3> +<H3><a name="Java_nan_exception_typemap">25.10.3 NaN Exception - exception handling for a particular type</a></H3> <p> @@ -6622,7 +6622,7 @@ If we were a martyr to the JNI cause, we could replace the succinct code within If we had, we would have put it in the "in" typemap which, like all JNI and Java typemaps, also supports the 'throws' attribute. </p> -<H3><a name="Java_converting_java_string_arrays"></a>25.10.4 Converting Java String arrays to char ** </H3> +<H3><a name="Java_converting_java_string_arrays">25.10.4 Converting Java String arrays to char ** </a></H3> <p> @@ -6766,7 +6766,7 @@ Lastly the "jni", "jtype" and "jstype" typemaps are also required to specify what Java types to use. </p> -<H3><a name="Java_expanding_java_object"></a>25.10.5 Expanding a Java object to multiple arguments</H3> +<H3><a name="Java_expanding_java_object">25.10.5 Expanding a Java object to multiple arguments</a></H3> <p> @@ -6848,7 +6848,7 @@ example.foo(new String[]{"red", "green", "blue", "white"}); </div> -<H3><a name="Java_using_typemaps_return_arguments"></a>25.10.6 Using typemaps to return arguments</H3> +<H3><a name="Java_using_typemaps_return_arguments">25.10.6 Using typemaps to return arguments</a></H3> <p> @@ -6966,7 +6966,7 @@ $ java runme 1 12.0 340.0 </pre></div> -<H3><a name="Java_adding_downcasts"></a>25.10.7 Adding Java downcasts to polymorphic return types</H3> +<H3><a name="Java_adding_downcasts">25.10.7 Adding Java downcasts to polymorphic return types</a></H3> <p> @@ -7172,7 +7172,7 @@ SWIG usually generates code which constructs the proxy classes using Java code a Note that the JNI code above uses a number of string lookups to call a constructor, whereas this would not occur using byte compiled Java code. </p> -<H3><a name="Java_adding_equals_method"></a>25.10.8 Adding an equals method to the Java classes</H3> +<H3><a name="Java_adding_equals_method">25.10.8 Adding an equals method to the Java classes</a></H3> <p> @@ -7216,7 +7216,7 @@ System.out.println("foo1? " + foo1.equals(foo2)); </div> -<H3><a name="Java_void_pointers"></a>25.10.9 Void pointers and a common Java base class</H3> +<H3><a name="Java_void_pointers">25.10.9 Void pointers and a common Java base class</a></H3> <p> @@ -7275,7 +7275,7 @@ This example contains some useful functionality which you may want in your code. <li> It also has a function which effectively implements a cast from the type of the proxy/type wrapper class to a void pointer. This is necessary for passing a proxy class or a type wrapper class to a function that takes a void pointer. </ul> -<H3><a name="Java_struct_pointer_pointer"></a>25.10.10 Struct pointer to pointer</H3> +<H3><a name="Java_struct_pointer_pointer">25.10.10 Struct pointer to pointer</a></H3> <p> @@ -7455,7 +7455,7 @@ The C functional interface has been completely morphed into an object-oriented i the Butler class would behave much like any pure Java class and feel more natural to Java users. </p> -<H3><a name="Java_memory_management_member_variables"></a>25.10.11 Memory management when returning references to member variables</H3> +<H3><a name="Java_memory_management_member_variables">25.10.11 Memory management when returning references to member variables</a></H3> <p> @@ -7578,7 +7578,7 @@ public class Bike { Note the <tt>addReference</tt> call. </p> -<H3><a name="Java_memory_management_objects"></a>25.10.12 Memory management for objects passed to the C++ layer</H3> +<H3><a name="Java_memory_management_objects">25.10.12 Memory management for objects passed to the C++ layer</a></H3> <p> @@ -7694,7 +7694,7 @@ The 'javacode' typemap simply adds in the specified code into the Java proxy cla </div> -<H3><a name="Java_date_marshalling"></a>25.10.13 Date marshalling using the javain typemap and associated attributes</H3> +<H3><a name="Java_date_marshalling">25.10.13 Date marshalling using the javain typemap and associated attributes</a></H3> <p> @@ -7871,7 +7871,7 @@ A few things to note: -<H2><a name="Java_directors_faq"></a>25.11 Living with Java Directors</H2> +<H2><a name="Java_directors_faq">25.11 Living with Java Directors</a></H2> <p> @@ -8052,10 +8052,10 @@ public abstract class UserVisibleFoo extends Foo { </li> </ol> -<H2><a name="Java_odds_ends"></a>25.12 Odds and ends</H2> +<H2><a name="Java_odds_ends">25.12 Odds and ends</a></H2> -<H3><a name="Java_javadoc_comments"></a>25.12.1 JavaDoc comments</H3> +<H3><a name="Java_javadoc_comments">25.12.1 JavaDoc comments</a></H3> <p> @@ -8111,7 +8111,7 @@ public class Barmy { -<H3><a name="Java_functional_interface"></a>25.12.2 Functional interface without proxy classes</H3> +<H3><a name="Java_functional_interface">25.12.2 Functional interface without proxy classes</a></H3> <p> @@ -8172,7 +8172,7 @@ All destructors have to be called manually for example the <tt>delete_Foo(foo)</ </p> -<H3><a name="Java_using_own_jni_functions"></a>25.12.3 Using your own JNI functions</H3> +<H3><a name="Java_using_own_jni_functions">25.12.3 Using your own JNI functions</a></H3> <p> @@ -8222,7 +8222,7 @@ This directive is only really useful if you want to mix your own hand crafted JN </p> -<H3><a name="Java_performance"></a>25.12.4 Performance concerns and hints</H3> +<H3><a name="Java_performance">25.12.4 Performance concerns and hints</a></H3> <p> @@ -8243,7 +8243,7 @@ However, you will have to be careful about memory management and make sure that This method normally calls the C++ destructor or <tt>free()</tt> for C code. </p> -<H3><a name="Java_debugging"></a>25.12.5 Debugging</H3> +<H3><a name="Java_debugging">25.12.5 Debugging</a></H3> <p> @@ -8265,7 +8265,7 @@ The -verbose:jni and -verbose:gc are also useful options for monitoring code beh </p> -<H2><a name="Java_examples"></a>25.13 Java Examples</H2> +<H2><a name="Java_examples">25.13 Java Examples</a></H2> <p> diff --git a/Doc/Manual/Javascript.html b/Doc/Manual/Javascript.html index 69e6665ea..a3b6cf0c5 100644 --- a/Doc/Manual/Javascript.html +++ b/Doc/Manual/Javascript.html @@ -6,7 +6,7 @@ </head> <body> -<H1><a name="Javascript"></a>26 SWIG and Javascript</H1> +<H1><a name="Javascript">26 SWIG and Javascript</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -51,7 +51,7 @@ <p>This chapter describes SWIG's support of Javascript. It does not cover SWIG basics, but only information that is specific to this module.</p> -<H2><a name="Javascript_overview"></a>26.1 Overview</H2> +<H2><a name="Javascript_overview">26.1 Overview</a></H2> <p>Javascript is a prototype-based scripting language that is dynamic, weakly typed and has first-class functions. Its arguably the most popular language for web development. @@ -62,10 +62,10 @@ Javascript has gone beyond being a browser-based scripting language and with <a With <a href="https://github.com/rogerwang/node-webkit">node-webkit</a> there is a platform which uses Google's <code>Chromium</code> as Web-Browser widget and <code>node.js</code> for javascript extensions. </p> -<H2><a name="Javascript_preliminaries"></a>26.2 Preliminaries</H2> +<H2><a name="Javascript_preliminaries">26.2 Preliminaries</a></H2> -<H3><a name="Javascript_running_swig"></a>26.2.1 Running SWIG</H3> +<H3><a name="Javascript_running_swig">26.2.1 Running SWIG</a></H3> <p>Suppose that you defined a SWIG module such as the following:</p> @@ -109,7 +109,7 @@ void example_initialize(v8::Handle<v8::Object> exports)</pre> <b>Note</b>: be aware that <code>v8</code> has a C++ API, and thus, the generated modules must be compiled as C++. </p> -<H3><a name="Javascript_running_tests_examples"></a>26.2.2 Running Tests and Examples</H3> +<H3><a name="Javascript_running_tests_examples">26.2.2 Running Tests and Examples</a></H3> <p>The configuration for tests and examples currently supports Linux and Mac only and not MinGW (Windows) yet.</p> @@ -141,7 +141,7 @@ $ make check-javascript-test-suite ENGINE=jsc</pre> $ make check-javascript-examples V8_VERSION=0x032530 ENGINE=v8</pre> </div> -<H3><a name="Javascript_known_issues"></a>26.2.3 Known Issues</H3> +<H3><a name="Javascript_known_issues">26.2.3 Known Issues</a></H3> <p>At the moment, the Javascript generators pass all tests syntactically, i.e., the generated source code compiles. However, there are still remaining runtime issues.</p> @@ -158,12 +158,12 @@ $ make check-javascript-examples V8_VERSION=0x032530 ENGINE=v8</pre> <p>The primary development environment has been Linux (Ubuntu 12.04). Windows and Mac OS X have been tested sporadically. Therefore, the generators might have more issues on those platforms. Please report back any problem you observe to help us improving this module quickly.</p> -<H2><a name="Javascript_integration"></a>26.3 Integration</H2> +<H2><a name="Javascript_integration">26.3 Integration</a></H2> <p>This chapter gives a short introduction how to use a native Javascript extension: as a <code>node.js</code> module, and as an extension for an embedded Webkit.</p> -<H3><a name="Javascript_node_extensions"></a>26.3.1 Creating node.js Extensions</H3> +<H3><a name="Javascript_node_extensions">26.3.1 Creating node.js Extensions</a></H3> <p>To install <code>node.js</code> you can download an installer from their <a href="https://launchpad.net/~chris-lea/+archive/node.js">web-site</a> for Mac OS X and Windows. For Linux you can either build the source yourself and run <code>sudo checkinstall</code> or keep to the (probably stone-age) packaged version. For Ubuntu there is a <a href="https://launchpad.net/~chris-lea/+archive/ubuntu/node.js/">PPA</a> available.</p> @@ -209,7 +209,7 @@ require("./build/Release/example")</pre> </div> <p>A more detailed explanation is given in the <a href="#Javascript_examples">Examples</a> section.</p> -<H4><a name="Javascript_troubleshooting"></a>26.3.1.1 Troubleshooting</H4> +<H4><a name="Javascript_troubleshooting">26.3.1.1 Troubleshooting</a></H4> <ul> @@ -221,12 +221,12 @@ require("./build/Release/example")</pre> $ sudo apt-get remove gyp</pre> </div> -<H3><a name="Javascript_embedded_webkit"></a>26.3.2 Embedded Webkit</H3> +<H3><a name="Javascript_embedded_webkit">26.3.2 Embedded Webkit</a></H3> <p>Webkit is pre-installed on Mac OS X and available as a library for GTK.</p> -<H4><a name="Javascript_osx"></a>26.3.2.1 Mac OS X</H4> +<H4><a name="Javascript_osx">26.3.2.1 Mac OS X</a></H4> <p>There is general information about programming with WebKit on <a href="https://developer.apple.com/library/mac/documentation/cocoa/conceptual/DisplayWebContent/DisplayWebContent.html">Apple Developer Documentation</a>. Details about <code>Cocoa</code> programming are not covered here.</p> @@ -274,7 +274,7 @@ extern bool example_initialize(JSGlobalContextRef context, JSObjectRef* exports) @end</pre> </div> -<H4><a name="Javascript_gtk"></a>26.3.2.2 GTK</H4> +<H4><a name="Javascript_gtk">26.3.2.2 GTK</a></H4> <p>There is general information about programming GTK at <a href="https://developer.gnome.org/gtk2/">GTK documentation</a> and in the <a href="https://developer.gnome.org/gtk-tutorial">GTK tutorial</a>, and for Webkit there is a <a href="http://webkitgtk.org/reference/webkitgtk/stable/index.html">Webkit GTK+ API Reference</a>.</p> @@ -319,7 +319,7 @@ int main(int argc, char* argv[]) }</pre> </div> -<H3><a name="Javascript_applications_webkit"></a>26.3.3 Creating Applications with node-webkit</H3> +<H3><a name="Javascript_applications_webkit">26.3.3 Creating Applications with node-webkit</a></H3> <p>To get started with <code>node-webkit</code> there is a very informative set of <a href="https://github.com/rogerwang/node-webkit/wiki">wiki pages</a>.</p> @@ -410,12 +410,12 @@ open new windows, and many more things. };</pre> </div> -<H2><a name="Javascript_examples"></a>26.4 Examples</H2> +<H2><a name="Javascript_examples">26.4 Examples</a></H2> <p>Some basic examples are shown here in more detail.</p> -<H3><a name="Javascript_simple_example"></a>26.4.1 Simple</H3> +<H3><a name="Javascript_simple_example">26.4.1 Simple</a></H3> <p>The common example <code>simple</code> looks like this:</p> @@ -465,7 +465,7 @@ example.Foo = 3.1415926;</pre> <p><b>Note</b>: ECMAScript 5, the currently implemented Javascript standard, does not have modules. <code>node.js</code> and other implementations provide this mechanism defined by the <a href="http://wiki.commonjs.org/wiki/CommonJS">CommonJS</a> group. For browsers this is provided by <a href="http://browserify.org">Browserify</a>, for instance.</p> -<H3><a name="Javascript_class_example"></a>26.4.2 Class</H3> +<H3><a name="Javascript_class_example">26.4.2 Class</a></H3> <p>The common example <code>class</code> defines three classes, <code>Shape</code>, <code>Circle</code>, and <code>Square</code>:</p> @@ -595,12 +595,12 @@ at emitKey (readline.js:1095:12)</pre> <b>Note</b>: In ECMAScript 5 there is no concept for classes. Instead each function can be used as a constructor function which is executed by the 'new' operator. Furthermore, during construction the key property <code>prototype</code> of the constructor function is used to attach a prototype instance to the created object. A prototype is essentially an object itself that is the first-class delegate of a class used whenever the access to a property of an object fails. The very same prototype instance is shared among all instances of one type. Prototypal inheritance is explained in more detail on in <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Inheritance_and_the_prototype_chain">Inheritance and the prototype chain</a>, for instance. </p> -<H2><a name="Javascript_implementation"></a>26.5 Implementation</H2> +<H2><a name="Javascript_implementation">26.5 Implementation</a></H2> <p>The Javascript Module implementation has taken a very different approach compared to other language modules in order to support different Javascript interpreters.</p> -<H3><a name="Javascript_source_code"></a>26.5.1 Source Code</H3> +<H3><a name="Javascript_source_code">26.5.1 Source Code</a></H3> <p>The Javascript module is implemented in <code>Source/Modules/javascript.cxx</code>. It dispatches the code generation to a <code>JSEmitter</code> instance, <code>V8Emitter</code> or <code>JSCEmitter</code>. Additionally there are some helpers: <code>Template</code>, for templated code generation, and <code>JSEmitterState</code>, which is used to manage state information during AST traversal. This rough map shall make it easier to find a way through this huge source file:</p> @@ -701,7 +701,7 @@ Template::Template(const String *code_) { ... } ...</pre> </div> -<H3><a name="Javascript_code_templates"></a>26.5.2 Code Templates</H3> +<H3><a name="Javascript_code_templates">26.5.2 Code Templates</a></H3> <p>All generated code is created on the basis of code templates. The templates for <em>JavascriptCore</em> can be found in <code>Lib/javascript/jsc/javascriptcode.swg</code>, for <em>v8</em> in <code>Lib/javascript/v8/javascriptcode.swg</code>.</p> @@ -740,7 +740,7 @@ t_register.replace("$jsparent", state.clazz(NAME_MANGLED)) </div> <p><code>Template</code> creates a copy of that string and <code>Template::replace</code> uses Swig's <code>Replaceall</code> to replace variables in the template. <code>Template::trim</code> can be used to eliminate leading and trailing whitespaces. <code>Template::print</code> is used to write the final template string to a Swig <code>DOH</code> (based on <code>Printv</code>). All methods allow chaining.</p> -<H3><a name="Javascript_emitter"></a>26.5.3 Emitter</H3> +<H3><a name="Javascript_emitter">26.5.3 Emitter</a></H3> <p>The Javascript module delegates code generation to a <code>JSEmitter</code> instance. The following extract shows the essential interface:</p> @@ -859,7 +859,7 @@ int JAVASCRIPT::classHandler(Node *n) { </div> <p>In <code>enterClass</code> the emitter stores state information that is necessary when processing class members. In <code>exitClass</code> the wrapper code for the whole class is generated.</p> -<H3><a name="Javascript_emitter_states"></a>26.5.4 Emitter states</H3> +<H3><a name="Javascript_emitter_states">26.5.4 Emitter states</a></H3> <p>For storing information during the AST traversal the emitter provides a <code>JSEmitterState</code> with different slots to store data representing the scopes global, class, function, and variable.</p> @@ -903,7 +903,7 @@ state.clazz(NAME, Getattr(n, "sym:name"));</pre> <p>State information can be retrieved using <code>state.clazz(NAME)</code> or with <code>Getattr</code> on <code>state.clazz()</code> which actually returns a <code>Hash</code> instance.</p> -<H3><a name="Javascript_jsc_exceptions"></a>26.5.5 Handling Exceptions in JavascriptCore</H3> +<H3><a name="Javascript_jsc_exceptions">26.5.5 Handling Exceptions in JavascriptCore</a></H3> <p>Applications with an embedded JavascriptCore should be able to present detailed exception messages that occur in the Javascript engine. Below is an example derived from code provided by Brian Barnes on how these exception details can be extracted.</p> diff --git a/Doc/Manual/Library.html b/Doc/Manual/Library.html index fb12e3ce8..203ea6d46 100644 --- a/Doc/Manual/Library.html +++ b/Doc/Manual/Library.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Library"></a>9 SWIG library</H1> +<H1><a name="Library">9 SWIG library</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -59,7 +59,7 @@ Alternative libraries provide similar functionality. Please read this chapter carefully if you used the old libraries. </p> -<H2><a name="Library_nn2"></a>9.1 The %include directive and library search path</H2> +<H2><a name="Library_nn2">9.1 The %include directive and library search path</a></H2> <p> @@ -91,7 +91,7 @@ Set the environment variable to hold an alternative library directory. The directories that are searched are displayed when using <tt>-verbose</tt> commandline option. </p> -<H2><a name="Library_nn3"></a>9.2 C Arrays and Pointers</H2> +<H2><a name="Library_nn3">9.2 C Arrays and Pointers</a></H2> <p> @@ -103,7 +103,7 @@ pointers as class-like objects. Since these functions provide direct access to memory, their use is potentially unsafe and you should exercise caution. </p> -<H3><a name="Library_nn4"></a>9.2.1 cpointer.i</H3> +<H3><a name="Library_nn4">9.2.1 cpointer.i</a></H3> <p> @@ -319,7 +319,7 @@ In this example, the function <tt>int_to_uint()</tt> would be used to cast type <b>Note:</b> When working with simple pointers, typemaps can often be used to provide more seamless operation. </p> -<H3><a name="Library_carrays"></a>9.2.2 carrays.i</H3> +<H3><a name="Library_carrays">9.2.2 carrays.i</a></H3> <p> @@ -497,7 +497,7 @@ you should consider using a special array object rather than a bare pointer. used with types of <tt>char</tt> or <tt>char *</tt>. </p> -<H3><a name="Library_nn6"></a>9.2.3 cmalloc.i</H3> +<H3><a name="Library_nn6">9.2.3 cmalloc.i</a></H3> <p> @@ -658,7 +658,7 @@ Now, in a script: </pre> </div> -<H3><a name="Library_nn7"></a>9.2.4 cdata.i</H3> +<H3><a name="Library_nn7">9.2.4 cdata.i</a></H3> <p> @@ -760,7 +760,7 @@ char *cdata_<em>name</em>(type* ptr, int nitems) Clearly they are unsafe. </p> -<H2><a name="Library_nn8"></a>9.3 C String Handling</H2> +<H2><a name="Library_nn8">9.3 C String Handling</a></H2> <p> @@ -780,7 +780,7 @@ morality. The modules in this section provide basic functionality for manipulating raw C strings. </p> -<H3><a name="Library_nn9"></a>9.3.1 Default string handling</H3> +<H3><a name="Library_nn9">9.3.1 Default string handling</a></H3> <p> @@ -821,7 +821,7 @@ interpreter and lead to a crash). Furthermore, the default behavior does not work well with binary data. Instead, strings are assumed to be NULL-terminated. </p> -<H3><a name="Library_nn10"></a>9.3.2 Passing binary data</H3> +<H3><a name="Library_nn10">9.3.2 Passing binary data</a></H3> <p> @@ -863,7 +863,7 @@ In the wrapper function, the passed string will be expanded to a pointer and len The <tt>(char *STRING, int LENGTH)</tt> multi-argument typemap is also available in addition to <tt>(char *STRING, size_t LENGTH)</tt>. </p> -<H3><a name="Library_nn11"></a>9.3.3 Using %newobject to release memory</H3> +<H3><a name="Library_nn11">9.3.3 Using %newobject to release memory</a></H3> <p> @@ -904,7 +904,7 @@ however, you may need to provide your own "newfree" typemap for other types. See <a href="Customization.html#Customization_ownership">Object ownership and %newobject</a> for more details. </p> -<H3><a name="Library_nn12"></a>9.3.4 cstring.i</H3> +<H3><a name="Library_nn12">9.3.4 cstring.i</a></H3> <p> @@ -1364,7 +1364,7 @@ structure or class instead. </li> </ul> -<H2><a name="Library_stl_cpp_library"></a>9.4 STL/C++ Library</H2> +<H2><a name="Library_stl_cpp_library">9.4 STL/C++ Library</a></H2> <p> @@ -1403,7 +1403,7 @@ Please look for the library files in the appropriate language library directory. </p> -<H3><a name="Library_std_string"></a>9.4.1 std::string</H3> +<H3><a name="Library_std_string">9.4.1 std::string</a></H3> <p> @@ -1487,7 +1487,7 @@ void foo(string s, const String &t); // std_string typemaps still applie </pre> </div> -<H3><a name="Library_std_vector"></a>9.4.2 std::vector</H3> +<H3><a name="Library_std_vector">9.4.2 std::vector</a></H3> <p> @@ -1666,7 +1666,7 @@ if you want to make their head explode. details and the public API exposed to the interpreter vary. </p> -<H3><a name="Library_stl_exceptions"></a>9.4.3 STL exceptions</H3> +<H3><a name="Library_stl_exceptions">9.4.3 STL exceptions</a></H3> <p> @@ -1716,7 +1716,7 @@ The <tt>%exception</tt> directive can be used by placing the following code befo Any thrown STL exceptions will then be gracefully handled instead of causing a crash. </p> -<H3><a name="Library_std_shared_ptr"></a>9.4.4 shared_ptr smart pointer</H3> +<H3><a name="Library_std_shared_ptr">9.4.4 shared_ptr smart pointer</a></H3> <p> @@ -1907,7 +1907,7 @@ Please help to improve this support by providing patches with improvements. </p> -<H3><a name="Library_std_auto_ptr"></a>9.4.5 auto_ptr smart pointer</H3> +<H3><a name="Library_std_auto_ptr">9.4.5 auto_ptr smart pointer</a></H3> <p> @@ -1956,10 +1956,10 @@ int value = k.getValue(); </pre> </div> -<H2><a name="Library_nn16"></a>9.5 Utility Libraries</H2> +<H2><a name="Library_nn16">9.5 Utility Libraries</a></H2> -<H3><a name="Library_nn17"></a>9.5.1 exception.i</H3> +<H3><a name="Library_nn17">9.5.1 exception.i</a></H3> <p> diff --git a/Doc/Manual/Lisp.html b/Doc/Manual/Lisp.html index d2bf316a4..ccb424e50 100644 --- a/Doc/Manual/Lisp.html +++ b/Doc/Manual/Lisp.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Lisp"></a>27 SWIG and Common Lisp</H1> +<H1><a name="Lisp">27 SWIG and Common Lisp</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -41,7 +41,7 @@ Lisp, Common Foreign Function Interface(CFFI), CLisp and UFFI foreign function interfaces. </p> -<H2><a name="Lisp_nn2"></a>27.1 Allegro Common Lisp</H2> +<H2><a name="Lisp_nn2">27.1 Allegro Common Lisp</a></H2> <p> @@ -50,7 +50,7 @@ <a href="Allegrocl.html#Allegrocl">here</a> </p> -<H2><a name="Lisp_nn3"></a>27.2 Common Foreign Function Interface(CFFI)</H2> +<H2><a name="Lisp_nn3">27.2 Common Foreign Function Interface(CFFI)</a></H2> <p> @@ -77,7 +77,7 @@ swig -cffi -module <i>module-name</i> <i>file-name</i> files and the various things which you can do with them. </p> -<H3><a name="Lisp_nn4"></a>27.2.1 Additional Commandline Options </H3> +<H3><a name="Lisp_nn4">27.2.1 Additional Commandline Options </a></H3> <p> @@ -118,7 +118,7 @@ swig -cffi -help </table> -<H3><a name="Lisp_nn5"></a>27.2.2 Generating CFFI bindings</H3> +<H3><a name="Lisp_nn5">27.2.2 Generating CFFI bindings</a></H3> As we mentioned earlier the ideal way to use SWIG is to use interface @@ -395,7 +395,7 @@ The feature <i>intern_function</i> ensures that all C names are </pre></div> -<H3><a name="Lisp_nn6"></a>27.2.3 Generating CFFI bindings for C++ code</H3> +<H3><a name="Lisp_nn6">27.2.3 Generating CFFI bindings for C++ code</a></H3> <p>This feature to SWIG (for CFFI) is very new and still far from @@ -571,7 +571,7 @@ If you have any questions, suggestions, patches, etc., related to CFFI module feel free to contact us on the SWIG mailing list, and also please add a "[CFFI]" tag in the subject line. -<H3><a name="Lisp_nn7"></a>27.2.4 Inserting user code into generated files</H3> +<H3><a name="Lisp_nn7">27.2.4 Inserting user code into generated files</a></H3> <p> @@ -611,7 +611,7 @@ Note that the block <tt>%{ ... %}</tt> is effectively a shortcut for </p> -<H2><a name="Lisp_nn8"></a>27.3 CLISP</H2> +<H2><a name="Lisp_nn8">27.3 CLISP</a></H2> <p> @@ -641,7 +641,7 @@ swig -clisp -module <i>module-name</i> <i>file-name</i> interface file for the CLISP module. The CLISP module tries to produce code which is both human readable and easily modifyable. </p> -<H3><a name="Lisp_nn9"></a>27.3.1 Additional Commandline Options </H3> +<H3><a name="Lisp_nn9">27.3.1 Additional Commandline Options </a></H3> <p> @@ -674,7 +674,7 @@ and global variables will be created otherwise only definitions for<br/> </table> -<H3><a name="Lisp_nn10"></a>27.3.2 Details on CLISP bindings</H3> +<H3><a name="Lisp_nn10">27.3.2 Details on CLISP bindings</a></H3> <p> @@ -798,7 +798,7 @@ struct bar { </pre></div> -<H2><a name="Lisp_nn11"></a>27.4 UFFI </H2> +<H2><a name="Lisp_nn11">27.4 UFFI </a></H2> </body> diff --git a/Doc/Manual/Lua.html b/Doc/Manual/Lua.html index 2e1515c43..1b6b87e51 100644 --- a/Doc/Manual/Lua.html +++ b/Doc/Manual/Lua.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Lua"></a>28 SWIG and Lua</H1> +<H1><a name="Lua">28 SWIG and Lua</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -82,14 +82,14 @@ Lua is an extension programming language designed to support general procedural eLua stands for Embedded Lua (can be thought of as a flavor of Lua) and offers the full implementation of the Lua programming language to the embedded world, extending it with specific features for efficient and portable software embedded development. eLua runs on smaller devices like microcontrollers and provides the full features of the regular Lua desktop version. More information on eLua can be found here: <a href="http://www.eluaproject.net">http://www.eluaproject.net</a> </p> -<H2><a name="Lua_nn2"></a>28.1 Preliminaries</H2> +<H2><a name="Lua_nn2">28.1 Preliminaries</a></H2> <p> The current SWIG implementation is designed to work with Lua 5.0.x, 5.1.x and 5.2.x. It should work with later versions of Lua, but certainly not with Lua 4.0 due to substantial API changes. It is possible to either static link or dynamic link a Lua module into the interpreter (normally Lua static links its libraries, as dynamic linking is not available on all platforms). SWIG also has support for eLua starting from eLua 0.8. Due to substantial changes between SWIG 2.x and SWIG 3.0 and unavailability of testing platform, eLua status was downgraded to 'experimental'. </p> -<H2><a name="Lua_nn3"></a>28.2 Running SWIG</H2> +<H2><a name="Lua_nn3">28.2 Running SWIG</a></H2> <p> @@ -137,7 +137,7 @@ $ swig -lua -eluac example.i The <tt>-elua</tt> option puts all the C function wrappers and variable get/set wrappers in rotables. It also generates a metatable which will control the access to these variables from eLua. It also offers a significant amount of module size compression. On the other hand, the <tt>-eluac</tt> option puts all the wrappers in a single rotable. With this option, no matter how huge the module, it will consume no additional microcontroller SRAM (crass compression). There is a catch though: Metatables are not generated with <tt>-eluac</tt>. To access any value from eLua, one must directly call the wrapper function associated with that value. </p> -<H3><a name="Lua_commandline"></a>28.2.1 Additional command line options</H3> +<H3><a name="Lua_commandline">28.2.1 Additional command line options</a></H3> <p> @@ -178,7 +178,7 @@ swig -lua -help </tr> </table> -<H3><a name="Lua_nn4"></a>28.2.2 Compiling and Linking and Interpreter</H3> +<H3><a name="Lua_nn4">28.2.2 Compiling and Linking and Interpreter</a></H3> <p> @@ -249,7 +249,7 @@ LUALIB_API int ( luaopen_mod )(lua_State *L ); More information on building and configuring eLua can be found here: <a href="http://www.eluaproject.net/doc/v0.8/en_building.html">http://www.eluaproject.net/doc/v0.8/en_building.html</a> </p> -<H3><a name="Lua_nn5"></a>28.2.3 Compiling a dynamic module</H3> +<H3><a name="Lua_nn5">28.2.3 Compiling a dynamic module</a></H3> <p> @@ -317,7 +317,7 @@ Is quite obvious (Go back and consult the Lua documents on how to enable loadlib -<H3><a name="Lua_nn6"></a>28.2.4 Using your module</H3> +<H3><a name="Lua_nn6">28.2.4 Using your module</a></H3> <p> @@ -335,19 +335,19 @@ $ ./my_lua > </pre></div> -<H2><a name="Lua_nn7"></a>28.3 A tour of basic C/C++ wrapping</H2> +<H2><a name="Lua_nn7">28.3 A tour of basic C/C++ wrapping</a></H2> <p> By default, SWIG tries to build a very natural Lua interface to your C/C++ code. This section briefly covers the essential aspects of this wrapping. </p> -<H3><a name="Lua_nn8"></a>28.3.1 Modules</H3> +<H3><a name="Lua_nn8">28.3.1 Modules</a></H3> <p> The SWIG module directive specifies the name of the Lua module. If you specify `module example', then everything is wrapped into a Lua table 'example' containing all the functions and variables. When choosing a module name, make sure you don't use the same name as a built-in Lua command or standard module name. </p> -<H3><a name="Lua_nn9"></a>28.3.2 Functions</H3> +<H3><a name="Lua_nn9">28.3.2 Functions</a></H3> <p> @@ -388,7 +388,7 @@ It is also possible to rename the module with an assignment. 24 </pre></div> -<H3><a name="Lua_nn10"></a>28.3.3 Global variables</H3> +<H3><a name="Lua_nn10">28.3.3 Global variables</a></H3> <p> @@ -476,7 +476,7 @@ If you have used the <tt>-eluac</tt> option for your eLua module, you will have In general, functions of the form <tt>"variable_get()"</tt> and <tt>"variable_set()"</tt> are automatically generated by SWIG for use with <tt>-eluac</tt>. </p> -<H3><a name="Lua_nn11"></a>28.3.4 Constants and enums</H3> +<H3><a name="Lua_nn11">28.3.4 Constants and enums</a></H3> <p> @@ -511,7 +511,7 @@ If you're using eLua and have used <tt>-elua</tt> or <tt>-eluac</tt> to generate Hello World </pre></div> -<H4><a name="Lua_nn13"></a>28.3.4.1 Constants/enums and classes/structures</H4> +<H4><a name="Lua_nn13">28.3.4.1 Constants/enums and classes/structures</a></H4> <p> @@ -567,7 +567,7 @@ If the <tt>-no-old-metatable-bindings</tt> option is used, then these old-style It is worth mentioning, that <tt>example.Test.TEST1</tt> and <tt>example.Test_TEST1</tt> are different entities and changing one does not change the other. Given the fact that these are constantes and they are not supposed to be changed, it is up to you to avoid such issues. </p> -<H3><a name="Lua_nn12"></a>28.3.5 Pointers</H3> +<H3><a name="Lua_nn12">28.3.5 Pointers</a></H3> <p> @@ -605,7 +605,7 @@ Lua enforces the integrity of its userdata, so it is virtually impossible to cor nil </pre></div> -<H3><a name="Lua_structures"></a>28.3.6 Structures</H3> +<H3><a name="Lua_structures">28.3.6 Structures</a></H3> <p> @@ -709,7 +709,7 @@ For eLua with the <tt>-eluac</tt> option, structure manipulation has to be perfo In general, functions of the form <tt>"new_struct()"</tt>, <tt>"struct_member_get()"</tt>, <tt>"struct_member_set()"</tt> and <tt>"free_struct()"</tt> are automatically generated by SWIG for each structure defined in C. (Please note: This doesn't apply for modules generated with the <tt>-elua</tt> option) </p> -<H3><a name="Lua_nn14"></a>28.3.7 C++ classes</H3> +<H3><a name="Lua_nn14">28.3.7 C++ classes</a></H3> <p> @@ -784,7 +784,7 @@ Both style names are generated by default now. However, if the <tt>-no-old-metatable-bindings</tt> option is used, then the backward compatible names are not generated in addition to ordinary ones. </p> -<H3><a name="Lua_nn15"></a>28.3.8 C++ inheritance</H3> +<H3><a name="Lua_nn15">28.3.8 C++ inheritance</a></H3> <p> @@ -809,7 +809,7 @@ then the function <tt>spam()</tt> accepts a Foo pointer or a pointer to any clas <p> It is safe to use multiple inheritance with SWIG. </p> -<H3><a name="Lua_nn16"></a>28.3.9 Pointers, references, values, and arrays</H3> +<H3><a name="Lua_nn16">28.3.9 Pointers, references, values, and arrays</a></H3> <p> @@ -840,7 +840,7 @@ Foo spam7(); <p> then all three functions will return a pointer to some Foo object. Since the third function (spam7) returns a value, newly allocated memory is used to hold the result and a pointer is returned (Lua will release this memory when the return value is garbage collected). The other two are pointers which are assumed to be managed by the C code and so will not be garbage collected. </p> -<H3><a name="Lua_nn17"></a>28.3.10 C++ overloaded functions</H3> +<H3><a name="Lua_nn17">28.3.10 C++ overloaded functions</a></H3> <p> @@ -926,7 +926,7 @@ Please refer to the "SWIG and C++" chapter for more information about overloadin <p> Dealing with the Lua coercion mechanism, the priority is roughly (integers, floats, strings, userdata). But it is better to rename the functions rather than rely upon the ordering. </p> -<H3><a name="Lua_nn18"></a>28.3.11 C++ operators</H3> +<H3><a name="Lua_nn18">28.3.11 C++ operators</a></H3> <p> @@ -1060,7 +1060,7 @@ operators and pseudo-operators):</p> </ul> <p>No other lua metafunction is inherited. For example, __gc is not inherited and must be redefined in every class. <tt>__tostring</tt> is subject to a special handling. If absent in class and in class bases, a default one will be provided by SWIG. </p> -<H3><a name="Lua_nn19"></a>28.3.12 Class extension with %extend</H3> +<H3><a name="Lua_nn19">28.3.12 Class extension with %extend</a></H3> <p> @@ -1116,7 +1116,7 @@ true Extend works with both C and C++ code, on classes and structs. It does not modify the underlying object in any way---the extensions only show up in the Lua interface. The only item to take note of is the code has to use the '$self' instead of 'this', and that you cannot access protected/private members of the code (as you are not officially part of the class). </p> -<H3><a name="Lua_nn20"></a>28.3.13 Using %newobject to release memory</H3> +<H3><a name="Lua_nn20">28.3.13 Using %newobject to release memory</a></H3> <p> If you have a function that allocates memory like this,</p> @@ -1140,7 +1140,7 @@ char *foo(); </div> <p> This will release the allocated memory.</p> -<H3><a name="Lua_nn21"></a>28.3.14 C++ templates</H3> +<H3><a name="Lua_nn21">28.3.14 C++ templates</a></H3> <p> @@ -1175,7 +1175,7 @@ In Lua: <p> Obviously, there is more to template wrapping than shown in this example. More details can be found in the SWIG and C++ chapter. Some more complicated examples will appear later. </p> -<H3><a name="Lua_nn22"></a>28.3.15 C++ Smart Pointers</H3> +<H3><a name="Lua_nn22">28.3.15 C++ Smart Pointers</a></H3> <p> @@ -1227,7 +1227,7 @@ If you ever need to access the underlying pointer returned by <tt>operator->( > f = p:__deref__() -- Returns underlying Foo * </pre></div> -<H3><a name="Lua_nn23"></a>28.3.16 C++ Exceptions</H3> +<H3><a name="Lua_nn23">28.3.16 C++ Exceptions</a></H3> <p> @@ -1370,7 +1370,7 @@ and the "<a href="Customization.html#Customization_exception">Exception handling add exception specification to functions or globally (respectively). </p> -<H3><a name="Lua_namespaces"></a>28.3.17 Namespaces </H3> +<H3><a name="Lua_namespaces">28.3.17 Namespaces </a></H3> <p> @@ -1421,7 +1421,7 @@ Now, from Lua usage is as follows: 19 > </pre></div> -<H4><a name="Lua_nn27"></a>28.3.17.1 Compatibility Note </H4> +<H4><a name="Lua_nn27">28.3.17.1 Compatibility Note </a></H4> <p> @@ -1437,7 +1437,7 @@ If SWIG is running in a backwards compatible way, i.e. without the <tt>-no-old-m </pre></div> -<H4><a name="Lua_nn29"></a>28.3.17.2 Names </H4> +<H4><a name="Lua_nn29">28.3.17.2 Names </a></H4> <p> If SWIG is launched without <tt>-no-old-metatable-bindings</tt> option, then it enters backward-compatible mode. While in this mode, it tries @@ -1481,7 +1481,7 @@ surrounding scope without any prefixing. Pretending that Test2 is a struct, not > </pre></div> -<H4><a name="Lua_nn30"></a>28.3.17.3 Inheritance </H4> +<H4><a name="Lua_nn30">28.3.17.3 Inheritance </a></H4> <p> The internal organization of inheritance has changed. @@ -1522,12 +1522,12 @@ function > </pre></div> -<H2><a name="Lua_nn24"></a>28.4 Typemaps</H2> +<H2><a name="Lua_nn24">28.4 Typemaps</a></H2> <p>This section explains what typemaps are and how to use them. The default wrapping behaviour of SWIG is enough in most cases. However sometimes SWIG may need a little additional assistance to know which typemap to apply to provide the best wrapping. This section will be explaining how to use typemaps to best effect</p> -<H3><a name="Lua_nn25"></a>28.4.1 What is a typemap?</H3> +<H3><a name="Lua_nn25">28.4.1 What is a typemap?</a></H3> <p>A typemap is nothing more than a code generation rule that is attached to a specific C datatype. For example, to convert integers from Lua to C, you might define a typemap like this:</p> @@ -1555,7 +1555,7 @@ Received an integer : 6 720 </pre></div> -<H3><a name="Lua_nn26"></a>28.4.2 Using typemaps</H3> +<H3><a name="Lua_nn26">28.4.2 Using typemaps</a></H3> <p>There are many ready written typemaps built into SWIG for all common types (int, float, short, long, char*, enum and more), which SWIG uses automatically, with no effort required on your part.</p> @@ -1608,7 +1608,7 @@ void swap(int *sx, int *sy); <p>Note: C++ references must be handled exactly the same way. However SWIG will automatically wrap a <tt>const int&</tt> as an input parameter (since that it obviously input).</p> -<H3><a name="Lua_typemap_arrays"></a>28.4.3 Typemaps and arrays</H3> +<H3><a name="Lua_typemap_arrays">28.4.3 Typemaps and arrays</a></H3> <p>Arrays present a challenge for SWIG, because like pointers SWIG does not know whether these are input or output values, nor @@ -1672,7 +1672,7 @@ and Lua tables to be 1..N, (the indexing follows the norm for the language). In <p>Note: SWIG also can support arrays of pointers in a similar manner.</p> -<H3><a name="Lua_typemaps_ptr_ptr_functions"></a>28.4.4 Typemaps and pointer-pointer functions</H3> +<H3><a name="Lua_typemaps_ptr_ptr_functions">28.4.4 Typemaps and pointer-pointer functions</a></H3> <p>Several C++ libraries use a pointer-pointer functions to create its objects. These functions require a pointer to a pointer which is then filled with the pointer to the new object. Microsoft's COM and DirectX as well as many other libraries have this kind of function. An example is given below:</p> @@ -1706,7 +1706,7 @@ int Create_Math(iMath** pptr); // its creator (assume it mallocs) ptr=nil -- the iMath* will be GC'ed as normal </pre></div> -<H2><a name="Lua_writing_typemaps"></a>28.5 Writing typemaps</H2> +<H2><a name="Lua_writing_typemaps">28.5 Writing typemaps</a></H2> <p>This section describes how you can modify SWIG's default wrapping behavior for various C/C++ datatypes using the <tt>%typemap</tt> directive. This is an advanced topic that assumes familiarity with the Lua C API as well as the material in the "<a href="Typemaps.html#Typemaps">Typemaps</a>" chapter.</p> @@ -1715,7 +1715,7 @@ ptr=nil -- the iMath* will be GC'ed as normal <p>Before proceeding, you should read the previous section on using typemaps, and look at the existing typemaps found in luatypemaps.swg and typemaps.i. These are both well documented and fairly easy to read. You should not attempt to write your own typemaps until you have read and can understand both of these files (they may well also give you an idea to base your work on).</p> -<H3><a name="Lua_typemaps_write"></a>28.5.1 Typemaps you can write</H3> +<H3><a name="Lua_typemaps_write">28.5.1 Typemaps you can write</a></H3> <p>There are many different types of typemap that can be written, the full list can be found in the "<a href="Typemaps.html#Typemaps">Typemaps</a>" chapter. However the following are the most commonly used ones.</p> @@ -1728,7 +1728,7 @@ ptr=nil -- the iMath* will be GC'ed as normal (the syntax for the typecheck is different from the typemap, see typemaps for details).</li> </ul> -<H3><a name="Lua_nn31"></a>28.5.2 SWIG's Lua-C API</H3> +<H3><a name="Lua_nn31">28.5.2 SWIG's Lua-C API</a></H3> <p>This section explains the SWIG specific Lua-C API. It does not cover the main Lua-C api, as this is well documented and not worth covering.</p> @@ -1777,7 +1777,7 @@ This macro, when called within the context of a SWIG wrapped function, will disp <div class="indent"> Similar to SWIG_fail_arg, except that it will display the swig_type_info information instead.</div> -<H2><a name="Lua_nn32"></a>28.6 Customization of your Bindings</H2> +<H2><a name="Lua_nn32">28.6 Customization of your Bindings</a></H2> <p> @@ -1786,7 +1786,7 @@ This section covers adding of some small extra bits to your module to add the la -<H3><a name="Lua_nn33"></a>28.6.1 Writing your own custom wrappers</H3> +<H3><a name="Lua_nn33">28.6.1 Writing your own custom wrappers</a></H3> <p> @@ -1805,7 +1805,7 @@ int native_function(lua_State*L) // my native code The <tt>%native</tt> directive in the above example, tells SWIG that there is a function <tt>int native_function(lua_State*L);</tt> which is to be added into the module under the name '<tt>my_func</tt>'. SWIG will not add any wrapper for this function, beyond adding it into the function table. How you write your code is entirely up to you. </p> -<H3><a name="Lua_nn34"></a>28.6.2 Adding additional Lua code</H3> +<H3><a name="Lua_nn34">28.6.2 Adding additional Lua code</a></H3> <p> @@ -1843,7 +1843,7 @@ Good uses for this feature is adding of new code, or writing helper functions to See Examples/lua/arrays for an example of this code. </p> -<H2><a name="Lua_nn35"></a>28.7 Details on the Lua binding</H2> +<H2><a name="Lua_nn35">28.7 Details on the Lua binding</a></H2> <p> @@ -1854,7 +1854,7 @@ See Examples/lua/arrays for an example of this code. </i> </p> -<H3><a name="Lua_nn36"></a>28.7.1 Binding global data into the module.</H3> +<H3><a name="Lua_nn36">28.7.1 Binding global data into the module.</a></H3> <p> @@ -1914,7 +1914,7 @@ end <p> That way when you call '<tt>a=example.Foo</tt>', the interpreter looks at the table 'example' sees that there is no field 'Foo' and calls __index. This will in turn check in '.get' table and find the existence of 'Foo' and then return the value of the C function call 'Foo_get()'. Similarly for the code '<tt>example.Foo=10</tt>', the interpreter will check the table, then call the __newindex which will then check the '.set' table and call the C function 'Foo_set(10)'. </p> -<H3><a name="Lua_nn37"></a>28.7.2 Userdata and Metatables</H3> +<H3><a name="Lua_nn37">28.7.2 Userdata and Metatables</a></H3> <p> @@ -1994,7 +1994,7 @@ Note: Both the opaque structures (like the FILE*) and normal wrapped classes/str <p> Note: Operator overloads are basically done in the same way, by adding functions such as '__add' & '__call' to the class' metatable. The current implementation is a bit rough as it will add any member function beginning with '__' into the metatable too, assuming its an operator overload. </p> -<H3><a name="Lua_nn38"></a>28.7.3 Memory management</H3> +<H3><a name="Lua_nn38">28.7.3 Memory management</a></H3> <p> diff --git a/Doc/Manual/Modula3.html b/Doc/Manual/Modula3.html index ffbf6132d..ed6e596e7 100644 --- a/Doc/Manual/Modula3.html +++ b/Doc/Manual/Modula3.html @@ -5,7 +5,7 @@ <link rel="stylesheet" type="text/css" href="style.css"> </head> <body bgcolor="#FFFFFF"> -<H1><a name="Modula3"></a>29 SWIG and Modula-3</H1> +<H1><a name="Modula3">29 SWIG and Modula-3</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -54,7 +54,7 @@ especially <a href="Typemaps.html#Typemaps">typemaps</a>. </p> -<H2><a name="Modula3_modula3_overview"></a>29.1 Overview</H2> +<H2><a name="Modula3_modula3_overview">29.1 Overview</a></H2> <p> @@ -84,7 +84,7 @@ FFTW </li> </ol> -<H3><a name="Modula3_motivation"></a>29.1.1 Motivation</H3> +<H3><a name="Modula3_motivation">29.1.1 Motivation</a></H3> <p> @@ -131,10 +131,10 @@ functions), but it doesn't allow you to easily integrate a Modula-3 module into a C/C++ project. </p> -<H2><a name="Modula3_conception"></a>29.2 Conception</H2> +<H2><a name="Modula3_conception">29.2 Conception</a></H2> -<H3><a name="Modula3_cinterface"></a>29.2.1 Interfaces to C libraries</H3> +<H3><a name="Modula3_cinterface">29.2.1 Interfaces to C libraries</a></H3> <p> @@ -283,7 +283,7 @@ and the principal type must be renamed (<tt>%typemap</tt>). </p> -<H3><a name="Modula3_cppinterface"></a>29.2.2 Interfaces to C++ libraries</H3> +<H3><a name="Modula3_cppinterface">29.2.2 Interfaces to C++ libraries</a></H3> <p> @@ -384,10 +384,10 @@ There is no C++ library I wrote a SWIG interface for, so I'm not sure if this is possible or sensible, yet. </p> -<H2><a name="Modula3_preliminaries"></a>29.3 Preliminaries</H2> +<H2><a name="Modula3_preliminaries">29.3 Preliminaries</a></H2> -<H3><a name="Modula3_compilers"></a>29.3.1 Compilers</H3> +<H3><a name="Modula3_compilers">29.3.1 Compilers</a></H3> <p> @@ -400,7 +400,7 @@ For testing examples I use Critical Mass cm3. </p> -<H3><a name="Modula3_commandline"></a>29.3.2 Additional Commandline Options</H3> +<H3><a name="Modula3_commandline">29.3.2 Additional Commandline Options</a></H3> <p> @@ -477,10 +477,10 @@ Instead generate templates for some basic typemaps. </tr> </table> -<H2><a name="Modula3_typemaps"></a>29.4 Modula-3 typemaps</H2> +<H2><a name="Modula3_typemaps">29.4 Modula-3 typemaps</a></H2> -<H3><a name="Modula3_inoutparam"></a>29.4.1 Inputs and outputs</H3> +<H3><a name="Modula3_inoutparam">29.4.1 Inputs and outputs</a></H3> <p> @@ -694,7 +694,7 @@ consist of the following parts: </table> -<H3><a name="Modula3_ordinals"></a>29.4.2 Subranges, Enumerations, Sets</H3> +<H3><a name="Modula3_ordinals">29.4.2 Subranges, Enumerations, Sets</a></H3> <p> @@ -746,7 +746,7 @@ that I'd like to automate. </p> -<H3><a name="Modula3_class"></a>29.4.3 Objects</H3> +<H3><a name="Modula3_class">29.4.3 Objects</a></H3> <p> @@ -759,7 +759,7 @@ is not really useful, yet. </p> -<H3><a name="Modula3_imports"></a>29.4.4 Imports</H3> +<H3><a name="Modula3_imports">29.4.4 Imports</a></H3> <p> @@ -792,7 +792,7 @@ IMPORT M3toC; </pre></div> -<H3><a name="Modula3_exceptions"></a>29.4.5 Exceptions</H3> +<H3><a name="Modula3_exceptions">29.4.5 Exceptions</a></H3> <p> @@ -816,7 +816,7 @@ you should declare <tt>%typemap("m3wrapinconv:throws") blah * %{OSError.E%}</tt>. </p> -<H3><a name="Modula3_typemap_example"></a>29.4.6 Example</H3> +<H3><a name="Modula3_typemap_example">29.4.6 Example</a></H3> <p> @@ -863,10 +863,10 @@ where almost everything is generated by a typemap: </pre></div> -<H2><a name="Modula3_hints"></a>29.5 More hints to the generator</H2> +<H2><a name="Modula3_hints">29.5 More hints to the generator</a></H2> -<H3><a name="Modula3_features"></a>29.5.1 Features</H3> +<H3><a name="Modula3_features">29.5.1 Features</a></H3> <table border summary="Modula-3 features"> @@ -903,7 +903,7 @@ where almost everything is generated by a typemap: </tr> </table> -<H3><a name="Modula3_pragmas"></a>29.5.2 Pragmas</H3> +<H3><a name="Modula3_pragmas">29.5.2 Pragmas</a></H3> <table border summary="Modula-3 pragmas"> @@ -926,7 +926,7 @@ where almost everything is generated by a typemap: </tr> </table> -<H2><a name="Modula3_remarks"></a>29.6 Remarks</H2> +<H2><a name="Modula3_remarks">29.6 Remarks</a></H2> <ul> diff --git a/Doc/Manual/Modules.html b/Doc/Manual/Modules.html index 4846aedc1..d12383a1d 100644 --- a/Doc/Manual/Modules.html +++ b/Doc/Manual/Modules.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Modules"></a>16 Working with Modules</H1> +<H1><a name="Modules">16 Working with Modules</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -23,7 +23,7 @@ -<H2><a name="Modules_introduction"></a>16.1 Modules Introduction</H2> +<H2><a name="Modules_introduction">16.1 Modules Introduction</a></H2> <p> @@ -77,7 +77,7 @@ where you want to create a collection of modules. Each module in the collection is created via separate invocations of SWIG. </p> -<H2><a name="Modules_nn1"></a>16.2 Basics</H2> +<H2><a name="Modules_nn1">16.2 Basics</a></H2> <p> @@ -176,7 +176,7 @@ in parallel from multiple threads as SWIG provides no locking - for more on that issue, read on. </p> -<H2><a name="Modules_nn2"></a>16.3 The SWIG runtime code</H2> +<H2><a name="Modules_nn2">16.3 The SWIG runtime code</a></H2> <p> @@ -242,7 +242,7 @@ can peacefully coexist. So the type structures are separated by the is empty. Only modules compiled with the same pair will share type information. </p> -<H2><a name="Modules_external_run_time"></a>16.4 External access to the runtime</H2> +<H2><a name="Modules_external_run_time">16.4 External access to the runtime</a></H2> <p>As described in <a href="Typemaps.html#Typemaps_runtime_type_checker">The run-time type checker</a>, @@ -281,7 +281,7 @@ SWIG_TYPE_TABLE to be the same as the module whose types you are trying to access. </p> -<H2><a name="Modules_nn4"></a>16.5 A word of caution about static libraries</H2> +<H2><a name="Modules_nn4">16.5 A word of caution about static libraries</a></H2> <p> @@ -292,7 +292,7 @@ into it. This is very often <b>NOT</b> what you want and it can lead to unexpect behavior. When working with dynamically loadable modules, you should try to work exclusively with shared libraries. </p> -<H2><a name="Modules_nn5"></a>16.6 References</H2> +<H2><a name="Modules_nn5">16.6 References</a></H2> <p> @@ -300,7 +300,7 @@ Due to the complexity of working with shared libraries and multiple modules, it an outside reference. John Levine's "Linkers and Loaders" is highly recommended. </p> -<H2><a name="Modules_nn6"></a>16.7 Reducing the wrapper file size</H2> +<H2><a name="Modules_nn6">16.7 Reducing the wrapper file size</a></H2> <p> diff --git a/Doc/Manual/Mzscheme.html b/Doc/Manual/Mzscheme.html index fadda5fc9..358942a35 100644 --- a/Doc/Manual/Mzscheme.html +++ b/Doc/Manual/Mzscheme.html @@ -8,7 +8,7 @@ <body bgcolor="#ffffff"> -<H1><a name="Mzscheme"></a>30 SWIG and MzScheme/Racket</H1> +<H1><a name="Mzscheme">30 SWIG and MzScheme/Racket</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -24,7 +24,7 @@ <p> This section contains information on SWIG's support of Racket, formally known as MzScheme. -<H2><a name="MzScheme_nn2"></a>30.1 Creating native structures</H2> +<H2><a name="MzScheme_nn2">30.1 Creating native structures</a></H2> <p> @@ -65,7 +65,7 @@ Then in scheme, you can use regular struct access procedures like </pre> </div> -<H2><a name="MzScheme_simple"></a>30.2 Simple example</H2> +<H2><a name="MzScheme_simple">30.2 Simple example</a></H2> <p> @@ -166,7 +166,7 @@ Some points of interest: <li> The above requests mzc to create an extension using the CGC garbage-collector. The alternative -- the 3m collector -- has generally better performance, but work is still required for SWIG to emit code which is compatible with it. </ul> -<H2><a name="MzScheme_external_docs"></a>30.3 External documentation</H2> +<H2><a name="MzScheme_external_docs">30.3 External documentation</a></H2> <p> diff --git a/Doc/Manual/Ocaml.html b/Doc/Manual/Ocaml.html index b927a7d8f..789bbae53 100644 --- a/Doc/Manual/Ocaml.html +++ b/Doc/Manual/Ocaml.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Ocaml"></a>31 SWIG and Ocaml</H1> +<H1><a name="Ocaml">31 SWIG and Ocaml</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -83,7 +83,7 @@ If you're not familiar with the Objective Caml language, you can visit <a href="http://ocaml.org/">The Ocaml Website</a>. </p> -<H2><a name="Ocaml_nn2"></a>31.1 Preliminaries</H2> +<H2><a name="Ocaml_nn2">31.1 Preliminaries</a></H2> <p> @@ -101,7 +101,7 @@ file Examples/Makefile illustrate how to compile and link SWIG modules that will be loaded dynamically. This has only been tested on Linux so far. </p> -<H3><a name="Ocaml_nn3"></a>31.1.1 Running SWIG</H3> +<H3><a name="Ocaml_nn3">31.1.1 Running SWIG</a></H3> <p> @@ -124,7 +124,7 @@ you will compile the file <tt>example_wrap.c</tt> with <tt>ocamlc</tt> or the resulting .ml and .mli files as well, and do the final link with -custom (not needed for native link).</p> -<H3><a name="Ocaml_nn4"></a>31.1.2 Compiling the code</H3> +<H3><a name="Ocaml_nn4">31.1.2 Compiling the code</a></H3> <p> @@ -161,7 +161,7 @@ in C++ mode, you must:</p> </pre> </div> -<H3><a name="Ocaml_nn5"></a>31.1.3 The camlp4 module</H3> +<H3><a name="Ocaml_nn5">31.1.3 The camlp4 module</a></H3> <p> @@ -237,7 +237,7 @@ let b = C_string (getenv "PATH") </td></tr> </table> -<H3><a name="Ocaml_nn6"></a>31.1.4 Using your module</H3> +<H3><a name="Ocaml_nn6">31.1.4 Using your module</a></H3> <p> @@ -251,7 +251,7 @@ option to build your functions into the primitive list. This option is not needed when you build native code. </p> -<H3><a name="Ocaml_nn7"></a>31.1.5 Compilation problems and compiling with C++</H3> +<H3><a name="Ocaml_nn7">31.1.5 Compilation problems and compiling with C++</a></H3> <p> @@ -262,7 +262,7 @@ liberal with pointer types may not compile under the C++ compiler. Most code meant to be compiled as C++ will not have problems. </p> -<H2><a name="Ocaml_nn8"></a>31.2 The low-level Ocaml/C interface</H2> +<H2><a name="Ocaml_nn8">31.2 The low-level Ocaml/C interface</a></H2> <p> @@ -362,7 +362,7 @@ value items pass through directly, but you must make your own type signature for a function that uses value in this way. </p> -<H3><a name="Ocaml_nn9"></a>31.2.1 The generated module</H3> +<H3><a name="Ocaml_nn9">31.2.1 The generated module</a></H3> <p> @@ -396,7 +396,7 @@ it describes the output SWIG will generate for class definitions. </td></tr> </table> -<H3><a name="Ocaml_nn10"></a>31.2.2 Enums</H3> +<H3><a name="Ocaml_nn10">31.2.2 Enums</a></H3> <p> @@ -459,7 +459,7 @@ val x : Enum_test.c_obj = C_enum `a </pre> </div> -<H4><a name="Ocaml_nn11"></a>31.2.2.1 Enum typing in Ocaml</H4> +<H4><a name="Ocaml_nn11">31.2.2.1 Enum typing in Ocaml</a></H4> <p> @@ -472,10 +472,10 @@ functions imported from different modules. You must convert values to master values using the swig_val function before sharing them with another module. </p> -<H3><a name="Ocaml_nn12"></a>31.2.3 Arrays</H3> +<H3><a name="Ocaml_nn12">31.2.3 Arrays</a></H3> -<H4><a name="Ocaml_nn13"></a>31.2.3.1 Simple types of bounded arrays</H4> +<H4><a name="Ocaml_nn13">31.2.3.1 Simple types of bounded arrays</a></H4> <p> @@ -496,7 +496,7 @@ arrays of simple types with known bounds in your code, but this only works for arrays whose bounds are completely specified. </p> -<H4><a name="Ocaml_nn14"></a>31.2.3.2 Complex and unbounded arrays</H4> +<H4><a name="Ocaml_nn14">31.2.3.2 Complex and unbounded arrays</a></H4> <p> @@ -509,7 +509,7 @@ SWIG can't predict which of these methods will be used in the array, so you have to specify it for yourself in the form of a typemap. </p> -<H4><a name="Ocaml_nn15"></a>31.2.3.3 Using an object</H4> +<H4><a name="Ocaml_nn15">31.2.3.3 Using an object</a></H4> <p> @@ -523,7 +523,7 @@ Consider writing an object when the ending condition of your array is complex, such as using a required sentinel, etc. </p> -<H4><a name="Ocaml_nn16"></a>31.2.3.4 Example typemap for a function taking float * and int</H4> +<H4><a name="Ocaml_nn16">31.2.3.4 Example typemap for a function taking float * and int</a></H4> <p> @@ -574,7 +574,7 @@ void printfloats( float *tab, int len ); </pre></td></tr></table> -<H3><a name="Ocaml_nn17"></a>31.2.4 C++ Classes</H3> +<H3><a name="Ocaml_nn17">31.2.4 C++ Classes</a></H3> <p> @@ -617,7 +617,7 @@ the underlying pointer, so using create_[x]_from_ptr alters the returned value for the same object. </p> -<H4><a name="Ocaml_nn18"></a>31.2.4.1 STL vector and string Example</H4> +<H4><a name="Ocaml_nn18">31.2.4.1 STL vector and string Example</a></H4> <p> @@ -697,7 +697,7 @@ baz # </pre></div> -<H4><a name="Ocaml_nn19"></a>31.2.4.2 C++ Class Example</H4> +<H4><a name="Ocaml_nn19">31.2.4.2 C++ Class Example</a></H4> <p> @@ -727,7 +727,7 @@ public: }; </pre></td></tr></table> -<H4><a name="Ocaml_nn20"></a>31.2.4.3 Compiling the example</H4> +<H4><a name="Ocaml_nn20">31.2.4.3 Compiling the example</a></H4> <div class="code"><pre> @@ -745,7 +745,7 @@ bash-2.05a$ ocamlmktop -custom swig.cmo -I `camlp4 -where` \ -L$QTPATH/lib -cclib -lqt </pre></div> -<H4><a name="Ocaml_nn21"></a>31.2.4.4 Sample Session</H4> +<H4><a name="Ocaml_nn21">31.2.4.4 Sample Session</a></H4> <div class="code"><pre> @@ -772,10 +772,10 @@ Assuming you have a working installation of QT, you will see a window containing the string "hi" in a button. </p> -<H3><a name="Ocaml_nn22"></a>31.2.5 Director Classes</H3> +<H3><a name="Ocaml_nn22">31.2.5 Director Classes</a></H3> -<H4><a name="Ocaml_nn23"></a>31.2.5.1 Director Introduction</H4> +<H4><a name="Ocaml_nn23">31.2.5.1 Director Introduction</a></H4> <p> @@ -802,7 +802,7 @@ class foo { }; </pre></div> -<H4><a name="Ocaml_nn24"></a>31.2.5.2 Overriding Methods in Ocaml</H4> +<H4><a name="Ocaml_nn24">31.2.5.2 Overriding Methods in Ocaml</a></H4> <p> @@ -830,7 +830,7 @@ In this example, I'll examine the objective caml code involved in providing an overloaded class. This example is contained in Examples/ocaml/shapes. </p> -<H4><a name="Ocaml_nn25"></a>31.2.5.3 Director Usage Example</H4> +<H4><a name="Ocaml_nn25">31.2.5.3 Director Usage Example</a></H4> <table border="1" bgcolor="#dddddd" summary="Director usage example"> @@ -889,7 +889,7 @@ in a more effortless style in ocaml, while leaving the "engine" part of the program in C++. </p> -<H4><a name="Ocaml_nn26"></a>31.2.5.4 Creating director objects</H4> +<H4><a name="Ocaml_nn26">31.2.5.4 Creating director objects</a></H4> <p> @@ -930,7 +930,7 @@ object from causing a core dump, as long as the object is destroyed properly. </p> -<H4><a name="Ocaml_nn27"></a>31.2.5.5 Typemaps for directors, <tt>directorin, directorout, directorargout</tt></H4> +<H4><a name="Ocaml_nn27">31.2.5.5 Typemaps for directors, <tt>directorin, directorout, directorargout</tt></a></H4> <p> @@ -941,7 +941,7 @@ well as a function return value in the same way you provide function arguments, and to receive arguments the same way you normally receive function returns. </p> -<H4><a name="Ocaml_nn28"></a>31.2.5.6 <tt>directorin</tt> typemap</H4> +<H4><a name="Ocaml_nn28">31.2.5.6 <tt>directorin</tt> typemap</a></H4> <p> @@ -952,7 +952,7 @@ code receives when you are called. In general, a simple <tt>directorin</tt> typ can use the same body as a simple <tt>out</tt> typemap. </p> -<H4><a name="Ocaml_nn29"></a>31.2.5.7 <tt>directorout</tt> typemap</H4> +<H4><a name="Ocaml_nn29">31.2.5.7 <tt>directorout</tt> typemap</a></H4> <p> @@ -963,7 +963,7 @@ for the same type, except when there are special requirements for object ownership, etc. </p> -<H4><a name="Ocaml_nn30"></a>31.2.5.8 <tt>directorargout</tt> typemap</H4> +<H4><a name="Ocaml_nn30">31.2.5.8 <tt>directorargout</tt> typemap</a></H4> <p> @@ -980,7 +980,7 @@ In the event that you don't specify all of the necessary values, integral values will read zero, and struct or object returns have undefined results. </p> -<H3><a name="Ocaml_nn31"></a>31.2.6 Exceptions</H3> +<H3><a name="Ocaml_nn31">31.2.6 Exceptions</a></H3> <p> diff --git a/Doc/Manual/Octave.html b/Doc/Manual/Octave.html index 53ee86f7c..df484103d 100644 --- a/Doc/Manual/Octave.html +++ b/Doc/Manual/Octave.html @@ -8,7 +8,7 @@ <body bgcolor="#ffffff"> -<H1><a name="Octave"></a>32 SWIG and Octave</H1> +<H1><a name="Octave">32 SWIG and Octave</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -59,7 +59,7 @@ More information can be found at <a href="http://www.gnu.org/software/octave/">O Also, there are a dozen or so examples in the Examples/octave directory, and hundreds in the test suite (Examples/test-suite and Examples/test-suite/octave). </p> -<H2><a name="Octave_nn2"></a>32.1 Preliminaries</H2> +<H2><a name="Octave_nn2">32.1 Preliminaries</a></H2> <p> @@ -67,7 +67,7 @@ As of SWIG 3.0.7, the Octave module is regularly tested with Octave versions 3.2 Use of older Octave versions is not recommended, as these versions are no longer tested with SWIG. </p> -<H2><a name="Octave_nn3"></a>32.2 Running SWIG</H2> +<H2><a name="Octave_nn3">32.2 Running SWIG</a></H2> <p> @@ -99,7 +99,7 @@ The <tt>-c++</tt> option is also required when wrapping C++ code: This creates a C++ source file "example_wrap.cpp". A C++ file is generated even when wrapping C code as Octave is itself written in C++ and requires wrapper code to be in the same language. The generated C++ source file contains the low-level wrappers that need to be compiled and linked with the rest of your C/C++ application (in this case, the gcd implementation) to create an extension module. </p> -<H3><a name="Octave_nn4"></a>32.2.1 Command-line options</H3> +<H3><a name="Octave_nn4">32.2.1 Command-line options</a></H3> <p> @@ -122,7 +122,7 @@ The special name "." loads C global variables into the module namespace, i.e. al The <em>-opprefix</em> options sets the prefix of the names of global/friend <a href="#Octave_nn18">operator</a> functions. </p> -<H3><a name="Octave_nn5"></a>32.2.2 Compiling a dynamic module</H3> +<H3><a name="Octave_nn5">32.2.2 Compiling a dynamic module</a></H3> <p> @@ -149,7 +149,7 @@ $ mkoctfile example_wrap.cpp example.c <div class="targetlang"><pre>octave:1> swigexample</pre></div> -<H3><a name="Octave_nn6"></a>32.2.3 Using your module</H3> +<H3><a name="Octave_nn6">32.2.3 Using your module</a></H3> <p> @@ -167,10 +167,10 @@ octave:4> swigexample.cvar.Foo=4; octave:5> swigexample.cvar.Foo ans = 4 </pre></div> -<H2><a name="Octave_nn7"></a>32.3 A tour of basic C/C++ wrapping</H2> +<H2><a name="Octave_nn7">32.3 A tour of basic C/C++ wrapping</a></H2> -<H3><a name="Octave_nn8"></a>32.3.1 Modules</H3> +<H3><a name="Octave_nn8">32.3.1 Modules</a></H3> <p> @@ -215,7 +215,7 @@ octave:4> swigexample.gcd(4,6) ans = 2 </pre></div> -<H3><a name="Octave_nn9"></a>32.3.2 Functions</H3> +<H3><a name="Octave_nn9">32.3.2 Functions</a></H3> <p> @@ -232,7 +232,7 @@ int fact(int n); </pre></div> <div class="targetlang"><pre>octave:1> swigexample.fact(4) 24 </pre></div> -<H3><a name="Octave_nn10"></a>32.3.3 Global variables</H3> +<H3><a name="Octave_nn10">32.3.3 Global variables</a></H3> <p> @@ -285,7 +285,7 @@ octave:2> swigexample.PI=3.142; octave:3> swigexample.PI ans = 3.1420 </pre></div> -<H3><a name="Octave_nn11"></a>32.3.4 Constants and enums</H3> +<H3><a name="Octave_nn11">32.3.4 Constants and enums</a></H3> <p> @@ -307,7 +307,7 @@ swigexample.SCONST="Hello World" swigexample.SUNDAY=0 .... </pre></div> -<H3><a name="Octave_nn12"></a>32.3.5 Pointers</H3> +<H3><a name="Octave_nn12">32.3.5 Pointers</a></H3> <p> @@ -354,7 +354,7 @@ octave:2> f=swigexample.fopen("not there","r"); error: value on right hand side of assignment is undefined error: evaluating assignment expression near line 2, column 2 </pre></div> -<H3><a name="Octave_nn13"></a>32.3.6 Structures and C++ classes</H3> +<H3><a name="Octave_nn13">32.3.6 Structures and C++ classes</a></H3> <p> @@ -489,7 +489,7 @@ ans = 1 Depending on the ownership setting of a <tt>swig_ref</tt>, it may call C++ destructors when its reference count goes to zero. See the section on memory management below for details. </p> -<H3><a name="Octave_nn15"></a>32.3.7 C++ inheritance</H3> +<H3><a name="Octave_nn15">32.3.7 C++ inheritance</a></H3> <p> @@ -498,7 +498,7 @@ This information contains the full class hierarchy. When an indexing operation ( the tree is walked to find a match in the current class as well as any of its bases. The lookup is then cached in the <tt>swig_ref</tt>. </p> -<H3><a name="Octave_nn17"></a>32.3.8 C++ overloaded functions</H3> +<H3><a name="Octave_nn17">32.3.8 C++ overloaded functions</a></H3> <p> @@ -508,7 +508,7 @@ The dispatch function selects which overload to call (if any) based on the passe <tt>typecheck</tt> typemaps are used to analyze each argument, as well as assign precedence. See the chapter on typemaps for details. </p> -<H3><a name="Octave_nn18"></a>32.3.9 C++ operators</H3> +<H3><a name="Octave_nn18">32.3.9 C++ operators</a></H3> <p> @@ -612,7 +612,7 @@ On the C++ side, the default mappings are as follows: Octave can also utilise friend (i.e. non-member) operators with a simple %rename: see the example in the Examples/octave/operator directory. </p> -<H3><a name="Octave_nn19"></a>32.3.10 Class extension with %extend</H3> +<H3><a name="Octave_nn19">32.3.10 Class extension with %extend</a></H3> <p> @@ -642,7 +642,7 @@ octave:3> printf("%s\n",a); octave:4> a.__str() 4 </pre></div> -<H3><a name="Octave_nn20"></a>32.3.11 C++ templates</H3> +<H3><a name="Octave_nn20">32.3.11 C++ templates</a></H3> <p> @@ -719,10 +719,10 @@ ans = </pre></div> -<H3><a name="Octave_nn21"></a>32.3.12 C++ Smart Pointers</H3> +<H3><a name="Octave_nn21">32.3.12 C++ Smart Pointers</a></H3> -<H4><a name="Octave_smart_pointers_shared_ptr"></a>32.3.12.1 The shared_ptr Smart Pointer</H4> +<H4><a name="Octave_smart_pointers_shared_ptr">32.3.12.1 The shared_ptr Smart Pointer</a></H4> <p> @@ -733,14 +733,14 @@ in the <a href="Library.html#Library_std_shared_ptr">shared_ptr smart pointer</a </p> -<H4><a name="Octave_smart_pointers_generic"></a>32.3.12.2 Generic Smart Pointers</H4> +<H4><a name="Octave_smart_pointers_generic">32.3.12.2 Generic Smart Pointers</a></H4> <p> C++ smart pointers are fully supported as in other modules. </p> -<H3><a name="Octave_nn22"></a>32.3.13 Directors (calling Octave from C++ code)</H3> +<H3><a name="Octave_nn22">32.3.13 Directors (calling Octave from C++ code)</a></H3> <p> @@ -821,14 +821,14 @@ c-side routine called octave-side routine called </pre></div> -<H3><a name="Octave_nn23"></a>32.3.14 Threads</H3> +<H3><a name="Octave_nn23">32.3.14 Threads</a></H3> <p> The use of threads in wrapped Director code is not supported; i.e., an Octave-side implementation of a C++ class must be called from the Octave interpreter's thread. Anything fancier (apartment/queue model, whatever) is left to the user. Without anything fancier, this amounts to the limitation that Octave must drive the module... like, for example, an optimization package that calls Octave to evaluate an objective function. </p> -<H3><a name="Octave_nn24"></a>32.3.15 Memory management</H3> +<H3><a name="Octave_nn24">32.3.15 Memory management</a></H3> <p> @@ -862,14 +862,14 @@ The %newobject directive may be used to control this behavior for pointers retur In the case where one wishes for the C++ side to own an object that was created in Octave (especially a Director object), one can use the __disown() method to invert this logic. Then letting the Octave reference count go to zero will not destroy the object, but destroying the object will invalidate the Octave-side object if it still exists (and call destructors of other C++ bases in the case of multiple inheritance/<tt>subclass()</tt>'ing). </p> -<H3><a name="Octave_nn25"></a>32.3.16 STL support</H3> +<H3><a name="Octave_nn25">32.3.16 STL support</a></H3> <p> Various STL library files are provided for wrapping STL containers. </p> -<H3><a name="Octave_nn26"></a>32.3.17 Matrix typemaps</H3> +<H3><a name="Octave_nn26">32.3.17 Matrix typemaps</a></H3> <p> diff --git a/Doc/Manual/Perl5.html b/Doc/Manual/Perl5.html index 8bc7cbfd3..bb912ec8e 100644 --- a/Doc/Manual/Perl5.html +++ b/Doc/Manual/Perl5.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Perl5"></a>33 SWIG and Perl5</H1> +<H1><a name="Perl5">33 SWIG and Perl5</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -96,7 +96,7 @@ later. We're no longer testing regularly with older versions, but Perl 5.6 seems to mostly work, while older versions don't. </p> -<H2><a name="Perl5_nn2"></a>33.1 Overview</H2> +<H2><a name="Perl5_nn2">33.1 Overview</a></H2> <p> @@ -117,7 +117,7 @@ described. Advanced customization features, typemaps, and other options are found near the end of the chapter. </p> -<H2><a name="Perl5_nn3"></a>33.2 Preliminaries</H2> +<H2><a name="Perl5_nn3">33.2 Preliminaries</a></H2> <p> @@ -142,7 +142,7 @@ To build the module, you will need to compile the file <tt>example_wrap.c</tt> and link it with the rest of your program. </p> -<H3><a name="Perl5_nn4"></a>33.2.1 Getting the right header files</H3> +<H3><a name="Perl5_nn4">33.2.1 Getting the right header files</a></H3> <p> @@ -174,7 +174,7 @@ $ perl -e 'use Config; print "$Config{archlib}\n";' </pre> </div> -<H3><a name="Perl5_nn5"></a>33.2.2 Compiling a dynamic module</H3> +<H3><a name="Perl5_nn5">33.2.2 Compiling a dynamic module</a></H3> <p> @@ -207,7 +207,7 @@ the target should be named `<tt>example.so</tt>', `<tt>example.sl</tt>', or the appropriate dynamic module name on your system. </p> -<H3><a name="Perl5_nn6"></a>33.2.3 Building a dynamic module with MakeMaker</H3> +<H3><a name="Perl5_nn6">33.2.3 Building a dynamic module with MakeMaker</a></H3> <p> @@ -241,7 +241,7 @@ the preferred approach to compilation. More information about MakeMaker can be found in "Programming Perl, 2nd ed." by Larry Wall, Tom Christiansen, and Randal Schwartz.</p> -<H3><a name="Perl5_nn7"></a>33.2.4 Building a static version of Perl</H3> +<H3><a name="Perl5_nn7">33.2.4 Building a static version of Perl</a></H3> <p> @@ -310,7 +310,7 @@ added to it. Depending on your machine, you may need to link with additional libraries such as <tt>-lsocket, -lnsl, -ldl</tt>, etc. </p> -<H3><a name="Perl5_nn8"></a>33.2.5 Using the module</H3> +<H3><a name="Perl5_nn8">33.2.5 Using the module</a></H3> <p> @@ -463,7 +463,7 @@ system configuration (this requires root access and you will need to read the man pages). </p> -<H3><a name="Perl5_nn9"></a>33.2.6 Compilation problems and compiling with C++</H3> +<H3><a name="Perl5_nn9">33.2.6 Compilation problems and compiling with C++</a></H3> <p> @@ -606,7 +606,7 @@ have to find the macro that conflicts and add an #undef into the .i file. Pleas any conflicting macros you find to <a href="http://www.swig.org/mail.html">swig-user mailing list</a>. </p> -<H3><a name="Perl5_nn10"></a>33.2.7 Compiling for 64-bit platforms</H3> +<H3><a name="Perl5_nn10">33.2.7 Compiling for 64-bit platforms</a></H3> <p> @@ -633,7 +633,7 @@ also introduce problems on platforms that support more than one linking standard (e.g., -o32 and -n32 on Irix). </p> -<H2><a name="Perl5_nn11"></a>33.3 Building Perl Extensions under Windows</H2> +<H2><a name="Perl5_nn11">33.3 Building Perl Extensions under Windows</a></H2> <p> @@ -644,7 +644,7 @@ section assumes you are using SWIG with Microsoft Visual C++ although the procedure may be similar with other compilers. </p> -<H3><a name="Perl5_nn12"></a>33.3.1 Running SWIG from Developer Studio</H3> +<H3><a name="Perl5_nn12">33.3.1 Running SWIG from Developer Studio</a></H3> <p> @@ -707,7 +707,7 @@ print "$a\n"; </pre></div> -<H3><a name="Perl5_nn13"></a>33.3.2 Using other compilers</H3> +<H3><a name="Perl5_nn13">33.3.2 Using other compilers</a></H3> <p> @@ -715,7 +715,7 @@ SWIG is known to work with Cygwin and may work with other compilers on Windows. For general hints and suggestions refer to the <a href="Windows.html#Windows">Windows</a> chapter. </p> -<H2><a name="Perl5_nn14"></a>33.4 The low-level interface</H2> +<H2><a name="Perl5_nn14">33.4 The low-level interface</a></H2> <p> @@ -725,7 +725,7 @@ can be used to control your application. However, it is also used to construct more user-friendly proxy classes as described in the next section. </p> -<H3><a name="Perl5_nn15"></a>33.4.1 Functions</H3> +<H3><a name="Perl5_nn15">33.4.1 Functions</a></H3> <p> @@ -748,7 +748,7 @@ use example; $a = &example::fact(2); </pre></div> -<H3><a name="Perl5_nn16"></a>33.4.2 Global variables</H3> +<H3><a name="Perl5_nn16">33.4.2 Global variables</a></H3> <p> @@ -818,7 +818,7 @@ extern char *path; // Declared later in the input </pre> </div> -<H3><a name="Perl5_nn17"></a>33.4.3 Constants</H3> +<H3><a name="Perl5_nn17">33.4.3 Constants</a></H3> <p> @@ -858,7 +858,7 @@ print example::FOO,"\n"; </pre> </div> -<H3><a name="Perl5_nn18"></a>33.4.4 Pointers</H3> +<H3><a name="Perl5_nn18">33.4.4 Pointers</a></H3> <p> @@ -967,7 +967,7 @@ as XS and <tt>xsubpp</tt>. Given the advancement of the SWIG typesystem and the SWIG and XS, this is no longer supported. </p> -<H3><a name="Perl5_nn19"></a>33.4.5 Structures</H3> +<H3><a name="Perl5_nn19">33.4.5 Structures</a></H3> <p> @@ -1101,7 +1101,7 @@ void Bar_f_set(Bar *b, Foo *val) { </div> -<H3><a name="Perl5_nn20"></a>33.4.6 C++ classes</H3> +<H3><a name="Perl5_nn20">33.4.6 C++ classes</a></H3> <p> @@ -1166,7 +1166,7 @@ provides direct access to C++ objects. A higher level interface using Perl prox can be built using these low-level accessors. This is described shortly. </p> -<H3><a name="Perl5_nn21"></a>33.4.7 C++ classes and type-checking</H3> +<H3><a name="Perl5_nn21">33.4.7 C++ classes and type-checking</a></H3> <p> @@ -1202,7 +1202,7 @@ If necessary, the type-checker also adjusts the value of the pointer (as is nece multiple inheritance is used). </p> -<H3><a name="Perl5_nn22"></a>33.4.8 C++ overloaded functions</H3> +<H3><a name="Perl5_nn22">33.4.8 C++ overloaded functions</a></H3> <p> @@ -1246,7 +1246,7 @@ example::Spam_foo_d($s,3.14); Please refer to the "SWIG Basics" chapter for more information. </p> -<H3><a name="Perl5_nn23"></a>33.4.9 Operators</H3> +<H3><a name="Perl5_nn23">33.4.9 Operators</a></H3> <p> @@ -1273,7 +1273,7 @@ The following C++ operators are currently supported by the Perl module: <li>operator or </li> </ul> -<H3><a name="Perl5_nn24"></a>33.4.10 Modules and packages</H3> +<H3><a name="Perl5_nn24">33.4.10 Modules and packages</a></H3> <p> @@ -1368,7 +1368,7 @@ print Foo::fact(4),"\n"; # Call a function in package FooBar </pre></div> --> -<H2><a name="Perl5_nn25"></a>33.5 Input and output parameters</H2> +<H2><a name="Perl5_nn25">33.5 Input and output parameters</a></H2> <p> @@ -1587,7 +1587,7 @@ print "$c\n"; <b>Note:</b> The <tt>REFERENCE</tt> feature is only currently supported for numeric types (integers and floating point). </p> -<H2><a name="Perl5_nn26"></a>33.6 Exception handling</H2> +<H2><a name="Perl5_nn26">33.6 Exception handling</a></H2> <p> @@ -1752,7 +1752,7 @@ This is still supported, but it is deprecated. The newer <tt>%exception</tt> di functionality, but it has additional capabilities that make it more powerful. </p> -<H2><a name="Perl5_nn27"></a>33.7 Remapping datatypes with typemaps</H2> +<H2><a name="Perl5_nn27">33.7 Remapping datatypes with typemaps</a></H2> <p> @@ -1769,7 +1769,7 @@ Typemaps are only used if you want to change some aspect of the primitive C-Perl interface. </p> -<H3><a name="Perl5_nn28"></a>33.7.1 A simple typemap example</H3> +<H3><a name="Perl5_nn28">33.7.1 A simple typemap example</a></H3> <p> @@ -1873,7 +1873,7 @@ example::count("e","Hello World"); </div> -<H3><a name="Perl5_nn29"></a>33.7.2 Perl5 typemaps</H3> +<H3><a name="Perl5_nn29">33.7.2 Perl5 typemaps</a></H3> <p> @@ -1978,7 +1978,7 @@ Return of C++ member data (all languages). Check value of input parameter. </div> -<H3><a name="Perl5_nn30"></a>33.7.3 Typemap variables</H3> +<H3><a name="Perl5_nn30">33.7.3 Typemap variables</a></H3> <p> @@ -2049,7 +2049,7 @@ properly assigned. The Perl name of the wrapper function being created. </div> -<H3><a name="Perl5_nn31"></a>33.7.4 Useful functions</H3> +<H3><a name="Perl5_nn31">33.7.4 Useful functions</a></H3> <p> @@ -2118,7 +2118,7 @@ int sv_isa(SV *, char *0; </div> -<H2><a name="Perl5_nn32"></a>33.8 Typemap Examples</H2> +<H2><a name="Perl5_nn32">33.8 Typemap Examples</a></H2> <p> @@ -2127,7 +2127,7 @@ might look at the files "<tt>perl5.swg</tt>" and "<tt>typemaps.i</tt>" in the SWIG library. </p> -<H3><a name="Perl5_nn33"></a>33.8.1 Converting a Perl5 array to a char **</H3> +<H3><a name="Perl5_nn33">33.8.1 Converting a Perl5 array to a char **</a></H3> <p> @@ -2219,7 +2219,7 @@ print @$b,"\n"; # Print it out </pre></div> -<H3><a name="Perl5_nn34"></a>33.8.2 Return values</H3> +<H3><a name="Perl5_nn34">33.8.2 Return values</a></H3> <p> @@ -2248,7 +2248,7 @@ can be done using the <tt>EXTEND()</tt> macro as in: } </pre></div> -<H3><a name="Perl5_nn35"></a>33.8.3 Returning values from arguments</H3> +<H3><a name="Perl5_nn35">33.8.3 Returning values from arguments</a></H3> <p> @@ -2302,7 +2302,7 @@ print "multout(7,13) = @r\n"; ($x,$y) = multout(7,13); </pre></div> -<H3><a name="Perl5_nn36"></a>33.8.4 Accessing array structure members</H3> +<H3><a name="Perl5_nn36">33.8.4 Accessing array structure members</a></H3> <p> @@ -2365,7 +2365,7 @@ the "in" typemap in the previous section would be used to convert an to copy the converted array into a C data structure. </p> -<H3><a name="Perl5_nn37"></a>33.8.5 Turning Perl references into C pointers</H3> +<H3><a name="Perl5_nn37">33.8.5 Turning Perl references into C pointers</a></H3> <p> @@ -2430,7 +2430,7 @@ print "$c\n"; </pre></div> -<H3><a name="Perl5_nn38"></a>33.8.6 Pointer handling</H3> +<H3><a name="Perl5_nn38">33.8.6 Pointer handling</a></H3> <p> @@ -2509,7 +2509,7 @@ For example: </pre> </div> -<H2><a name="Perl5_nn39"></a>33.9 Proxy classes</H2> +<H2><a name="Perl5_nn39">33.9 Proxy classes</a></H2> <p> @@ -2525,7 +2525,7 @@ to the underlying code. This section describes the implementation details of the proxy interface. </p> -<H3><a name="Perl5_nn40"></a>33.9.1 Preliminaries</H3> +<H3><a name="Perl5_nn40">33.9.1 Preliminaries</a></H3> <p> @@ -2547,7 +2547,7 @@ SWIG creates a collection of high-level Perl wrappers. In your scripts, you wil high level wrappers. The wrappers, in turn, interact with the low-level procedural module. </p> -<H3><a name="Perl5_nn41"></a>33.9.2 Structure and class wrappers</H3> +<H3><a name="Perl5_nn41">33.9.2 Structure and class wrappers</a></H3> <p> @@ -2673,7 +2673,7 @@ $v->DESTROY(); </pre></div> -<H3><a name="Perl5_nn42"></a>33.9.3 Object Ownership</H3> +<H3><a name="Perl5_nn42">33.9.3 Object Ownership</a></H3> <p> @@ -2760,7 +2760,7 @@ counting, garbage collection, or advanced features one might find in sophisticated languages. </p> -<H3><a name="Perl5_nn43"></a>33.9.4 Nested Objects</H3> +<H3><a name="Perl5_nn43">33.9.4 Nested Objects</a></H3> <p> @@ -2813,7 +2813,7 @@ $p->{f}->{x} = 0.0; %${$p->{v}} = ( x=>0, y=>0, z=>0); </pre></div> -<H3><a name="Perl5_nn44"></a>33.9.5 Proxy Functions</H3> +<H3><a name="Perl5_nn44">33.9.5 Proxy Functions</a></H3> <p> @@ -2847,7 +2847,7 @@ This function replaces the original function, but operates in an identical manner. </p> -<H3><a name="Perl5_nn45"></a>33.9.6 Inheritance</H3> +<H3><a name="Perl5_nn45">33.9.6 Inheritance</a></H3> <p> @@ -2923,7 +2923,7 @@ particular, inheritance of data members is extremely tricky (and I'm not even sure if it really works). </p> -<H3><a name="Perl5_nn46"></a>33.9.7 Modifying the proxy methods</H3> +<H3><a name="Perl5_nn46">33.9.7 Modifying the proxy methods</a></H3> <p> @@ -2951,7 +2951,7 @@ public: }; </pre></div> -<H2><a name="Perl5_nn47"></a>33.10 Adding additional Perl code</H2> +<H2><a name="Perl5_nn47">33.10 Adding additional Perl code</a></H2> <p> @@ -3002,7 +3002,7 @@ set_transform($im, $a); </pre> </div> -<H2><a name="Perl5_directors"></a>33.11 Cross language polymorphism</H2> +<H2><a name="Perl5_directors">33.11 Cross language polymorphism</a></H2> <p> @@ -3036,7 +3036,7 @@ proxy classes, director classes, and C wrapper functions takes care of all the cross-language method routing transparently. </p> -<H3><a name="Perl5_nn48"></a>33.11.1 Enabling directors</H3> +<H3><a name="Perl5_nn48">33.11.1 Enabling directors</a></H3> <p> @@ -3126,7 +3126,7 @@ sub one { </div> -<H3><a name="Perl5_nn49"></a>33.11.2 Director classes</H3> +<H3><a name="Perl5_nn49">33.11.2 Director classes</a></H3> @@ -3206,7 +3206,7 @@ so there is no need for the extra overhead involved with routing the calls through Perl. </p> -<H3><a name="Perl5_nn50"></a>33.11.3 Ownership and object destruction</H3> +<H3><a name="Perl5_nn50">33.11.3 Ownership and object destruction</a></H3> <p> @@ -3255,7 +3255,7 @@ sub DESTROY { </div> -<H3><a name="Perl5_nn51"></a>33.11.4 Exception unrolling</H3> +<H3><a name="Perl5_nn51">33.11.4 Exception unrolling</a></H3> <p> @@ -3311,7 +3311,7 @@ Swig::DirectorMethodException is thrown, Perl will register the exception as soon as the C wrapper function returns. </p> -<H3><a name="Perl5_nn52"></a>33.11.5 Overhead and code bloat</H3> +<H3><a name="Perl5_nn52">33.11.5 Overhead and code bloat</a></H3> <p> @@ -3345,7 +3345,7 @@ directive) for only those methods that are likely to be extended in Perl. </p> -<H3><a name="Perl5_nn53"></a>33.11.6 Typemaps</H3> +<H3><a name="Perl5_nn53">33.11.6 Typemaps</a></H3> <p> diff --git a/Doc/Manual/Php.html b/Doc/Manual/Php.html index 623adb68a..e1adce5ad 100644 --- a/Doc/Manual/Php.html +++ b/Doc/Manual/Php.html @@ -7,7 +7,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Php"></a>34 SWIG and PHP</H1> +<H1><a name="Php">34 SWIG and PHP</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -80,7 +80,7 @@ your extension into php directly, you will need the complete PHP source tree available. </p> -<H2><a name="Php_nn1"></a>34.1 Generating PHP Extensions</H2> +<H2><a name="Php_nn1">34.1 Generating PHP Extensions</a></H2> <p> @@ -125,7 +125,7 @@ and it doesn't play nicely with package system. We don't recommend this approach, or provide explicit support for it. </p> -<H3><a name="Php_nn1_1"></a>34.1.1 Building a loadable extension</H3> +<H3><a name="Php_nn1_1">34.1.1 Building a loadable extension</a></H3> <p> @@ -140,7 +140,7 @@ least work for Linux though): gcc -shared example_wrap.o example.o -o example.so </pre></div> -<H3><a name="Php_nn1_3"></a>34.1.2 Using PHP Extensions</H3> +<H3><a name="Php_nn1_3">34.1.2 Using PHP Extensions</a></H3> <p> @@ -188,7 +188,7 @@ This PHP module also defines the PHP classes for the wrapped API, so you'll almost certainly want to include it anyway. </p> -<H2><a name="Php_nn2"></a>34.2 Basic PHP interface</H2> +<H2><a name="Php_nn2">34.2 Basic PHP interface</a></H2> <p> @@ -199,7 +199,7 @@ other symbols unless care is taken to <tt>%rename</tt> them. At present SWIG doesn't have support for the namespace feature added in PHP 5.3. </p> -<H3><a name="Php_nn2_1"></a>34.2.1 Constants</H3> +<H3><a name="Php_nn2_1">34.2.1 Constants</a></H3> <p> @@ -276,7 +276,7 @@ is treated as true by the if test, when the value of the intended constant would be treated as false! </p> -<H3><a name="Php_nn2_2"></a>34.2.2 Global Variables</H3> +<H3><a name="Php_nn2_2">34.2.2 Global Variables</a></H3> <p> @@ -325,7 +325,7 @@ undefined. At this time SWIG does not support custom accessor methods. </p> -<H3><a name="Php_nn2_3"></a>34.2.3 Functions</H3> +<H3><a name="Php_nn2_3">34.2.3 Functions</a></H3> <p> @@ -378,7 +378,7 @@ print $s; # The value of $s was not changed. --> -<H3><a name="Php_nn2_4"></a>34.2.4 Overloading</H3> +<H3><a name="Php_nn2_4">34.2.4 Overloading</a></H3> <p> @@ -434,7 +434,7 @@ taking the integer argument. </p> --> -<H3><a name="Php_nn2_5"></a>34.2.5 Pointers and References</H3> +<H3><a name="Php_nn2_5">34.2.5 Pointers and References</a></H3> <p> @@ -579,7 +579,7 @@ PHP in a number of ways: by using <tt>unset</tt> on an existing variable, or assigning <tt>NULL</tt> to a variable. </p> -<H3><a name="Php_nn2_6"></a>34.2.6 Structures and C++ classes</H3> +<H3><a name="Php_nn2_6">34.2.6 Structures and C++ classes</a></H3> <p> @@ -640,7 +640,7 @@ Would be used in the following way from PHP5: Member variables and methods are accessed using the <tt>-></tt> operator. </p> -<H4><a name="Php_nn2_6_1"></a>34.2.6.1 Using <tt>-noproxy</tt></H4> +<H4><a name="Php_nn2_6_1">34.2.6.1 Using <tt>-noproxy</tt></a></H4> <p> @@ -666,7 +666,7 @@ Complex_im_set($obj,$d); Complex_im_get($obj); </pre></div> -<H4><a name="Php_nn2_6_2"></a>34.2.6.2 Constructors and Destructors</H4> +<H4><a name="Php_nn2_6_2">34.2.6.2 Constructors and Destructors</a></H4> <p> @@ -707,7 +707,7 @@ the programmer can either reassign the variable or call <tt>unset($v)</tt> </p> -<H4><a name="Php_nn2_6_3"></a>34.2.6.3 Static Member Variables</H4> +<H4><a name="Php_nn2_6_3">34.2.6.3 Static Member Variables</a></H4> <p> @@ -750,7 +750,7 @@ Ko::threats(10); echo "There have now been " . Ko::threats() . " threats\n"; </pre></div> -<H4><a name="Php_nn2_6_4"></a>34.2.6.4 Static Member Functions</H4> +<H4><a name="Php_nn2_6_4">34.2.6.4 Static Member Functions</a></H4> <p> @@ -772,7 +772,7 @@ Ko::threats(); </pre></div> -<H4><a name="Php_nn2_6_5"></a>34.2.6.5 Specifying Implemented Interfaces</H4> +<H4><a name="Php_nn2_6_5">34.2.6.5 Specifying Implemented Interfaces</a></H4> <p> @@ -790,7 +790,7 @@ so: If there are multiple interfaces, just list them separated by commas. </p> -<H3><a name="Php_nn2_7"></a>34.2.7 PHP Pragmas, Startup and Shutdown code</H3> +<H3><a name="Php_nn2_7">34.2.7 PHP Pragmas, Startup and Shutdown code</a></H3> <p> @@ -878,7 +878,7 @@ The <tt>%rinit</tt> and <tt>%rshutdown</tt> statements are very similar but inse into the request init (PHP_RINIT_FUNCTION) and request shutdown (PHP_RSHUTDOWN_FUNCTION) code respectively. </p> -<H2><a name="Php_nn3"></a>34.3 Cross language polymorphism</H2> +<H2><a name="Php_nn3">34.3 Cross language polymorphism</a></H2> <p> @@ -913,7 +913,7 @@ wrapper functions takes care of all the cross-language method routing transparently. </p> -<H3><a name="Php_nn3_1"></a>34.3.1 Enabling directors</H3> +<H3><a name="Php_nn3_1">34.3.1 Enabling directors</a></H3> <p> @@ -1002,7 +1002,7 @@ class MyFoo extends Foo { </div> -<H3><a name="Php_nn3_2"></a>34.3.2 Director classes</H3> +<H3><a name="Php_nn3_2">34.3.2 Director classes</a></H3> @@ -1082,7 +1082,7 @@ so there is no need for the extra overhead involved with routing the calls through PHP. </p> -<H3><a name="Php_nn3_3"></a>34.3.3 Ownership and object destruction</H3> +<H3><a name="Php_nn3_3">34.3.3 Ownership and object destruction</a></H3> <p> @@ -1138,7 +1138,7 @@ In this example, we are assuming that FooContainer will take care of deleting all the Foo pointers it contains at some point. </p> -<H3><a name="Php_nn3_4"></a>34.3.4 Exception unrolling</H3> +<H3><a name="Php_nn3_4">34.3.4 Exception unrolling</a></H3> <p> @@ -1197,7 +1197,7 @@ Swig::DirectorMethodException is thrown, PHP will register the exception as soon as the C wrapper function returns. </p> -<H3><a name="Php_nn3_5"></a>34.3.5 Overhead and code bloat</H3> +<H3><a name="Php_nn3_5">34.3.5 Overhead and code bloat</a></H3> <p> @@ -1230,7 +1230,7 @@ optimized by selectively enabling director methods (using the %feature directive) for only those methods that are likely to be extended in PHP. </p> -<H3><a name="Php_nn3_6"></a>34.3.6 Typemaps</H3> +<H3><a name="Php_nn3_6">34.3.6 Typemaps</a></H3> <p> @@ -1244,7 +1244,7 @@ need to be supported. </p> -<H3><a name="Php_nn3_7"></a>34.3.7 Miscellaneous</H3> +<H3><a name="Php_nn3_7">34.3.7 Miscellaneous</a></H3> <p> Director typemaps for STL classes are mostly in place, and hence you diff --git a/Doc/Manual/Pike.html b/Doc/Manual/Pike.html index 44c6930f8..c7e75d00c 100644 --- a/Doc/Manual/Pike.html +++ b/Doc/Manual/Pike.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Pike"></a>35 SWIG and Pike</H1> +<H1><a name="Pike">35 SWIG and Pike</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -46,10 +46,10 @@ least, make sure you read the "<a href="SWIG.html#SWIG">SWIG Basics</a>" chapter.<br> </p> -<H2><a name="Pike_nn2"></a>35.1 Preliminaries</H2> +<H2><a name="Pike_nn2">35.1 Preliminaries</a></H2> -<H3><a name="Pike_nn3"></a>35.1.1 Running SWIG</H3> +<H3><a name="Pike_nn3">35.1.1 Running SWIG</a></H3> <p> @@ -94,7 +94,7 @@ can use the <tt>-o</tt> option: <div class="code"> <pre>$ <b>swig -pike -o pseudonym.c example.i</b><br></pre> </div> -<H3><a name="Pike_nn4"></a>35.1.2 Getting the right header files</H3> +<H3><a name="Pike_nn4">35.1.2 Getting the right header files</a></H3> <p> @@ -114,7 +114,7 @@ You're looking for files with the names <tt>global.h</tt>, <tt>program.h</tt> and so on. </p> -<H3><a name="Pike_nn5"></a>35.1.3 Using your module</H3> +<H3><a name="Pike_nn5">35.1.3 Using your module</a></H3> <p> @@ -129,10 +129,10 @@ Pike v7.4 release 10 running Hilfe v3.5 (Incremental Pike Frontend) (1) Result: 24 </pre></div> -<H2><a name="Pike_nn6"></a>35.2 Basic C/C++ Mapping</H2> +<H2><a name="Pike_nn6">35.2 Basic C/C++ Mapping</a></H2> -<H3><a name="Pike_nn7"></a>35.2.1 Modules</H3> +<H3><a name="Pike_nn7">35.2.1 Modules</a></H3> <p> @@ -143,7 +143,7 @@ concerned), SWIG's <tt>%module</tt> directive doesn't really have any significance. </p> -<H3><a name="Pike_nn8"></a>35.2.2 Functions</H3> +<H3><a name="Pike_nn8">35.2.2 Functions</a></H3> <p> @@ -168,7 +168,7 @@ exactly as you'd expect it to: (1) Result: 24 </pre></div> -<H3><a name="Pike_nn9"></a>35.2.3 Global variables</H3> +<H3><a name="Pike_nn9">35.2.3 Global variables</a></H3> <p> @@ -197,7 +197,7 @@ will result in two functions, <tt>Foo_get()</tt> and <tt>Foo_set()</tt>: (3) Result: 3.141590 </pre></div> -<H3><a name="Pike_nn10"></a>35.2.4 Constants and enumerated types</H3> +<H3><a name="Pike_nn10">35.2.4 Constants and enumerated types</a></H3> <p> @@ -205,7 +205,7 @@ Enumerated types in C/C++ declarations are wrapped as Pike constants, not as Pike enums. </p> -<H3><a name="Pike_nn11"></a>35.2.5 Constructors and Destructors</H3> +<H3><a name="Pike_nn11">35.2.5 Constructors and Destructors</a></H3> <p> @@ -213,7 +213,7 @@ Constructors are wrapped as <tt>create()</tt> methods, and destructors are wrapped as <tt>destroy()</tt> methods, for Pike classes. </p> -<H3><a name="Pike_nn12"></a>35.2.6 Static Members</H3> +<H3><a name="Pike_nn12">35.2.6 Static Members</a></H3> <p> diff --git a/Doc/Manual/Preface.html b/Doc/Manual/Preface.html index 6ddea588a..186bc415d 100644 --- a/Doc/Manual/Preface.html +++ b/Doc/Manual/Preface.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Preface"></a>1 Preface</H1> +<H1><a name="Preface">1 Preface</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -35,7 +35,7 @@ -<H2><a name="Preface_nn2"></a>1.1 Introduction</H2> +<H2><a name="Preface_nn2">1.1 Introduction</a></H2> <p> @@ -58,7 +58,7 @@ has since evolved into a general purpose tool that is used in a wide variety of applications--in fact almost anything where C/C++ programming is involved. -<H2><a name="Preface_nn4"></a>1.2 SWIG Versions</H2> +<H2><a name="Preface_nn4">1.2 SWIG Versions</a></H2> <p> @@ -70,7 +70,7 @@ An official stable version was released along with the decision to make SWIG license changes and this gave rise to version 2.0.0 in 2010. </p> -<H2><a name="Preface_license"></a>1.3 SWIG License</H2> +<H2><a name="Preface_license">1.3 SWIG License</a></H2> <p> @@ -86,7 +86,7 @@ under license terms of the user's choice/requirements and at the same time the S source was placed under the GNU General Public License version 3. </p> -<H2><a name="Preface_nn5"></a>1.4 SWIG resources</H2> +<H2><a name="Preface_nn5">1.4 SWIG resources</a></H2> <p> @@ -126,7 +126,7 @@ about this can be obtained at: -<H2><a name="Preface_nn6"></a>1.5 Prerequisites</H2> +<H2><a name="Preface_nn6">1.5 Prerequisites</a></H2> <p> @@ -151,7 +151,7 @@ However, this isn't meant to be a tutorial on C++ programming. For many of the gory details, you will almost certainly want to consult a good C++ reference. If you don't program in C++, you may just want to skip those parts of the manual. -<H2><a name="Preface_nn7"></a>1.6 Organization of this manual</H2> +<H2><a name="Preface_nn7">1.6 Organization of this manual</a></H2> <p> @@ -163,7 +163,7 @@ can probably skip to that chapter and find almost everything you need to know. </p> -<H2><a name="Preface_nn8"></a>1.7 How to avoid reading the manual</H2> +<H2><a name="Preface_nn8">1.7 How to avoid reading the manual</a></H2> <p> @@ -175,7 +175,7 @@ The SWIG distribution also comes with a large directory of examples that illustrate different topics. </p> -<H2><a name="Preface_nn9"></a>1.8 Backwards compatibility</H2> +<H2><a name="Preface_nn9">1.8 Backwards compatibility</a></H2> <p> @@ -211,7 +211,7 @@ Note: The version symbol is not defined in the generated SWIG wrapper file. The SWIG preprocessor has defined SWIG_VERSION since SWIG-1.3.11. </p> -<H2><a name="Preface_release_notes"></a>1.9 Release notes</H2> +<H2><a name="Preface_release_notes">1.9 Release notes</a></H2> <p> @@ -220,7 +220,7 @@ contain, respectively, detailed release notes for the current version, detailed release notes for previous releases and summary release notes from SWIG-1.3.22 onwards. </p> -<H2><a name="Preface_nn10"></a>1.10 Credits</H2> +<H2><a name="Preface_nn10">1.10 Credits</a></H2> <p> @@ -233,7 +233,7 @@ who have made contributions at all levels over time. Contributors are mentioned either in the COPYRIGHT file or CHANGES files shipped with SWIG or in submitted bugs. </p> -<H2><a name="Preface_nn11"></a>1.11 Bug reports</H2> +<H2><a name="Preface_nn11">1.11 Bug reports</a></H2> <p> @@ -248,10 +248,10 @@ used, and any important pieces of the SWIG generated wrapper code. We can only fix bugs if we know about them. </p> -<H2><a name="Preface_installation"></a>1.12 Installation</H2> +<H2><a name="Preface_installation">1.12 Installation</a></H2> -<H3><a name="Preface_windows_installation"></a>1.12.1 Windows installation</H3> +<H3><a name="Preface_windows_installation">1.12.1 Windows installation</a></H3> <p> @@ -262,7 +262,7 @@ the top level directory. Otherwise it is exactly the same as the main SWIG distribution. There is no need to download anything else. </p> -<H3><a name="Preface_unix_installation"></a>1.12.2 Unix installation</H3> +<H3><a name="Preface_unix_installation">1.12.2 Unix installation</a></H3> <p> @@ -350,7 +350,7 @@ a number of packages to be installed. Full instructions at </li> </ul> -<H3><a name="Preface_osx_installation"></a>1.12.3 Macintosh OS X installation</H3> +<H3><a name="Preface_osx_installation">1.12.3 Macintosh OS X installation</a></H3> <p> @@ -378,7 +378,7 @@ Darwin's two-level namespaces. Some details about this can be found here Needless to say, you might have to experiment a bit to get things working at first. </p> -<H3><a name="Preface_testing"></a>1.12.4 Testing</H3> +<H3><a name="Preface_testing">1.12.4 Testing</a></H3> <p> @@ -432,7 +432,7 @@ have many different target languages installed and a slow machine, it might take more than an hour to run the test-suite. </p> -<H3><a name="Preface_examples"></a>1.12.5 Examples</H3> +<H3><a name="Preface_examples">1.12.5 Examples</a></H3> <p> diff --git a/Doc/Manual/Preprocessor.html b/Doc/Manual/Preprocessor.html index e188fc0be..b8a6e9b0e 100644 --- a/Doc/Manual/Preprocessor.html +++ b/Doc/Manual/Preprocessor.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Preprocessor"></a>8 Preprocessing</H1> +<H1><a name="Preprocessor">8 Preprocessing</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -37,7 +37,7 @@ However, a number of modifications and enhancements have been made. This chapter describes some of these modifications. </p> -<H2><a name="Preprocessor_nn2"></a>8.1 File inclusion</H2> +<H2><a name="Preprocessor_nn2">8.1 File inclusion</a></H2> <p> @@ -63,7 +63,7 @@ By default, the <tt>#include</tt> is ignored unless you run SWIG with the is that you often don't want SWIG to try and wrap everything included in standard header system headers and auxiliary files. -<H2><a name="Preprocessor_nn3"></a>8.2 File imports</H2> +<H2><a name="Preprocessor_nn3">8.2 File imports</a></H2> <p> @@ -92,7 +92,7 @@ The <tt>-importall</tt> directive tells SWIG to follow all <tt>#include</tt> sta as imports. This might be useful if you want to extract type definitions from system header files without generating any wrappers. -<H2><a name="Preprocessor_condition_compilation"></a>8.3 Conditional Compilation</H2> +<H2><a name="Preprocessor_condition_compilation">8.3 Conditional Compilation</a></H2> <p> @@ -156,7 +156,7 @@ SWIG (except for the symbol `<tt>SWIG</tt>' which is only defined within the SWIG compiler). </p> -<H2><a name="Preprocessor_nn5"></a>8.4 Macro Expansion</H2> +<H2><a name="Preprocessor_nn5">8.4 Macro Expansion</a></H2> <p> @@ -211,7 +211,7 @@ like <tt>#x</tt>. This is a non-standard SWIG extension. </li> </ul> -<H2><a name="Preprocessor_nn6"></a>8.5 SWIG Macros</H2> +<H2><a name="Preprocessor_nn6">8.5 SWIG Macros</a></H2> <p> @@ -257,7 +257,7 @@ many of SWIG's advanced features and libraries are built using this mechanism (s support). </p> -<H2><a name="Preprocessor_nn7"></a>8.6 C99 and GNU Extensions</H2> +<H2><a name="Preprocessor_nn7">8.6 C99 and GNU Extensions</a></H2> <p> @@ -313,14 +313,14 @@ interface building. However, they are used internally to implement a number of SWIG directives and are provided to make SWIG more compatible with C99 code. </p> -<H2><a name="Preprocessor_delimiters"></a>8.7 Preprocessing and delimiters</H2> +<H2><a name="Preprocessor_delimiters">8.7 Preprocessing and delimiters</a></H2> <p> The preprocessor handles { }, " " and %{ %} delimiters differently. </p> -<H3><a name="Preprocessor_nn8"></a>8.7.1 Preprocessing and %{ ... %} & " ... " delimiters</H3> +<H3><a name="Preprocessor_nn8">8.7.1 Preprocessing and %{ ... %} & " ... " delimiters</a></H3> <p> @@ -345,7 +345,7 @@ the contents of the <tt>%{ ... %}</tt> block are copied without modification to the output (including all preprocessor directives). </p> -<H3><a name="Preprocessor_nn9"></a>8.7.2 Preprocessing and { ... } delimiters</H3> +<H3><a name="Preprocessor_nn9">8.7.2 Preprocessing and { ... } delimiters</a></H3> <p> @@ -387,7 +387,7 @@ to actually go into the wrapper file, prefix the preprocessor directives with <t SWIG will strip the extra <tt>%</tt> and leave the preprocessor directive in the code. </p> -<H2><a name="Preprocessor_typemap_delimiters"></a>8.8 Preprocessor and Typemaps</H2> +<H2><a name="Preprocessor_typemap_delimiters">8.8 Preprocessor and Typemaps</a></H2> <p> @@ -458,7 +458,7 @@ would generate </div> -<H2><a name="Preprocessor_nn10"></a>8.9 Viewing preprocessor output</H2> +<H2><a name="Preprocessor_nn10">8.9 Viewing preprocessor output</a></H2> <p> @@ -468,7 +468,7 @@ Instead the results after the preprocessor has run are displayed. This might be useful as an aid to debugging and viewing the results of macro expansions. </p> -<H2><a name="Preprocessor_warning_error"></a>8.10 The #error and #warning directives</H2> +<H2><a name="Preprocessor_warning_error">8.10 The #error and #warning directives</a></H2> <p> diff --git a/Doc/Manual/Python.html b/Doc/Manual/Python.html index c5219b693..c288581b7 100644 --- a/Doc/Manual/Python.html +++ b/Doc/Manual/Python.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Python"></a>36 SWIG and Python</H1> +<H1><a name="Python">36 SWIG and Python</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -148,7 +148,7 @@ very least, make sure you read the "<a href="SWIG.html#SWIG">SWIG Basics</a>" chapter. </p> -<H2><a name="Python_nn2"></a>36.1 Overview</H2> +<H2><a name="Python_nn2">36.1 Overview</a></H2> <p> @@ -175,10 +175,10 @@ described followed by a discussion of low-level implementation details. </p> -<H2><a name="Python_nn3"></a>36.2 Preliminaries</H2> +<H2><a name="Python_nn3">36.2 Preliminaries</a></H2> -<H3><a name="Python_nn4"></a>36.2.1 Running SWIG</H3> +<H3><a name="Python_nn4">36.2.1 Running SWIG</a></H3> <p> @@ -276,7 +276,7 @@ The following sections have further practical examples and details on how you might go about compiling and using the generated files. </p> -<H3><a name="Python_nn6"></a>36.2.2 Using distutils</H3> +<H3><a name="Python_nn6">36.2.2 Using distutils</a></H3> <p> @@ -368,7 +368,7 @@ This same approach works on all platforms if the appropriate compiler is install can even build extensions to the standard Windows Python using MingGW) </p> -<H3><a name="Python_nn7"></a>36.2.3 Hand compiling a dynamic module</H3> +<H3><a name="Python_nn7">36.2.3 Hand compiling a dynamic module</a></H3> <p> @@ -416,7 +416,7 @@ module actually consists of two files; <tt>socket.py</tt> and </p> -<H3><a name="Python_nn8"></a>36.2.4 Static linking</H3> +<H3><a name="Python_nn8">36.2.4 Static linking</a></H3> <p> @@ -495,7 +495,7 @@ If using static linking, you might want to rely on a different approach (perhaps using distutils). </p> -<H3><a name="Python_nn9"></a>36.2.5 Using your module</H3> +<H3><a name="Python_nn9">36.2.5 Using your module</a></H3> <p> @@ -652,7 +652,7 @@ system configuration (this requires root access and you will need to read the man pages). </p> -<H3><a name="Python_nn10"></a>36.2.6 Compilation of C++ extensions</H3> +<H3><a name="Python_nn10">36.2.6 Compilation of C++ extensions</a></H3> <p> @@ -744,7 +744,7 @@ erratic program behavior. If working with lots of software components, you might want to investigate using a more formal standard such as COM. </p> -<H3><a name="Python_nn11"></a>36.2.7 Compiling for 64-bit platforms</H3> +<H3><a name="Python_nn11">36.2.7 Compiling for 64-bit platforms</a></H3> <p> @@ -781,7 +781,7 @@ and -m64 allow you to choose the desired binary format for your python extension. </p> -<H3><a name="Python_nn12"></a>36.2.8 Building Python Extensions under Windows</H3> +<H3><a name="Python_nn12">36.2.8 Building Python Extensions under Windows</a></H3> <p> @@ -910,7 +910,7 @@ SWIG Wiki</a>. </p> -<H2><a name="Python_nn13"></a>36.3 A tour of basic C/C++ wrapping</H2> +<H2><a name="Python_nn13">36.3 A tour of basic C/C++ wrapping</a></H2> <p> @@ -919,7 +919,7 @@ to your C/C++ code. Functions are wrapped as functions, classes are wrapped as This section briefly covers the essential aspects of this wrapping. </p> -<H3><a name="Python_nn14"></a>36.3.1 Modules</H3> +<H3><a name="Python_nn14">36.3.1 Modules</a></H3> <p> @@ -932,7 +932,7 @@ module name, make sure you don't use the same name as a built-in Python command or standard module name. </p> -<H3><a name="Python_nn15"></a>36.3.2 Functions</H3> +<H3><a name="Python_nn15">36.3.2 Functions</a></H3> <p> @@ -956,7 +956,7 @@ like you think it does: >>> </pre></div> -<H3><a name="Python_nn16"></a>36.3.3 Global variables</H3> +<H3><a name="Python_nn16">36.3.3 Global variables</a></H3> <p> @@ -1094,7 +1094,7 @@ that starts with a leading underscore. SWIG does not create <tt>cvar</tt> if there are no global variables in a module. </p> -<H3><a name="Python_nn17"></a>36.3.4 Constants and enums</H3> +<H3><a name="Python_nn17">36.3.4 Constants and enums</a></H3> <p> @@ -1134,7 +1134,7 @@ other object. Unfortunately, there is no easy way for SWIG to generate code that prevents this. You will just have to be careful. </p> -<H3><a name="Python_nn18"></a>36.3.5 Pointers</H3> +<H3><a name="Python_nn18">36.3.5 Pointers</a></H3> <p> @@ -1275,7 +1275,7 @@ C-style cast may return a bogus result whereas as the C++-style cast will return <tt>None</tt> if the conversion can't be performed. </p> -<H3><a name="Python_nn19"></a>36.3.6 Structures</H3> +<H3><a name="Python_nn19">36.3.6 Structures</a></H3> <p> @@ -1464,7 +1464,7 @@ everything works just like you would expect. For example: </pre> </div> -<H3><a name="Python_nn20"></a>36.3.7 C++ classes</H3> +<H3><a name="Python_nn20">36.3.7 C++ classes</a></H3> <p> @@ -1553,7 +1553,7 @@ they are accessed through <tt>cvar</tt> like this: </pre> </div> -<H3><a name="Python_nn21"></a>36.3.8 C++ inheritance</H3> +<H3><a name="Python_nn21">36.3.8 C++ inheritance</a></H3> <p> @@ -1608,7 +1608,7 @@ then the function <tt>spam()</tt> accepts <tt>Foo *</tt> or a pointer to any cla It is safe to use multiple inheritance with SWIG. </p> -<H3><a name="Python_nn22"></a>36.3.9 Pointers, references, values, and arrays</H3> +<H3><a name="Python_nn22">36.3.9 Pointers, references, values, and arrays</a></H3> <p> @@ -1669,7 +1669,7 @@ treated as a returning value, and it will follow the same allocation/deallocation process. </p> -<H3><a name="Python_nn23"></a>36.3.10 C++ overloaded functions</H3> +<H3><a name="Python_nn23">36.3.10 C++ overloaded functions</a></H3> <p> @@ -1792,7 +1792,7 @@ first declaration takes precedence. Please refer to the "SWIG and C++" chapter for more information about overloading. </p> -<H3><a name="Python_nn24"></a>36.3.11 C++ operators</H3> +<H3><a name="Python_nn24">36.3.11 C++ operators</a></H3> <p> @@ -1881,7 +1881,7 @@ Also, be aware that certain operators don't map cleanly to Python. For instance overloaded assignment operators don't map to Python semantics and will be ignored. </p> -<H3><a name="Python_nn25"></a>36.3.12 C++ namespaces</H3> +<H3><a name="Python_nn25">36.3.12 C++ namespaces</a></H3> <p> @@ -1948,7 +1948,7 @@ utilizes thousands of small deeply nested namespaces each with identical symbol names, well, then you get what you deserve. </p> -<H3><a name="Python_nn26"></a>36.3.13 C++ templates</H3> +<H3><a name="Python_nn26">36.3.13 C++ templates</a></H3> <p> @@ -2002,10 +2002,10 @@ Some more complicated examples will appear later. </p> -<H3><a name="Python_nn27"></a>36.3.14 C++ Smart Pointers</H3> +<H3><a name="Python_nn27">36.3.14 C++ Smart Pointers</a></H3> -<H4><a name="Python_smart_pointers_shared_ptr"></a>36.3.14.1 The shared_ptr Smart Pointer</H4> +<H4><a name="Python_smart_pointers_shared_ptr">36.3.14.1 The shared_ptr Smart Pointer</a></H4> <p> @@ -2016,7 +2016,7 @@ in the <a href="Library.html#Library_std_shared_ptr">shared_ptr smart pointer</a </p> -<H4><a name="Python_smart_pointers_generic"></a>36.3.14.2 Generic Smart Pointers</H4> +<H4><a name="Python_smart_pointers_generic">36.3.14.2 Generic Smart Pointers</a></H4> <p> @@ -2100,7 +2100,7 @@ simply use the <tt>__deref__()</tt> method. For example: </pre> </div> -<H3><a name="Python_nn27a"></a>36.3.15 C++ reference counted objects</H3> +<H3><a name="Python_nn27a">36.3.15 C++ reference counted objects</a></H3> <p> @@ -2109,7 +2109,7 @@ Python examples of memory management using referencing counting. </p> -<H2><a name="Python_nn28"></a>36.4 Further details on the Python class interface</H2> +<H2><a name="Python_nn28">36.4 Further details on the Python class interface</a></H2> <p> @@ -2132,7 +2132,7 @@ the <tt>-builtin</tt> option are in the <a href="#Python_builtin_types">Built-in section. </p> -<H3><a name="Python_nn29"></a>36.4.1 Proxy classes</H3> +<H3><a name="Python_nn29">36.4.1 Proxy classes</a></H3> <p> @@ -2221,7 +2221,7 @@ you can attach new Python methods to the class and you can even inherit from it by Python built-in types until Python 2.2). </p> -<H3><a name="Python_builtin_types"></a>36.4.2 Built-in Types</H3> +<H3><a name="Python_builtin_types">36.4.2 Built-in Types</a></H3> <p> @@ -2265,7 +2265,7 @@ please refer to the python documentation:</p> <p><a href="http://docs.python.org/extending/newtypes.html">http://docs.python.org/extending/newtypes.html</a></p> -<H4><a name="Python_builtin_limitations"></a>36.4.2.1 Limitations</H4> +<H4><a name="Python_builtin_limitations">36.4.2.1 Limitations</a></H4> <p>Use of the <tt>-builtin</tt> option implies a couple of limitations: @@ -2433,7 +2433,7 @@ assert(issubclass(B.Derived, A.Base)) </li> </ul> -<H4><a name="Python_builtin_overloads"></a>36.4.2.2 Operator overloads -- use them!</H4> +<H4><a name="Python_builtin_overloads">36.4.2.2 Operator overloads -- use them!</a></H4> <p>The entire justification for the <tt>-builtin</tt> option is improved @@ -2534,7 +2534,7 @@ structs. </p> -<H3><a name="Python_nn30"></a>36.4.3 Memory management</H3> +<H3><a name="Python_nn30">36.4.3 Memory management</a></H3> <p>NOTE: Although this section refers to proxy objects, everything here also applies @@ -2729,7 +2729,7 @@ It is also possible to deal with situations like this using typemaps--an advanced topic discussed later. </p> -<H3><a name="Python_nn31"></a>36.4.4 Python 2.2 and classic classes</H3> +<H3><a name="Python_nn31">36.4.4 Python 2.2 and classic classes</a></H3> <p> @@ -2766,7 +2766,7 @@ class itself. In Python-2.1 and earlier, they have to be accessed as a global function or through an instance (see the earlier section). </p> -<H2><a name="Python_directors"></a>36.5 Cross language polymorphism</H2> +<H2><a name="Python_directors">36.5 Cross language polymorphism</a></H2> <p> @@ -2800,7 +2800,7 @@ proxy classes, director classes, and C wrapper functions takes care of all the cross-language method routing transparently. </p> -<H3><a name="Python_nn33"></a>36.5.1 Enabling directors</H3> +<H3><a name="Python_nn33">36.5.1 Enabling directors</a></H3> <p> @@ -2892,7 +2892,7 @@ class MyFoo(mymodule.Foo): </div> -<H3><a name="Python_nn34"></a>36.5.2 Director classes</H3> +<H3><a name="Python_nn34">36.5.2 Director classes</a></H3> @@ -2974,7 +2974,7 @@ so there is no need for the extra overhead involved with routing the calls through Python. </p> -<H3><a name="Python_nn35"></a>36.5.3 Ownership and object destruction</H3> +<H3><a name="Python_nn35">36.5.3 Ownership and object destruction</a></H3> <p> @@ -3041,7 +3041,7 @@ deleting all the Foo pointers it contains at some point. Note that no hard references to the Foo objects remain in Python. </p> -<H3><a name="Python_nn36"></a>36.5.4 Exception unrolling</H3> +<H3><a name="Python_nn36">36.5.4 Exception unrolling</a></H3> <p> @@ -3100,7 +3100,7 @@ Swig::DirectorMethodException is thrown, Python will register the exception as soon as the C wrapper function returns. </p> -<H3><a name="Python_nn37"></a>36.5.5 Overhead and code bloat</H3> +<H3><a name="Python_nn37">36.5.5 Overhead and code bloat</a></H3> <p> @@ -3134,7 +3134,7 @@ directive) for only those methods that are likely to be extended in Python. </p> -<H3><a name="Python_nn38"></a>36.5.6 Typemaps</H3> +<H3><a name="Python_nn38">36.5.6 Typemaps</a></H3> <p> @@ -3148,7 +3148,7 @@ need to be supported. </p> -<H3><a name="Python_nn39"></a>36.5.7 Miscellaneous</H3> +<H3><a name="Python_nn39">36.5.7 Miscellaneous</a></H3> <p> @@ -3195,7 +3195,7 @@ methods that return const references. </p> -<H2><a name="Python_nn40"></a>36.6 Common customization features</H2> +<H2><a name="Python_nn40">36.6 Common customization features</a></H2> <p> @@ -3208,7 +3208,7 @@ This section describes some common SWIG features that are used to improve your the interface to an extension module. </p> -<H3><a name="Python_nn41"></a>36.6.1 C/C++ helper functions</H3> +<H3><a name="Python_nn41">36.6.1 C/C++ helper functions</a></H3> <p> @@ -3289,7 +3289,7 @@ hard to implement. It is possible to clean this up using Python code, typemaps, customization features as covered in later sections. </p> -<H3><a name="Python_nn42"></a>36.6.2 Adding additional Python code</H3> +<H3><a name="Python_nn42">36.6.2 Adding additional Python code</a></H3> <p> @@ -3541,7 +3541,7 @@ The same applies for overloaded constructors. </p> -<H3><a name="Python_nn43"></a>36.6.3 Class extension with %extend</H3> +<H3><a name="Python_nn43">36.6.3 Class extension with %extend</a></H3> <p> @@ -3630,7 +3630,7 @@ Vector(12,14,16) in any way---the extensions only show up in the Python interface. </p> -<H3><a name="Python_nn44"></a>36.6.4 Exception handling with %exception</H3> +<H3><a name="Python_nn44">36.6.4 Exception handling with %exception</a></H3> <p> @@ -3756,7 +3756,7 @@ The language-independent <tt>exception.i</tt> library file can also be used to raise exceptions. See the <a href="Library.html#Library">SWIG Library</a> chapter. </p> -<H2><a name="Python_nn45"></a>36.7 Tips and techniques</H2> +<H2><a name="Python_nn45">36.7 Tips and techniques</a></H2> <p> @@ -3766,7 +3766,7 @@ strings, binary data, and arrays. This chapter discusses the common techniques solving these problems. </p> -<H3><a name="Python_nn46"></a>36.7.1 Input and output parameters</H3> +<H3><a name="Python_nn46">36.7.1 Input and output parameters</a></H3> <p> @@ -3979,7 +3979,7 @@ void foo(Bar *OUTPUT); may not have the intended effect since <tt>typemaps.i</tt> does not define an OUTPUT rule for <tt>Bar</tt>. </p> -<H3><a name="Python_nn47"></a>36.7.2 Simple pointers</H3> +<H3><a name="Python_nn47">36.7.2 Simple pointers</a></H3> <p> @@ -4048,7 +4048,7 @@ If you replace <tt>%pointer_functions()</tt> by <tt>%pointer_class(type,name)</t See the <a href="Library.html#Library">SWIG Library</a> chapter for further details. </p> -<H3><a name="Python_nn48"></a>36.7.3 Unbounded C Arrays</H3> +<H3><a name="Python_nn48">36.7.3 Unbounded C Arrays</a></H3> <p> @@ -4110,7 +4110,7 @@ well suited for applications in which you need to create buffers, package binary data, etc. </p> -<H3><a name="Python_nn49"></a>36.7.4 String handling</H3> +<H3><a name="Python_nn49">36.7.4 String handling</a></H3> <p> @@ -4180,7 +4180,7 @@ also be used to extra binary data from arbitrary pointers. </p> -<H3><a name="Python_default_args"></a>36.7.5 Default arguments</H3> +<H3><a name="Python_default_args">36.7.5 Default arguments</a></H3> <p> @@ -4279,7 +4279,7 @@ Versions of SWIG prior to this varied in their ability to convert C++ default va equivalent Python default argument values. </p> -<H2><a name="Python_nn53"></a>36.8 Typemaps</H2> +<H2><a name="Python_nn53">36.8 Typemaps</a></H2> <p> @@ -4296,7 +4296,7 @@ Typemaps are only used if you want to change some aspect of the primitive C-Python interface or if you want to elevate your guru status. </p> -<H3><a name="Python_nn54"></a>36.8.1 What is a typemap?</H3> +<H3><a name="Python_nn54">36.8.1 What is a typemap?</a></H3> <p> @@ -4412,7 +4412,7 @@ parameter is omitted): </pre> </div> -<H3><a name="Python_nn55"></a>36.8.2 Python typemaps</H3> +<H3><a name="Python_nn55">36.8.2 Python typemaps</a></H3> <p> @@ -4453,7 +4453,7 @@ a look at the SWIG library version 1.3.20 or so. </p> -<H3><a name="Python_nn56"></a>36.8.3 Typemap variables</H3> +<H3><a name="Python_nn56">36.8.3 Typemap variables</a></H3> <p> @@ -4524,7 +4524,7 @@ properly assigned. The Python name of the wrapper function being created. </div> -<H3><a name="Python_nn57"></a>36.8.4 Useful Python Functions</H3> +<H3><a name="Python_nn57">36.8.4 Useful Python Functions</a></H3> <p> @@ -4652,7 +4652,7 @@ write me </pre> </div> -<H2><a name="Python_nn58"></a>36.9 Typemap Examples</H2> +<H2><a name="Python_nn58">36.9 Typemap Examples</a></H2> <p> @@ -4661,7 +4661,7 @@ might look at the files "<tt>python.swg</tt>" and "<tt>typemaps.i</tt>" in the SWIG library. </p> -<H3><a name="Python_nn59"></a>36.9.1 Converting Python list to a char ** </H3> +<H3><a name="Python_nn59">36.9.1 Converting Python list to a char ** </a></H3> <p> @@ -4741,7 +4741,7 @@ memory allocation is used to allocate memory for the array, the the C function. </p> -<H3><a name="Python_nn60"></a>36.9.2 Expanding a Python object into multiple arguments</H3> +<H3><a name="Python_nn60">36.9.2 Expanding a Python object into multiple arguments</a></H3> <p> @@ -4820,7 +4820,7 @@ to supply the argument count. This is automatically set by the typemap code. F </pre> </div> -<H3><a name="Python_nn61"></a>36.9.3 Using typemaps to return arguments</H3> +<H3><a name="Python_nn61">36.9.3 Using typemaps to return arguments</a></H3> <p> @@ -4908,7 +4908,7 @@ function can now be used as follows: >>> </pre></div> -<H3><a name="Python_nn62"></a>36.9.4 Mapping Python tuples into small arrays</H3> +<H3><a name="Python_nn62">36.9.4 Mapping Python tuples into small arrays</a></H3> <p> @@ -4957,7 +4957,7 @@ array, such an approach would not be recommended for huge arrays, but for small structures, this approach works fine. </p> -<H3><a name="Python_nn63"></a>36.9.5 Mapping sequences to C arrays</H3> +<H3><a name="Python_nn63">36.9.5 Mapping sequences to C arrays</a></H3> <p> @@ -5046,7 +5046,7 @@ static int convert_darray(PyObject *input, double *ptr, int size) { </pre> </div> -<H3><a name="Python_nn64"></a>36.9.6 Pointer handling</H3> +<H3><a name="Python_nn64">36.9.6 Pointer handling</a></H3> <p> @@ -5143,7 +5143,7 @@ class object (if applicable). -<H2><a name="Python_nn65"></a>36.10 Docstring Features</H2> +<H2><a name="Python_nn65">36.10 Docstring Features</a></H2> <p> @@ -5171,7 +5171,7 @@ of your users much simpler. </p> -<H3><a name="Python_nn66"></a>36.10.1 Module docstring</H3> +<H3><a name="Python_nn66">36.10.1 Module docstring</a></H3> <p> @@ -5205,7 +5205,7 @@ layout of controls on a panel, etc. to be loaded from an XML file." </div> -<H3><a name="Python_nn67"></a>36.10.2 %feature("autodoc")</H3> +<H3><a name="Python_nn67">36.10.2 %feature("autodoc")</a></H3> <p> @@ -5233,7 +5233,7 @@ four levels for autodoc controlled by the value given to the feature, <tt>%feature("autodoc", "<i>level</i>")</tt>. The four values for <i>level</i> are covered in the following sub-sections. -<H4><a name="Python_nn68"></a>36.10.2.1 %feature("autodoc", "0")</H4> +<H4><a name="Python_nn68">36.10.2.1 %feature("autodoc", "0")</a></H4> <p> @@ -5262,7 +5262,7 @@ def function_name(*args, **kwargs): </div> -<H4><a name="Python_nn69"></a>36.10.2.2 %feature("autodoc", "1")</H4> +<H4><a name="Python_nn69">36.10.2.2 %feature("autodoc", "1")</a></H4> <p> @@ -5287,7 +5287,7 @@ def function_name(*args, **kwargs): </div> -<H4><a name="Python_autodoc2"></a>36.10.2.3 %feature("autodoc", "2")</H4> +<H4><a name="Python_autodoc2">36.10.2.3 %feature("autodoc", "2")</a></H4> <p> @@ -5349,7 +5349,7 @@ def function_name(*args, **kwargs): </pre> </div> -<H4><a name="Python_autodoc3"></a>36.10.2.4 %feature("autodoc", "3")</H4> +<H4><a name="Python_autodoc3">36.10.2.4 %feature("autodoc", "3")</a></H4> <p> @@ -5375,7 +5375,7 @@ def function_name(*args, **kwargs): </div> -<H4><a name="Python_nn70"></a>36.10.2.5 %feature("autodoc", "docstring")</H4> +<H4><a name="Python_nn70">36.10.2.5 %feature("autodoc", "docstring")</a></H4> <p> @@ -5394,7 +5394,7 @@ void GetPosition(int* OUTPUT, int* OUTPUT); </div> -<H3><a name="Python_nn71"></a>36.10.3 %feature("docstring")</H3> +<H3><a name="Python_nn71">36.10.3 %feature("docstring")</a></H3> <p> @@ -5426,7 +5426,7 @@ with more than one line. </pre> </div> -<H2><a name="Python_nn72"></a>36.11 Python Packages</H2> +<H2><a name="Python_nn72">36.11 Python Packages</a></H2> <p>Python has concepts of modules and packages. Modules are separate units of @@ -5484,7 +5484,7 @@ users may need to use special features such as the <tt>package</tt> option in th <tt>%module</tt> directive or import related command line options. These are explained in the following sections.</p> -<H3><a name="Python_modulepackage"></a>36.11.1 Setting the Python package</H3> +<H3><a name="Python_modulepackage">36.11.1 Setting the Python package</a></H3> <p> @@ -5538,7 +5538,7 @@ pkg1/pkg2/_foo.so # (shared library built from C/C++ code generated by SWI </pre> </div> -<H3><a name="Python_absrelimports"></a>36.11.2 Absolute and relative imports</H3> +<H3><a name="Python_absrelimports">36.11.2 Absolute and relative imports</a></H3> <p>Suppose, we have the following hierarchy of files:</p> @@ -5677,7 +5677,7 @@ uses relative imports. Second case is, when one puts import directives in <tt>__init__.py</tt> to import symbols from submodules or subpackages and the submodule depends on other submodules (discussed later).</p> -<H3><a name="Python_absimport"></a>36.11.3 Enforcing absolute import semantics</H3> +<H3><a name="Python_absimport">36.11.3 Enforcing absolute import semantics</a></H3> <p>As you may know, there is an incompatibility in import semantics (for the @@ -5714,7 +5714,7 @@ from __future__ import absolute_import </pre> </div> -<H3><a name="Python_importfrominit"></a>36.11.4 Importing from __init__.py</H3> +<H3><a name="Python_importfrominit">36.11.4 Importing from __init__.py</a></H3> <p>Imports in <tt>__init__.py</tt> are handy when you want to populate a @@ -5825,7 +5825,7 @@ effect (note, that the Python 2 case also needs the <tt>-relativeimport</tt> workaround).</p> -<H2><a name="Python_python3support"></a>36.12 Python 3 Support</H2> +<H2><a name="Python_python3support">36.12 Python 3 Support</a></H2> <p> @@ -5852,7 +5852,7 @@ The following are Python 3.0 new features that are currently supported by SWIG. </p> -<H3><a name="Python_nn74"></a>36.12.1 Function annotation</H3> +<H3><a name="Python_nn74">36.12.1 Function annotation</a></H3> <p> @@ -5885,7 +5885,7 @@ For detailed usage of function annotation, see <a href="https://www.python.org/dev/peps/pep-3107/">PEP 3107</a>. </p> -<H3><a name="Python_nn75"></a>36.12.2 Buffer interface</H3> +<H3><a name="Python_nn75">36.12.2 Buffer interface</a></H3> <p> @@ -6037,7 +6037,7 @@ modify the buffer. </div> -<H3><a name="Python_nn76"></a>36.12.3 Abstract base classes</H3> +<H3><a name="Python_nn76">36.12.3 Abstract base classes</a></H3> <p> @@ -6078,7 +6078,7 @@ For details of abstract base class, please see <a href="https://www.python.org/dev/peps/pep-3119/">PEP 3119</a>. </p> -<H3><a name="Python_nn77"></a>36.12.4 Byte string output conversion</H3> +<H3><a name="Python_nn77">36.12.4 Byte string output conversion</a></H3> <p> @@ -6164,7 +6164,7 @@ For more details about the <tt>surrogateescape</tt> error handler, please see <a href="https://www.python.org/dev/peps/pep-0383/">PEP 383</a>. </p> -<H3><a name="Python_2_unicode"></a>36.12.5 Python 2 Unicode</H3> +<H3><a name="Python_2_unicode">36.12.5 Python 2 Unicode</a></H3> <p> diff --git a/Doc/Manual/R.html b/Doc/Manual/R.html index 50e861b22..fc60f368e 100644 --- a/Doc/Manual/R.html +++ b/Doc/Manual/R.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="R"></a>37 SWIG and R</H1> +<H1><a name="R">37 SWIG and R</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -33,7 +33,7 @@ compile and run an R interface to QuantLib running on Mandriva Linux with gcc. The R bindings also work on Microsoft Windows using Visual C++. </p> -<H2><a name="R_nn2"></a>37.1 Bugs</H2> +<H2><a name="R_nn2">37.1 Bugs</a></H2> <p> @@ -45,7 +45,7 @@ Currently the following features are not implemented or broken: <li>C Array wrappings </ul> -<H2><a name="R_nn3"></a>37.2 Using R and SWIG</H2> +<H2><a name="R_nn3">37.2 Using R and SWIG</a></H2> <p> @@ -136,7 +136,7 @@ Error in .Call("R_swig_fact", s_arg1, as.logical(.copy), PACKAGE = "example") : <li>Make sure the architecture of the shared library(x64 for instance), matches the architecture of the R program you want to load your shared library into </ul> -<H2><a name="R_nn4"></a>37.3 Precompiling large R files</H2> +<H2><a name="R_nn4">37.3 Precompiling large R files</a></H2> In cases where the R file is large, one make save a lot of loading @@ -154,7 +154,7 @@ will save a large amount of loading time. -<H2><a name="R_nn5"></a>37.4 General policy</H2> +<H2><a name="R_nn5">37.4 General policy</a></H2> <p> @@ -163,7 +163,7 @@ wrapping over the underlying functions and rely on the R type system to provide R syntax. </p> -<H2><a name="R_language_conventions"></a>37.5 Language conventions</H2> +<H2><a name="R_language_conventions">37.5 Language conventions</a></H2> <p> @@ -172,7 +172,7 @@ and [ are overloaded to allow for R syntax (one based indices and slices) </p> -<H2><a name="R_nn6"></a>37.6 C++ classes</H2> +<H2><a name="R_nn6">37.6 C++ classes</a></H2> <p> @@ -184,7 +184,7 @@ keep track of the pointer object which removes the necessity for a lot of the proxy class baggage you see in other languages. </p> -<H2><a name="R_nn7"></a>37.7 Enumerations</H2> +<H2><a name="R_nn7">37.7 Enumerations</a></H2> <p> diff --git a/Doc/Manual/Ruby.html b/Doc/Manual/Ruby.html index 2de9f673e..4663b4c95 100644 --- a/Doc/Manual/Ruby.html +++ b/Doc/Manual/Ruby.html @@ -7,7 +7,7 @@ <body bgcolor="#ffffff"> -<H1><a name="Ruby"></a>38 SWIG and Ruby</H1> +<H1><a name="Ruby">38 SWIG and Ruby</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -148,7 +148,7 @@ <p>This chapter describes SWIG's support of Ruby.</p> -<H2><a name="Ruby_nn2"></a>38.1 Preliminaries</H2> +<H2><a name="Ruby_nn2">38.1 Preliminaries</a></H2> <p> SWIG 3.0 is known to work with Ruby versions 1.8 and later. @@ -163,7 +163,7 @@ read the "<a href="SWIG.html#SWIG">SWIG Basics</a>" chapter. It is also assumed that the reader has a basic understanding of Ruby. </p> -<H3><a name="Ruby_nn3"></a>38.1.1 Running SWIG</H3> +<H3><a name="Ruby_nn3">38.1.1 Running SWIG</a></H3> <p> To build a Ruby module, run SWIG using the <tt>-ruby</tt> @@ -187,7 +187,7 @@ if compiling a C++ extension) that contains all of the code needed to build a Ruby extension module. To finish building the module, you need to compile this file and link it with the rest of your program. </p> -<H3><a name="Ruby_nn4"></a>38.1.2 Getting the right header files</H3> +<H3><a name="Ruby_nn4">38.1.2 Getting the right header files</a></H3> <p> In order to compile the wrapper code, the compiler needs the <tt>ruby.h</tt> @@ -216,7 +216,7 @@ installed, you can run Ruby to find out. For example: </p> </pre> </div> -<H3><a name="Ruby_nn5"></a>38.1.3 Compiling a dynamic module</H3> +<H3><a name="Ruby_nn5">38.1.3 Compiling a dynamic module</a></H3> <p> Ruby extension modules are typically compiled into shared @@ -289,7 +289,7 @@ manual pages for your compiler and linker to determine the correct set of options. You might also check the <a href="http://www.dabeaz.com/cgi-bin/wiki.pl">SWIG Wiki</a> for additional information. </p> -<H3><a name="Ruby_nn6"></a>38.1.4 Using your module</H3> +<H3><a name="Ruby_nn6">38.1.4 Using your module</a></H3> <p> Ruby <i>module</i> names must be capitalized, @@ -319,7 +319,7 @@ begins with: </p> <p> will result in an extension module using the feature name "example" and Ruby module name "Example". </p> -<H3><a name="Ruby_nn7"></a>38.1.5 Static linking</H3> +<H3><a name="Ruby_nn7">38.1.5 Static linking</a></H3> <p> An alternative approach to dynamic linking is to rebuild the @@ -334,7 +334,7 @@ finding the Ruby source, adding an entry to the <tt>ext/Setup</tt> file, adding your directory to the list of extensions in the file, and finally rebuilding Ruby. </p> -<H3><a name="Ruby_nn8"></a>38.1.6 Compilation of C++ extensions</H3> +<H3><a name="Ruby_nn8">38.1.6 Compilation of C++ extensions</a></H3> <p> On most machines, C++ extension modules should be linked @@ -366,7 +366,7 @@ $libs = append_library($libs, "supc++") create_makefile('example')</pre> </div> -<H2><a name="Ruby_nn9"></a>38.2 Building Ruby Extensions under Windows 95/NT</H2> +<H2><a name="Ruby_nn9">38.2 Building Ruby Extensions under Windows 95/NT</a></H2> <p> Building a SWIG extension to Ruby under Windows 95/NT is @@ -391,7 +391,7 @@ order to build extensions, you may need to download the source distribution to the Ruby package, as you will need the Ruby header files. </p> -<H3><a name="Ruby_nn10"></a>38.2.1 Running SWIG from Developer Studio</H3> +<H3><a name="Ruby_nn10">38.2.1 Running SWIG from Developer Studio</a></H3> <p> If you are developing your application within Microsoft @@ -455,13 +455,13 @@ Foo = 3.0 </pre> </div> -<H2><a name="Ruby_nn11"></a>38.3 The Ruby-to-C/C++ Mapping</H2> +<H2><a name="Ruby_nn11">38.3 The Ruby-to-C/C++ Mapping</a></H2> <p> This section describes the basics of how SWIG maps C or C++ declarations in your SWIG interface files to Ruby constructs. </p> -<H3><a name="Ruby_nn12"></a>38.3.1 Modules</H3> +<H3><a name="Ruby_nn12">38.3.1 Modules</a></H3> <p> The SWIG <tt>%module</tt> directive specifies @@ -533,7 +533,7 @@ option to wrap everything into the global module, take care that the names of your constants, classes and methods don't conflict with any of Ruby's built-in names. </p> -<H3><a name="Ruby_nn13"></a>38.3.2 Functions</H3> +<H3><a name="Ruby_nn13">38.3.2 Functions</a></H3> <p> Global functions are wrapped as Ruby module methods. For @@ -567,7 +567,7 @@ irb(main):002:0> <b>Example.fact(4)</b> 24</pre> </div> -<H3><a name="Ruby_nn14"></a>38.3.3 Variable Linking</H3> +<H3><a name="Ruby_nn14">38.3.3 Variable Linking</a></H3> <p> C/C++ global variables are wrapped as a pair of singleton @@ -629,7 +629,7 @@ directive. For example: </p> effect until it is explicitly disabled using <tt>%mutable</tt>. </p> -<H3><a name="Ruby_nn15"></a>38.3.4 Constants</H3> +<H3><a name="Ruby_nn15">38.3.4 Constants</a></H3> <p> C/C++ constants are wrapped as module constants initialized @@ -657,7 +657,7 @@ irb(main):002:0> <b>Example::PI</b> 3.14159</pre> </div> -<H3><a name="Ruby_nn16"></a>38.3.5 Pointers</H3> +<H3><a name="Ruby_nn16">38.3.5 Pointers</a></H3> <p> "Opaque" pointers to arbitrary C/C++ types (i.e. types that @@ -681,7 +681,7 @@ returns an instance of an internally generated Ruby class: </p> <p> A <tt>NULL</tt> pointer is always represented by the Ruby <tt>nil</tt> object. </p> -<H3><a name="Ruby_nn17"></a>38.3.6 Structures</H3> +<H3><a name="Ruby_nn17">38.3.6 Structures</a></H3> <p> C/C++ structs are wrapped as Ruby classes, with accessor @@ -786,7 +786,7 @@ void Bar_f_set(Bar *b, Foo *val) { }</pre> </div> -<H3><a name="Ruby_nn18"></a>38.3.7 C++ classes</H3> +<H3><a name="Ruby_nn18">38.3.7 C++ classes</a></H3> <p> Like structs, C++ classes are wrapped by creating a new Ruby @@ -841,7 +841,7 @@ Ale 3</pre> </div> -<H3><a name="Ruby_nn19"></a>38.3.8 C++ Inheritance</H3> +<H3><a name="Ruby_nn19">38.3.8 C++ Inheritance</a></H3> <p> The SWIG type-checker is fully aware of C++ inheritance. @@ -994,7 +994,7 @@ inherit from both <tt>Base1</tt> and <tt>Base2</tt> (i.e. they exhibit <a href="http://c2.com/cgi/wiki?DuckTyping">"Duck Typing"</a>). </p> -<H3><a name="Ruby_nn20"></a>38.3.9 C++ Overloaded Functions</H3> +<H3><a name="Ruby_nn20">38.3.9 C++ Overloaded Functions</a></H3> <p> C++ overloaded functions, methods, and constructors are @@ -1084,7 +1084,7 @@ arises--in this case, the first declaration takes precedence. </p> <p>Please refer to the <a href="SWIGPlus.html#SWIGPlus">"SWIG and C++"</a> chapter for more information about overloading. </p> -<H3><a name="Ruby_nn21"></a>38.3.10 C++ Operators</H3> +<H3><a name="Ruby_nn21">38.3.10 C++ Operators</a></H3> <p> For the most part, overloaded operators are handled @@ -1126,7 +1126,7 @@ c = Example.add_complex(a, b)</pre> is discussed in the <a href="#Ruby_operator_overloading">section on operator overloading</a>. </p> -<H3><a name="Ruby_nn22"></a>38.3.11 C++ namespaces</H3> +<H3><a name="Ruby_nn22">38.3.11 C++ namespaces</a></H3> <p> SWIG is aware of C++ namespaces, but namespace names do not @@ -1183,7 +1183,7 @@ and create extension modules for each namespace separately. If your program utilizes thousands of small deeply nested namespaces each with identical symbol names, well, then you get what you deserve. </p> -<H3><a name="Ruby_nn23"></a>38.3.12 C++ templates</H3> +<H3><a name="Ruby_nn23">38.3.12 C++ templates</a></H3> <p> C++ templates don't present a huge problem for SWIG. However, @@ -1225,7 +1225,7 @@ irb(main):004:0> <b>p.second</b> 4</pre> </div> -<H3><a name="Ruby_nn23_1"></a>38.3.13 C++ Standard Template Library (STL)</H3> +<H3><a name="Ruby_nn23_1">38.3.13 C++ Standard Template Library (STL)</a></H3> <p> On a related note, the standard SWIG library contains a @@ -1318,7 +1318,7 @@ puts v shown in these examples. More details can be found in the <a href="SWIGPlus.html#SWIGPlus">SWIG and C++</a> chapter.</p> -<H3><a name="Ruby_C_STL_Functors"></a>38.3.14 C++ STL Functors</H3> +<H3><a name="Ruby_C_STL_Functors">38.3.14 C++ STL Functors</a></H3> <p>Some containers in the STL allow you to modify their default @@ -1379,7 +1379,7 @@ b </pre> </div> -<H3><a name="Ruby_C_Iterators"></a>38.3.15 C++ STL Iterators</H3> +<H3><a name="Ruby_C_Iterators">38.3.15 C++ STL Iterators</a></H3> <p>The STL is well known for the use of iterators. There @@ -1462,10 +1462,10 @@ i <p>If you'd rather have STL classes without any iterators, you should define <tt>-DSWIG_NO_EXPORT_ITERATOR_METHODS</tt> when running swig.</p> -<H3><a name="Ruby_nn24"></a>38.3.16 C++ Smart Pointers</H3> +<H3><a name="Ruby_nn24">38.3.16 C++ Smart Pointers</a></H3> -<H4><a name="Ruby_smart_pointers_shared_ptr"></a>38.3.16.1 The shared_ptr Smart Pointer</H4> +<H4><a name="Ruby_smart_pointers_shared_ptr">38.3.16.1 The shared_ptr Smart Pointer</a></H4> <p> @@ -1476,7 +1476,7 @@ in the <a href="Library.html#Library_std_shared_ptr">shared_ptr smart pointer</a </p> -<H4><a name="Ruby_smart_pointers_generic"></a>38.3.16.2 Generic Smart Pointers</H4> +<H4><a name="Ruby_smart_pointers_generic">38.3.16.2 Generic Smart Pointers</a></H4> <p> In certain C++ programs, it is common to use classes that @@ -1541,7 +1541,7 @@ method. For example: </p> <pre>irb(main):004:0> <b>f = p.__deref__()</b> # Returns underlying Foo *</pre> </div> -<H3><a name="Ruby_nn25"></a>38.3.17 Cross-Language Polymorphism</H3> +<H3><a name="Ruby_nn25">38.3.17 Cross-Language Polymorphism</a></H3> <p> SWIG's Ruby module supports cross-language polymorphism @@ -1550,7 +1550,7 @@ module. Rather than duplicate the information presented in the <a href="Python.h section just notes the differences that you need to be aware of when using this feature with Ruby. </p> -<H4><a name="Ruby_nn26"></a>38.3.17.1 Exception Unrolling</H4> +<H4><a name="Ruby_nn26">38.3.17.1 Exception Unrolling</a></H4> <p> Whenever a C++ director class routes one of its virtual @@ -1573,7 +1573,7 @@ method is "wrapped" using the <tt>rb_rescue2()</tt> function from Ruby's C API. If any Ruby exception is raised, it will be caught here and a C++ exception is raised in its place. </p> -<H2><a name="Ruby_nn27"></a>38.4 Naming</H2> +<H2><a name="Ruby_nn27">38.4 Naming</a></H2> <p>Ruby has several common naming conventions. Constants are @@ -1611,7 +1611,7 @@ generated by SWIG, it is turned off by default in SWIG 1.3.28. However, it is planned to become the default option in future releases.</p> -<H3><a name="Ruby_nn28"></a>38.4.1 Defining Aliases</H3> +<H3><a name="Ruby_nn28">38.4.1 Defining Aliases</a></H3> <p> It's a fairly common practice in the Ruby built-ins and @@ -1681,7 +1681,7 @@ matching rules used for other kinds of features apply (see the chapter on <a href="Customization.html#Customization">"Customization Features"</a>) for more details).</p> -<H3><a name="Ruby_nn29"></a>38.4.2 Predicate Methods</H3> +<H3><a name="Ruby_nn29">38.4.2 Predicate Methods</a></H3> <p> Ruby methods that return a boolean value and end in a @@ -1730,7 +1730,7 @@ using SWIG's "features" mechanism and so the same name matching rules used for other kinds of features apply (see the chapter on <a href="Customization.html#Customization">"Customization Features"</a>) for more details). </p> -<H3><a name="Ruby_nn30"></a>38.4.3 Bang Methods</H3> +<H3><a name="Ruby_nn30">38.4.3 Bang Methods</a></H3> <p> Ruby methods that modify an object in-place and end in an @@ -1762,7 +1762,7 @@ using SWIG's "features" mechanism and so the same name matching rules used for other kinds of features apply (see the chapter on <a href="Customization.html#Customization">"Customization Features"</a>) for more details). </p> -<H3><a name="Ruby_nn31"></a>38.4.4 Getters and Setters</H3> +<H3><a name="Ruby_nn31">38.4.4 Getters and Setters</a></H3> <p> Often times a C++ library will expose properties through @@ -1797,7 +1797,7 @@ irb(main):003:0> <b>puts foo.value</b></pre> %rename("value=") Foo::setValue(int value);</pre> </div> -<H2><a name="Ruby_nn32"></a>38.5 Input and output parameters</H2> +<H2><a name="Ruby_nn32">38.5 Input and output parameters</a></H2> <p> A common problem in some C programs is handling parameters @@ -1936,10 +1936,10 @@ void get_dimensions(Matrix *m, int *rows, int*columns);</pre> <pre>r, c = Example.get_dimensions(m)</pre> </div> -<H2><a name="Ruby_nn33"></a>38.6 Exception handling </H2> +<H2><a name="Ruby_nn33">38.6 Exception handling </a></H2> -<H3><a name="Ruby_nn34"></a>38.6.1 Using the %exception directive </H3> +<H3><a name="Ruby_nn34">38.6.1 Using the %exception directive </a></H3> <p>The SWIG <tt>%exception</tt> directive can be @@ -2048,7 +2048,7 @@ methods and functions named <tt>getitem</tt> and <tt>setitem</tt>. limited to C++ exception handling. See the chapter on <a href="Customization.html#Customization">Customization Features</a> for more examples.</p> -<H3><a name="Ruby_nn34_2"></a>38.6.2 Handling Ruby Blocks </H3> +<H3><a name="Ruby_nn34_2">38.6.2 Handling Ruby Blocks </a></H3> <p>One of the highlights of Ruby and most of its standard library @@ -2115,7 +2115,7 @@ a special in typemap, like:</p> <p>For more information on typemaps, see <a href="#Ruby_nn37">Typemaps</a>.</p> -<H3><a name="Ruby_nn35"></a>38.6.3 Raising exceptions </H3> +<H3><a name="Ruby_nn35">38.6.3 Raising exceptions </a></H3> <p>There are three ways to raise exceptions from C++ code to @@ -2272,7 +2272,7 @@ function. The first argument passed to <tt>rb_raise()</tt> is the exception type. You can raise a custom exception type or one of the built-in Ruby exception types.</p> -<H3><a name="Ruby_nn36"></a>38.6.4 Exception classes </H3> +<H3><a name="Ruby_nn36">38.6.4 Exception classes </a></H3> <p>Starting with SWIG 1.3.28, the Ruby module supports the <tt>%exceptionclass</tt> @@ -2309,7 +2309,7 @@ end </pre> <p>For another example look at swig/Examples/ruby/exception_class. </p> -<H2><a name="Ruby_nn37"></a>38.7 Typemaps</H2> +<H2><a name="Ruby_nn37">38.7 Typemaps</a></H2> <p> This section describes how you can modify SWIG's default @@ -2324,7 +2324,7 @@ a required part of using SWIG---the default wrapping behavior is enough in most cases. Typemaps are only used if you want to change some aspect of the primitive C-Ruby interface.</p> -<H3><a name="Ruby_nn38"></a>38.7.1 What is a typemap?</H3> +<H3><a name="Ruby_nn38">38.7.1 What is a typemap?</a></H3> <p> A typemap is nothing more than a code generation rule that is @@ -2481,7 +2481,7 @@ to be used as follows (notice how the length parameter is omitted): </p> 2</pre> </div> -<H3><a name="Ruby_Typemap_scope"></a>38.7.2 Typemap scope</H3> +<H3><a name="Ruby_Typemap_scope">38.7.2 Typemap scope</a></H3> <p> Once defined, a typemap remains in effect for all of the @@ -2527,7 +2527,7 @@ where the class itself is defined. For example:</p> };</pre> </div> -<H3><a name="Ruby_Copying_a_typemap"></a>38.7.3 Copying a typemap</H3> +<H3><a name="Ruby_Copying_a_typemap">38.7.3 Copying a typemap</a></H3> <p> A typemap is copied by using assignment. For example:</p> @@ -2569,7 +2569,7 @@ rules as for <tt> %apply (char *buf, int len) { (char *buffer, int size) }; // Multiple arguments</pre> </div> -<H3><a name="Ruby_Deleting_a_typemap"></a>38.7.4 Deleting a typemap</H3> +<H3><a name="Ruby_Deleting_a_typemap">38.7.4 Deleting a typemap</a></H3> <p> A typemap can be deleted by simply defining no code. For @@ -2594,7 +2594,7 @@ defined by typemaps, clearing a fundamental type like <tt>int</tt> will make that type unusable unless you also define a new set of typemaps immediately after the clear operation.</p> -<H3><a name="Ruby_Placement_of_typemaps"></a>38.7.5 Placement of typemaps</H3> +<H3><a name="Ruby_Placement_of_typemaps">38.7.5 Placement of typemaps</a></H3> <p> Typemap declarations can be declared in the global scope, @@ -2665,13 +2665,13 @@ In this example, this is done using the class declaration <tt>class string</tt> .</p> -<H3><a name="Ruby_nn39"></a>38.7.6 Ruby typemaps</H3> +<H3><a name="Ruby_nn39">38.7.6 Ruby typemaps</a></H3> <p>The following list details all of the typemap methods that can be used by the Ruby module: </p> -<H4><a name="Ruby_in_typemap"></a>38.7.6.1 "in" typemap</H4> +<H4><a name="Ruby_in_typemap">38.7.6.1 "in" typemap</a></H4> <p>Converts Ruby objects to input @@ -2738,7 +2738,7 @@ arguments to be specified. For example:</p> <p> At this time, only zero or one arguments may be converted.</p> -<H4><a name="Ruby_typecheck_typemap"></a>38.7.6.2 "typecheck" typemap</H4> +<H4><a name="Ruby_typecheck_typemap">38.7.6.2 "typecheck" typemap</a></H4> <p> The "typecheck" typemap is used to support overloaded @@ -2760,7 +2760,7 @@ program uses overloaded methods, you should also define a collection of "typecheck" typemaps. More details about this follow in a later section on "Typemaps and Overloading."</p> -<H4><a name="Ruby_out_typemap"></a>38.7.6.3 "out" typemap</H4> +<H4><a name="Ruby_out_typemap">38.7.6.3 "out" typemap</a></H4> <p>Converts return value of a C function @@ -2811,7 +2811,7 @@ version of the C datatype matched by the typemap.</td> </table> </div> -<H4><a name="Ruby_arginit_typemap"></a>38.7.6.4 "arginit" typemap</H4> +<H4><a name="Ruby_arginit_typemap">38.7.6.4 "arginit" typemap</a></H4> <p> The "arginit" typemap is used to set the initial value of a @@ -2826,7 +2826,7 @@ applications. For example:</p> }</pre> </div> -<H4><a name="Ruby_default_typemap"></a>38.7.6.5 "default" typemap</H4> +<H4><a name="Ruby_default_typemap">38.7.6.5 "default" typemap</a></H4> <p> The "default" typemap is used to turn an argument into a @@ -2851,7 +2851,7 @@ arguments that follow must have default values. See the <a href="SWIG.html#SWIG_ Default/optional arguments</a> section for further information on default argument wrapping.</p> -<H4><a name="Ruby_check_typemap"></a>38.7.6.6 "check" typemap</H4> +<H4><a name="Ruby_check_typemap">38.7.6.6 "check" typemap</a></H4> <p> The "check" typemap is used to supply value checking code @@ -2866,7 +2866,7 @@ arguments have been converted. For example:</p> }</pre> </div> -<H4><a name="Ruby_argout_typemap_"></a>38.7.6.7 "argout" typemap</H4> +<H4><a name="Ruby_argout_typemap_">38.7.6.7 "argout" typemap</a></H4> <p> The "argout" typemap is used to return values from arguments. @@ -2920,7 +2920,7 @@ some function like SWIG_Ruby_AppendOutput.</p> <p> See the <tt>typemaps.i</tt> library for examples.</p> -<H4><a name="Ruby_freearg_typemap_"></a>38.7.6.8 "freearg" typemap</H4> +<H4><a name="Ruby_freearg_typemap_">38.7.6.8 "freearg" typemap</a></H4> <p> The "freearg" typemap is used to cleanup argument data. It is @@ -2947,7 +2947,7 @@ This code is also placed into a special variable <tt>$cleanup</tt> that may be used in other typemaps whenever a wrapper function needs to abort prematurely.</p> -<H4><a name="Ruby_newfree_typemap"></a>38.7.6.9 "newfree" typemap</H4> +<H4><a name="Ruby_newfree_typemap">38.7.6.9 "newfree" typemap</a></H4> <p> The "newfree" typemap is used in conjunction with the <tt>%newobject</tt> @@ -2971,7 +2971,7 @@ string *foo();</pre> <p> See <a href="Customization.html#Customization_ownership">Object ownership and %newobject</a> for further details.</p> -<H4><a name="Ruby_memberin_typemap"></a>38.7.6.10 "memberin" typemap</H4> +<H4><a name="Ruby_memberin_typemap">38.7.6.10 "memberin" typemap</a></H4> <p> The "memberin" typemap is used to copy data from<em> an @@ -2989,21 +2989,21 @@ example:</p> already provides a default implementation for arrays, strings, and other objects.</p> -<H4><a name="Ruby_varin_typemap"></a>38.7.6.11 "varin" typemap</H4> +<H4><a name="Ruby_varin_typemap">38.7.6.11 "varin" typemap</a></H4> <p> The "varin" typemap is used to convert objects in the target language to C for the purposes of assigning to a C/C++ global variable. This is implementation specific.</p> -<H4><a name="Ruby_varout_typemap_"></a>38.7.6.12 "varout" typemap</H4> +<H4><a name="Ruby_varout_typemap_">38.7.6.12 "varout" typemap</a></H4> <p> The "varout" typemap is used to convert a C/C++ object to an object in the target language when reading a C/C++ global variable. This is implementation specific.</p> -<H4><a name="Ruby_throws_typemap"></a>38.7.6.13 "throws" typemap</H4> +<H4><a name="Ruby_throws_typemap">38.7.6.13 "throws" typemap</a></H4> <p> The "throws" typemap is only used when SWIG parses a C++ @@ -3044,7 +3044,7 @@ specification yet they do throw exceptions, SWIG cannot know how to deal with them. For a neat way to handle these, see the <a href="Customization.html#Customization_exception">Exception handling with %exception</a> section.</p> -<H4><a name="Ruby_directorin_typemap"></a>38.7.6.14 directorin typemap</H4> +<H4><a name="Ruby_directorin_typemap">38.7.6.14 directorin typemap</a></H4> <p>Converts C++ objects in director @@ -3103,7 +3103,7 @@ referring to the class itself.</td> </table> </div> -<H4><a name="Ruby_directorout_typemap"></a>38.7.6.15 directorout typemap</H4> +<H4><a name="Ruby_directorout_typemap">38.7.6.15 directorout typemap</a></H4> <p>Converts Ruby objects in director @@ -3176,7 +3176,7 @@ exception. </p> -<H4><a name="Ruby_directorargout_typemap"></a>38.7.6.16 directorargout typemap</H4> +<H4><a name="Ruby_directorargout_typemap">38.7.6.16 directorargout typemap</a></H4> <p>Output argument processing in director @@ -3234,19 +3234,19 @@ referring to the instance of the class itself</td> </table> </div> -<H4><a name="Ruby_ret_typemap"></a>38.7.6.17 ret typemap</H4> +<H4><a name="Ruby_ret_typemap">38.7.6.17 ret typemap</a></H4> <p>Cleanup of function return values </p> -<H4><a name="Ruby_globalin_typemap"></a>38.7.6.18 globalin typemap</H4> +<H4><a name="Ruby_globalin_typemap">38.7.6.18 globalin typemap</a></H4> <p>Setting of C global variables </p> -<H3><a name="Ruby_nn40"></a>38.7.7 Typemap variables</H3> +<H3><a name="Ruby_nn40">38.7.7 Typemap variables</a></H3> <p> @@ -3296,7 +3296,7 @@ so that their values can be properly assigned. </div> <div class="indent">The Ruby name of the wrapper function being created. </div> -<H3><a name="Ruby_nn41"></a>38.7.8 Useful Functions</H3> +<H3><a name="Ruby_nn41">38.7.8 Useful Functions</a></H3> <p> When you write a typemap, you usually have to work directly @@ -3311,7 +3311,7 @@ stick to the swig functions instead of the native Ruby functions. That should help you avoid having to rewrite a lot of typemaps across multiple languages.</p> -<H4><a name="Ruby_nn42"></a>38.7.8.1 C Datatypes to Ruby Objects</H4> +<H4><a name="Ruby_nn42">38.7.8.1 C Datatypes to Ruby Objects</a></H4> <div class="diagram"> @@ -3353,7 +3353,7 @@ SWIG_From_float(float)</td> </table> </div> -<H4><a name="Ruby_nn43"></a>38.7.8.2 Ruby Objects to C Datatypes</H4> +<H4><a name="Ruby_nn43">38.7.8.2 Ruby Objects to C Datatypes</a></H4> <p>Here, while the Ruby versions return the value directly, the SWIG @@ -3421,7 +3421,7 @@ versions do not, but return a status value to indicate success (<tt>SWIG_OK</tt> </table> </div> -<H4><a name="Ruby_nn44"></a>38.7.8.3 Macros for VALUE</H4> +<H4><a name="Ruby_nn44">38.7.8.3 Macros for VALUE</a></H4> <p> <tt>RSTRING_LEN(str)</tt> </p> @@ -3444,7 +3444,7 @@ versions do not, but return a status value to indicate success (<tt>SWIG_OK</tt> <div class="indent">pointer to array storage</div> -<H4><a name="Ruby_nn45"></a>38.7.8.4 Exceptions</H4> +<H4><a name="Ruby_nn45">38.7.8.4 Exceptions</a></H4> <p> <tt>void rb_raise(VALUE exception, const char *fmt, @@ -3523,7 +3523,7 @@ message to standard error if Ruby was invoked with the <tt>-w</tt> flag. The given format string <i>fmt</i> and remaining arguments are interpreted as with <tt>printf()</tt>. </div> -<H4><a name="Ruby_nn46"></a>38.7.8.5 Iterators</H4> +<H4><a name="Ruby_nn46">38.7.8.5 Iterators</a></H4> <p> <tt>void rb_iter_break()</tt> </p> @@ -3569,14 +3569,14 @@ VALUE), VALUE value)</tt></p> <div class="indent"> Equivalent to Ruby's <tt>throw</tt>. </div> -<H3><a name="Ruby_nn47"></a>38.7.9 Typemap Examples</H3> +<H3><a name="Ruby_nn47">38.7.9 Typemap Examples</a></H3> <p> This section includes a few examples of typemaps. For more examples, you might look at the examples in the <tt>Example/ruby</tt> directory. </p> -<H3><a name="Ruby_nn48"></a>38.7.10 Converting a Ruby array to a char **</H3> +<H3><a name="Ruby_nn48">38.7.10 Converting a Ruby array to a char **</a></H3> <p> A common problem in many C programs is the processing of @@ -3641,7 +3641,7 @@ array. Since dynamic memory allocation is used to allocate memory for the array, the "freearg" typemap is used to later release this memory after the execution of the C function. </p> -<H3><a name="Ruby_nn49"></a>38.7.11 Collecting arguments in a hash</H3> +<H3><a name="Ruby_nn49">38.7.11 Collecting arguments in a hash</a></H3> <p> Ruby's solution to the "keyword arguments" capability of some @@ -3855,7 +3855,7 @@ memory leak. Fortunately, this typemap is a lot easier to write: </p> program that uses the extension, can be found in the <tt>Examples/ruby/hashargs</tt> directory of the SWIG distribution. </p> -<H3><a name="Ruby_nn50"></a>38.7.12 Pointer handling</H3> +<H3><a name="Ruby_nn50">38.7.12 Pointer handling</a></H3> <p> Occasionally, it might be necessary to convert pointer values @@ -3914,7 +3914,7 @@ For example: </p> }</pre> </div> -<H4><a name="Ruby_nn51"></a>38.7.12.1 Ruby Datatype Wrapping</H4> +<H4><a name="Ruby_nn51">38.7.12.1 Ruby Datatype Wrapping</a></H4> <p> <tt>VALUE Data_Wrap_Struct(VALUE class, void @@ -3941,7 +3941,7 @@ as above. </div> type <i>c-type</i> from the data object <i>obj</i> and assigns that pointer to <i>ptr</i>. </div> -<H3><a name="Ruby_nn52"></a>38.7.13 Example: STL Vector to Ruby Array</H3> +<H3><a name="Ruby_nn52">38.7.13 Example: STL Vector to Ruby Array</a></H3> <p>Another use for macros and type maps is to create a Ruby array @@ -4033,7 +4033,7 @@ STL with ruby, you are advised to use the standard swig STL library, which does much more than this. Refer to the section called the<a href="#Ruby_nn23_1"> C++ Standard Template Library</a>. -<H2><a name="Ruby_nn65"></a>38.8 Docstring Features</H2> +<H2><a name="Ruby_nn65">38.8 Docstring Features</a></H2> <p> @@ -4067,7 +4067,7 @@ generate ri documentation from a c wrap file, you could do:</p> $ rdoc -r file_wrap.c </pre></div> -<H3><a name="Ruby_nn66"></a>38.8.1 Module docstring</H3> +<H3><a name="Ruby_nn66">38.8.1 Module docstring</a></H3> <p> @@ -4097,7 +4097,7 @@ layout of controls on a panel, etc. to be loaded from an XML file." %module(docstring=DOCSTRING) xrc</pre> </div> -<H3><a name="Ruby_nn67"></a>38.8.2 %feature("autodoc")</H3> +<H3><a name="Ruby_nn67">38.8.2 %feature("autodoc")</a></H3> <p>Since SWIG does know everything about the function it wraps, @@ -4118,7 +4118,7 @@ several options for autodoc controlled by the value given to the feature, described below. </p> -<H4><a name="Ruby_nn68"></a>38.8.2.1 %feature("autodoc", "0")</H4> +<H4><a name="Ruby_nn68">38.8.2.1 %feature("autodoc", "0")</a></H4> <p> @@ -4142,7 +4142,7 @@ Then Ruby code like this will be generated: ...</pre> </div> -<H4><a name="Ruby_autodoc1"></a>38.8.2.2 %feature("autodoc", "1")</H4> +<H4><a name="Ruby_autodoc1">38.8.2.2 %feature("autodoc", "1")</a></H4> <p> @@ -4162,7 +4162,7 @@ this: ...</pre> </div> -<H4><a name="Ruby_autodoc2"></a>38.8.2.3 %feature("autodoc", "2")</H4> +<H4><a name="Ruby_autodoc2">38.8.2.3 %feature("autodoc", "2")</a></H4> <p> @@ -4174,7 +4174,7 @@ parameter types with the "2" option will result in Ruby code like this: </p> -<H4><a name="Ruby_feature_autodoc3"></a>38.8.2.4 %feature("autodoc", "3")</H4> +<H4><a name="Ruby_feature_autodoc3">38.8.2.4 %feature("autodoc", "3")</a></H4> <p> @@ -4195,7 +4195,7 @@ Parameters: bar - Bar</pre> </div> -<H4><a name="Ruby_nn70"></a>38.8.2.5 %feature("autodoc", "docstring")</H4> +<H4><a name="Ruby_nn70">38.8.2.5 %feature("autodoc", "docstring")</a></H4> <p> @@ -4211,7 +4211,7 @@ generated string. For example: void GetPosition(int* OUTPUT, int* OUTPUT);</pre> </div> -<H3><a name="Ruby_nn71"></a>38.8.3 %feature("docstring")</H3> +<H3><a name="Ruby_nn71">38.8.3 %feature("docstring")</a></H3> <p> @@ -4222,10 +4222,10 @@ docstring associated with classes, function or methods are output. If an item already has an autodoc string then it is combined with the docstring and they are output together. </p> -<H2><a name="Ruby_nn53"></a>38.9 Advanced Topics</H2> +<H2><a name="Ruby_nn53">38.9 Advanced Topics</a></H2> -<H3><a name="Ruby_operator_overloading"></a>38.9.1 Operator overloading</H3> +<H3><a name="Ruby_operator_overloading">38.9.1 Operator overloading</a></H3> <p> SWIG allows operator overloading with, by using the <tt>%extend</tt> @@ -4406,7 +4406,7 @@ separate method for handling <i>inequality</i> since Ruby parses the expression <i>a != b</i> as <i>!(a == b)</i>. </p> -<H3><a name="Ruby_nn55"></a>38.9.2 Creating Multi-Module Packages</H3> +<H3><a name="Ruby_nn55">38.9.2 Creating Multi-Module Packages</a></H3> <p> The chapter on <a href="Modules.html#Modules">Working @@ -4532,7 +4532,7 @@ irb(main):005:0> <b>c.getX()</b> 5.0</pre> </div> -<H3><a name="Ruby_nn56"></a>38.9.3 Specifying Mixin Modules</H3> +<H3><a name="Ruby_nn56">38.9.3 Specifying Mixin Modules</a></H3> <p> The Ruby language doesn't support multiple inheritance, but @@ -4599,7 +4599,7 @@ matching rules used for other kinds of features apply (see the chapter on <a href="Customization.html#Customization">"Customization Features"</a>) for more details). </p> -<H2><a name="Ruby_nn57"></a>38.10 Memory Management</H2> +<H2><a name="Ruby_nn57">38.10 Memory Management</a></H2> <p>One of the most common issues in generating SWIG bindings for @@ -4622,7 +4622,7 @@ to C++ (or vice versa) depending on what function or methods are invoked. Clearly, developing a SWIG wrapper requires a thorough understanding of how the underlying library manages memory.</p> -<H3><a name="Ruby_nn58"></a>38.10.1 Mark and Sweep Garbage Collector </H3> +<H3><a name="Ruby_nn58">38.10.1 Mark and Sweep Garbage Collector </a></H3> <p>Ruby uses a mark and sweep garbage collector. When the garbage @@ -4654,7 +4654,7 @@ any memory has been allocated in creating the underlying C struct or C++ struct, then a "free" function must be defined that deallocates this memory. </p> -<H3><a name="Ruby_nn59"></a>38.10.2 Object Ownership</H3> +<H3><a name="Ruby_nn59">38.10.2 Object Ownership</a></H3> <p>As described above, memory management depends on clearly @@ -4799,7 +4799,7 @@ public: <p> This code can be seen in swig/examples/ruby/tracking.</p> -<H3><a name="Ruby_nn60"></a>38.10.3 Object Tracking</H3> +<H3><a name="Ruby_nn60">38.10.3 Object Tracking</a></H3> <p>The remaining parts of this section will use the class library @@ -5025,7 +5025,7 @@ However, if you implement your own free functions (see below) you may also have to call the <tt>SWIG_RubyRemoveTracking</tt> and <tt>RubyUnlinkObjects</tt> methods.</p> -<H3><a name="Ruby_nn61"></a>38.10.4 Mark Functions</H3> +<H3><a name="Ruby_nn61">38.10.4 Mark Functions</a></H3> <p>With a bit more testing, we see that our class library still @@ -5154,7 +5154,7 @@ irb(main):016:0></pre> <p>This code can be seen in swig/examples/ruby/mark_function.</p> -<H3><a name="Ruby_nn62"></a>38.10.5 Free Functions</H3> +<H3><a name="Ruby_nn62">38.10.5 Free Functions</a></H3> <p>By default, SWIG creates a "free" function that is called when @@ -5323,7 +5323,7 @@ been freed, and thus raises a runtime exception.</p> <p>This code can be seen in swig/examples/ruby/free_function.</p> -<H3><a name="Ruby_nn63"></a>38.10.6 Embedded Ruby and the C++ Stack</H3> +<H3><a name="Ruby_nn63">38.10.6 Embedded Ruby and the C++ Stack</a></H3> <p>As has been said, the Ruby GC runs and marks objects before diff --git a/Doc/Manual/SWIG.html b/Doc/Manual/SWIG.html index 774e00b23..c31d8255f 100644 --- a/Doc/Manual/SWIG.html +++ b/Doc/Manual/SWIG.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="SWIG"></a>5 SWIG Basics</H1> +<H1><a name="SWIG">5 SWIG Basics</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -94,7 +94,7 @@ Specific details about each target language are described in later chapters. </p> -<H2><a name="SWIG_nn2"></a>5.1 Running SWIG</H2> +<H2><a name="SWIG_nn2">5.1 Running SWIG</a></H2> <p> @@ -156,7 +156,7 @@ can be obtained by typing <tt>swig -help</tt> or <tt>swig </pre></div> -<H3><a name="SWIG_nn3"></a>5.1.1 Input format</H3> +<H3><a name="SWIG_nn3">5.1.1 Input format</a></H3> <p> @@ -203,7 +203,7 @@ semantics in SWIG is analogous to that of the declarations section used in input files to parser generation tools such as yacc or bison. </p> -<H3><a name="SWIG_output"></a>5.1.2 SWIG Output</H3> +<H3><a name="SWIG_output">5.1.2 SWIG Output</a></H3> <p> @@ -263,7 +263,7 @@ as the output directory for the language files is the same directory as the generated C/C++ file if not overridden with <tt>-outdir</tt>. </p> -<H3><a name="SWIG_nn5"></a>5.1.3 Comments</H3> +<H3><a name="SWIG_nn5">5.1.3 Comments</a></H3> <p> @@ -273,7 +273,7 @@ documentation files. However, this feature is currently under repair and will reappear in a later SWIG release. </p> -<H3><a name="SWIG_nn6"></a>5.1.4 C Preprocessor</H3> +<H3><a name="SWIG_nn6">5.1.4 C Preprocessor</a></H3> <p> @@ -297,7 +297,7 @@ make it more powerful than the normal C preprocessor. These extensions are described in the "<a href="Preprocessor.html#Preprocessor">Preprocessor</a>" chapter. </p> -<H3><a name="SWIG_nn7"></a>5.1.5 SWIG Directives</H3> +<H3><a name="SWIG_nn7">5.1.5 SWIG Directives</a></H3> <p> @@ -328,7 +328,7 @@ included in C header files using conditional compilation like this: it is parsing an input file. </p> -<H3><a name="SWIG_nn8"></a>5.1.6 Parser Limitations</H3> +<H3><a name="SWIG_nn8">5.1.6 Parser Limitations</a></H3> <p> @@ -426,7 +426,7 @@ does not utilize a separate <em>typedef-name</em> terminal symbol as described on p. 234 of K&R). </p> -<H2><a name="SWIG_nn9"></a>5.2 Wrapping Simple C Declarations</H2> +<H2><a name="SWIG_nn9">5.2 Wrapping Simple C Declarations</a></H2> <p> @@ -489,7 +489,7 @@ environments, and semantics, it is not always possible to do so. The next few sections describe various aspects of this mapping. </p> -<H3><a name="SWIG_nn10"></a>5.2.1 Basic Type Handling</H3> +<H3><a name="SWIG_nn10">5.2.1 Basic Type Handling</a></H3> <p> @@ -614,7 +614,7 @@ will use the same internal representation (e.g., UCS-2 vs. UCS-4). You may need to write some special conversion functions. </p> -<H3><a name="SWIG_nn11"></a>5.2.2 Global Variables</H3> +<H3><a name="SWIG_nn11">5.2.2 Global Variables</a></H3> <p> @@ -669,7 +669,7 @@ Earlier versions of SWIG incorrectly handled <tt>const</tt> and created constants instead. </p> -<H3><a name="SWIG_nn12"></a>5.2.3 Constants</H3> +<H3><a name="SWIG_nn12">5.2.3 Constants</a></H3> <p> @@ -758,7 +758,7 @@ is only used when you want to add constants to the scripting language interface that are not defined in the original header file. </p> -<H3><a name="SWIG_nn13"></a>5.2.4 A brief word about <tt>const</tt></H3> +<H3><a name="SWIG_nn13">5.2.4 A brief word about <tt>const</tt></a></H3> <p> @@ -860,7 +860,7 @@ const int spam = 42; </pre> </div> -<H3><a name="SWIG_nn14"></a>5.2.5 A cautionary tale of <tt>char *</tt></H3> +<H3><a name="SWIG_nn14">5.2.5 A cautionary tale of <tt>char *</tt></a></H3> <p> @@ -899,7 +899,7 @@ input values. However, it must be noted that you could change the behavior of using <a href="Typemaps.html#Typemaps">typemaps</a>. </p> -<H2><a name="SWIG_nn15"></a>5.3 Pointers and complex objects</H2> +<H2><a name="SWIG_nn15">5.3 Pointers and complex objects</a></H2> <p> @@ -907,7 +907,7 @@ Most C programs manipulate arrays, structures, and other types of objects. This discusses the handling of these datatypes. </p> -<H3><a name="SWIG_nn16"></a>5.3.1 Simple pointers</H3> +<H3><a name="SWIG_nn16">5.3.1 Simple pointers</a></H3> <p> @@ -973,7 +973,7 @@ simplified and less prone to error. </li> </ul> -<H3><a name="SWIG_nn17"></a>5.3.2 Run time pointer type checking</H3> +<H3><a name="SWIG_nn17">5.3.2 Run time pointer type checking</a></H3> <p> @@ -995,7 +995,7 @@ as sentinel values or to denote a missing/empty value. Therefore, SWIG leaves NULL pointer checking up to the application. </p> -<H3><a name="SWIG_nn18"></a>5.3.3 Derived types, structs, and classes</H3> +<H3><a name="SWIG_nn18">5.3.3 Derived types, structs, and classes</a></H3> <p> @@ -1052,7 +1052,7 @@ In this case <tt>f1</tt>, <tt>f2</tt>, and <tt>buffer</tt> are all opaque objects containing C pointers. It doesn't matter what value they contain--our program works just fine without this knowledge.</p> -<H3><a name="SWIG_nn19"></a>5.3.4 Undefined datatypes</H3> +<H3><a name="SWIG_nn19">5.3.4 Undefined datatypes</a></H3> <p> @@ -1112,7 +1112,7 @@ The only way to fix this problem is to make sure you properly declare type names <!-- We might want to add an error reporting flag to swig --> -<H3><a name="SWIG_nn20"></a>5.3.5 Typedef</H3> +<H3><a name="SWIG_nn20">5.3.5 Typedef</a></H3> <p> @@ -1201,7 +1201,7 @@ The corresponding wrapper function will accept arguments of type <tt>unsigned int *</tt> or <tt>size_t *</tt>. </p> -<H2><a name="SWIG_nn21"></a>5.4 Other Practicalities</H2> +<H2><a name="SWIG_nn21">5.4 Other Practicalities</a></H2> <p> @@ -1211,7 +1211,7 @@ more difficult to map to a scripting language interface. This section describes some of these issues. </p> -<H3><a name="SWIG_nn22"></a>5.4.1 Passing structures by value</H3> +<H3><a name="SWIG_nn22">5.4.1 Passing structures by value</a></H3> <p> @@ -1242,7 +1242,7 @@ to Vectors instead of Vectors. For the most part, this transformation is transparent so you might not notice. </p> -<H3><a name="SWIG_nn23"></a>5.4.2 Return by value</H3> +<H3><a name="SWIG_nn23">5.4.2 Return by value</a></H3> <p> @@ -1297,7 +1297,7 @@ don't work correctly if <tt>Vector</tt> doesn't define a default constructor. The section on SWIG and C++ has more information about this case. </p> -<H3><a name="SWIG_nn24"></a>5.4.3 Linking to structure variables</H3> +<H3><a name="SWIG_nn24">5.4.3 Linking to structure variables</a></H3> <p> @@ -1329,7 +1329,7 @@ C++ classes must supply a properly defined copy constructor in order for assignment to work correctly. </p> -<H3><a name="SWIG_nn25"></a>5.4.4 Linking to <tt>char *</tt></H3> +<H3><a name="SWIG_nn25">5.4.4 Linking to <tt>char *</tt></a></H3> <p> @@ -1458,7 +1458,7 @@ value is not released. -<H3><a name="SWIG_nn26"></a>5.4.5 Arrays</H3> +<H3><a name="SWIG_nn26">5.4.5 Arrays</a></H3> <p> @@ -1594,7 +1594,7 @@ void pathname_set(char *value) { In the target language, the value can be set like a normal variable. </p> -<H3><a name="SWIG_readonly_variables"></a>5.4.6 Creating read-only variables</H3> +<H3><a name="SWIG_readonly_variables">5.4.6 Creating read-only variables</a></H3> <p> @@ -1668,10 +1668,10 @@ generate a warning message. Simply change the directives to <tt>%immutable;</t <tt>%mutable;</tt> to silence the warning. Don't forget the extra semicolon! </p> -<H3><a name="SWIG_rename_ignore"></a>5.4.7 Renaming and ignoring declarations</H3> +<H3><a name="SWIG_rename_ignore">5.4.7 Renaming and ignoring declarations</a></H3> -<H4><a name="SWIG_nn29"></a>5.4.7.1 Simple renaming of specific identifiers</H4> +<H4><a name="SWIG_nn29">5.4.7.1 Simple renaming of specific identifiers</a></H4> <p> @@ -1769,7 +1769,7 @@ This directive is still supported, but it is deprecated and should probably be a directive is more powerful and better supports wrapping of raw header file information. </p> -<H4><a name="SWIG_advanced_renaming"></a>5.4.7.2 Advanced renaming support</H4> +<H4><a name="SWIG_advanced_renaming">5.4.7.2 Advanced renaming support</a></H4> <p> @@ -1971,7 +1971,7 @@ are exactly equivalent and <tt>%rename</tt> can be used to selectively ignore multiple declarations using the previously described matching possibilities. </p> -<H4><a name="SWIG_limiting_renaming"></a>5.4.7.3 Limiting global renaming rules</H4> +<H4><a name="SWIG_limiting_renaming">5.4.7.3 Limiting global renaming rules</a></H4> <p> @@ -2069,7 +2069,7 @@ wrap C++ overloaded functions and methods or C++ methods which use default argum </p> -<H4><a name="SWIG_chosen_unignore"></a>5.4.7.4 Ignoring everything then wrapping a few selected symbols</H4> +<H4><a name="SWIG_chosen_unignore">5.4.7.4 Ignoring everything then wrapping a few selected symbols</a></H4> <p> @@ -2111,7 +2111,7 @@ members of the class, so when the chosen class is unignored, all of its methods </div> -<H3><a name="SWIG_default_args"></a>5.4.8 Default/optional arguments</H3> +<H3><a name="SWIG_default_args">5.4.8 Default/optional arguments</a></H3> <p> @@ -2148,7 +2148,7 @@ Please refer to the section on <a href="SWIGPlus.html#SWIGPlus_default_args">def in the C++ chapter for further details. </p> -<H3><a name="SWIG_nn30"></a>5.4.9 Pointers to functions and callbacks</H3> +<H3><a name="SWIG_nn30">5.4.9 Pointers to functions and callbacks</a></H3> <p> @@ -2301,7 +2301,7 @@ See the <a href="Typemaps.html#Typemaps">Typemaps chapter</a> for more about typ and individual target language chapters for more on callbacks and the 'director' feature. </p> -<H2><a name="SWIG_nn31"></a>5.5 Structures and unions</H2> +<H2><a name="SWIG_nn31">5.5 Structures and unions</a></H2> <p> @@ -2383,7 +2383,7 @@ delete_Vector(v) However, most of SWIG's language modules also provide a high-level interface that is more convenient. Keep reading. </p> -<H3><a name="SWIG_nn32"></a>5.5.1 Typedef and structures</H3> +<H3><a name="SWIG_nn32">5.5.1 Typedef and structures</a></H3> <p> @@ -2429,7 +2429,7 @@ vector_struct</tt>, SWIG knows that this is the same as <tt>Vector</tt> and it generates the appropriate type-checking code. </p> -<H3><a name="SWIG_nn33"></a>5.5.2 Character strings and structures</H3> +<H3><a name="SWIG_nn33">5.5.2 Character strings and structures</a></H3> <p> @@ -2476,7 +2476,7 @@ Note: If the <tt>-c++</tt> option is used, <tt>new</tt> and <tt>delete</tt> are perform memory allocation. </p> -<H3><a name="SWIG_nn34"></a>5.5.3 Array members</H3> +<H3><a name="SWIG_nn34">5.5.3 Array members</a></H3> <p> @@ -2498,7 +2498,7 @@ discussed in a later chapter. In many cases, the warning message is harmless. </p> -<H3><a name="SWIG_structure_data_members"></a>5.5.4 Structure data members</H3> +<H3><a name="SWIG_structure_data_members">5.5.4 Structure data members</a></H3> <p> @@ -2604,7 +2604,7 @@ class, or union. This is unlikely to break existing code. However, if you need datatype is really a struct, simply use a forward struct declaration such as <tt>"struct Foo;"</tt>. </p> -<H3><a name="SWIG_nn36"></a>5.5.5 C constructors and destructors</H3> +<H3><a name="SWIG_nn36">5.5.5 C constructors and destructors</a></H3> <p> @@ -2693,7 +2693,7 @@ the target languages, and it is highly recommended you don't use them. </p> -<H3><a name="SWIG_adding_member_functions"></a>5.5.6 Adding member functions to C structures</H3> +<H3><a name="SWIG_adding_member_functions">5.5.6 Adding member functions to C structures</a></H3> <p> @@ -2966,7 +2966,7 @@ be used to extend a structure with more than just methods, a more suitable directive name has been chosen. </p> -<H3><a name="SWIG_nested_structs"></a>5.5.7 Nested structures</H3> +<H3><a name="SWIG_nested_structs">5.5.7 Nested structures</a></H3> <p> @@ -3050,7 +3050,7 @@ Finally, note that nesting is handled differently in C++ mode, see <a href="SWIGPlus.html#SWIGPlus_nested_classes">Nested classes</a>. </p> -<H3><a name="SWIG_nn39"></a>5.5.8 Other things to note about structure wrapping</H3> +<H3><a name="SWIG_nn39">5.5.8 Other things to note about structure wrapping</a></H3> <p> @@ -3112,7 +3112,7 @@ interface described here, most of SWIG's language modules use it in some way or another. </p> -<H2><a name="SWIG_nn40"></a>5.6 Code Insertion</H2> +<H2><a name="SWIG_nn40">5.6 Code Insertion</a></H2> <p> @@ -3122,7 +3122,7 @@ additional C code to perform initialization or other operations. There are four common ways to insert code, but it's useful to know how the output of SWIG is structured first.</p> -<H3><a name="SWIG_nn41"></a>5.6.1 The output of SWIG</H3> +<H3><a name="SWIG_nn41">5.6.1 The output of SWIG</a></H3> <p> @@ -3158,7 +3158,7 @@ the module upon loading. </li> </ul> -<H3><a name="SWIG_nn42"></a>5.6.2 Code insertion blocks</H3> +<H3><a name="SWIG_nn42">5.6.2 Code insertion blocks</a></H3> <p> @@ -3236,7 +3236,7 @@ static Vector *new_Vector() { Vector *new_Vector(); </pre></div> -<H3><a name="SWIG_nn43"></a>5.6.3 Inlined code blocks</H3> +<H3><a name="SWIG_nn43">5.6.3 Inlined code blocks</a></H3> <p> @@ -3263,7 +3263,7 @@ declaration. Since the code inside an <tt>%inline %{ ... %}</tt> block is given to both the C compiler and SWIG, it is illegal to include any SWIG directives inside a <tt>%{ ... %}</tt> block.</p> -<H3><a name="SWIG_nn44"></a>5.6.4 Initialization blocks</H3> +<H3><a name="SWIG_nn44">5.6.4 Initialization blocks</a></H3> <p> @@ -3278,7 +3278,7 @@ initialization on module loading, you could write this: %} </pre></div> -<H2><a name="SWIG_nn45"></a>5.7 An Interface Building Strategy</H2> +<H2><a name="SWIG_nn45">5.7 An Interface Building Strategy</a></H2> <p> @@ -3286,7 +3286,7 @@ This section describes the general approach for building interfaces with SWIG. The specifics related to a particular scripting language are found in later chapters.</p> -<H3><a name="SWIG_nn46"></a>5.7.1 Preparing a C program for SWIG</H3> +<H3><a name="SWIG_nn46">5.7.1 Preparing a C program for SWIG</a></H3> <p> @@ -3340,7 +3340,7 @@ to the <a href="http://www.swig.org/mail.html">swig-devel mailing list</a> or to <a href="http://www.swig.org/bugs.html">SWIG bug tracker</a>. </p> -<H3><a name="SWIG_nn47"></a>5.7.2 The SWIG interface file</H3> +<H3><a name="SWIG_nn47">5.7.2 The SWIG interface file</a></H3> <p> @@ -3393,7 +3393,7 @@ The main advantage of this approach is minimal maintenance of an interface file In more complex projects, an interface file containing numerous <tt>%include</tt> and <tt>#include</tt> statements like this is one of the most common approaches to interface file design due to lower maintenance overhead. </p> -<H3><a name="SWIG_nn48"></a>5.7.3 Why use separate interface files?</H3> +<H3><a name="SWIG_nn48">5.7.3 Why use separate interface files?</a></H3> <p> @@ -3422,7 +3422,7 @@ and immediately see what is available without having to dig it out of header files. </ul> -<H3><a name="SWIG_nn49"></a>5.7.4 Getting the right header files</H3> +<H3><a name="SWIG_nn49">5.7.4 Getting the right header files</a></H3> <p> @@ -3442,7 +3442,7 @@ include certain header files by using a <tt>%{,%}</tt> block like this: ... </pre></div> -<H3><a name="SWIG_nn50"></a>5.7.5 What to do with main()</H3> +<H3><a name="SWIG_nn50">5.7.5 What to do with main()</a></H3> <p> diff --git a/Doc/Manual/SWIGPlus.html b/Doc/Manual/SWIGPlus.html index d138073d9..1127a8ee8 100644 --- a/Doc/Manual/SWIGPlus.html +++ b/Doc/Manual/SWIGPlus.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="SWIGPlus"></a>6 SWIG and C++</H1> +<H1><a name="SWIGPlus">6 SWIG and C++</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -75,7 +75,7 @@ how SWIG wraps ANSI C. Support for C++ builds upon ANSI C wrapping and that material will be useful in understanding this chapter. </p> -<H2><a name="SWIGPlus_nn2"></a>6.1 Comments on C++ Wrapping</H2> +<H2><a name="SWIGPlus_nn2">6.1 Comments on C++ Wrapping</a></H2> <p> @@ -117,7 +117,7 @@ crossing language boundaries and provides many opportunities to shoot yourself in the foot. You will just have to be careful. </p> -<H2><a name="SWIGPlus_nn3"></a>6.2 Approach</H2> +<H2><a name="SWIGPlus_nn3">6.2 Approach</a></H2> <p> @@ -158,7 +158,7 @@ proxy classes. More detailed coverage can be found in the documentation for each target language. </p> -<H2><a name="SWIGPlus_nn4"></a>6.3 Supported C++ features</H2> +<H2><a name="SWIGPlus_nn4">6.3 Supported C++ features</a></H2> <p> @@ -197,7 +197,7 @@ in future releases. However, we make no promises. Also, submitting a bug repor good way to get problems fixed (wink). </p> -<H2><a name="SWIGPlus_nn5"></a>6.4 Command line options and compilation</H2> +<H2><a name="SWIGPlus_nn5">6.4 Command line options and compilation</a></H2> <p> @@ -231,7 +231,7 @@ details. The SWIG Wiki also has further details. The <tt>-noproxy</tt> commandline option is recognised by many target languages and will generate just this interface as in earlier versions. -<H2><a name="SWIGPlus_nn38"></a>6.5 Proxy classes</H2> +<H2><a name="SWIGPlus_nn38">6.5 Proxy classes</a></H2> <p> @@ -243,7 +243,7 @@ wrapped by a Python proxy class. Or if you're building a Java module, each C++ class is wrapped by a Java proxy class. </p> -<H3><a name="SWIGPlus_nn39"></a>6.5.1 Construction of proxy classes</H3> +<H3><a name="SWIGPlus_nn39">6.5.1 Construction of proxy classes</a></H3> <p> @@ -325,7 +325,7 @@ Whenever possible, proxies try to take advantage of language features that are s might include operator overloading, exception handling, and other features. </p> -<H3><a name="SWIGPlus_nn40"></a>6.5.2 Resource management in proxies</H3> +<H3><a name="SWIGPlus_nn40">6.5.2 Resource management in proxies</a></H3> <p> @@ -479,7 +479,7 @@ every possible memory management problem. However, proxies do provide a mechani can be used (if necessary) to address some of the more tricky memory management problems. </p> -<H3><a name="SWIGPlus_nn41"></a>6.5.3 Language specific details</H3> +<H3><a name="SWIGPlus_nn41">6.5.3 Language specific details</a></H3> <p> @@ -487,7 +487,7 @@ Language specific details on proxy classes are contained in the chapters describ chapter has merely introduced the topic in a very general way. </p> -<H2><a name="SWIGPlus_nn6"></a>6.6 Simple C++ wrapping</H2> +<H2><a name="SWIGPlus_nn6">6.6 Simple C++ wrapping</a></H2> <p> @@ -520,7 +520,7 @@ To generate wrappers for this class, SWIG first reduces the class to a collectio accessor functions which are then used by the proxy classes. </p> -<H3><a name="SWIGPlus_nn7"></a>6.6.1 Constructors and destructors</H3> +<H3><a name="SWIGPlus_nn7">6.6.1 Constructors and destructors</a></H3> <p> @@ -537,7 +537,7 @@ void delete_List(List *l) { </pre></div> -<H3><a name="SWIGPlus_nn8"></a>6.6.2 Default constructors, copy constructors and implicit destructors</H3> +<H3><a name="SWIGPlus_nn8">6.6.2 Default constructors, copy constructors and implicit destructors</a></H3> <p> @@ -686,7 +686,7 @@ leaks, and so it is strongly recommended to not use them. </p> -<H3><a name="SWIGPlus_nn9"></a>6.6.3 When constructor wrappers aren't created</H3> +<H3><a name="SWIGPlus_nn9">6.6.3 When constructor wrappers aren't created</a></H3> <p> @@ -763,7 +763,7 @@ public: More information about <tt>%feature</tt> can be found in the <a href="Customization.html#Customization">Customization features</a> chapter. </p> -<H3><a name="SWIGPlus_nn10"></a>6.6.4 Copy constructors</H3> +<H3><a name="SWIGPlus_nn10">6.6.4 Copy constructors</a></H3> <p> @@ -865,7 +865,7 @@ constructor is set to <tt>new_CopyFoo()</tt>. This is the same as in older versions. </p> -<H3><a name="SWIGPlus_nn11"></a>6.6.5 Member functions</H3> +<H3><a name="SWIGPlus_nn11">6.6.5 Member functions</a></H3> <p> @@ -891,7 +891,7 @@ wrapper functions. However, the name and calling convention of the low-level procedural wrappers match the accessor function prototype described above. </p> -<H3><a name="SWIGPlus_nn12"></a>6.6.6 Static members</H3> +<H3><a name="SWIGPlus_nn12">6.6.6 Static members</a></H3> <p> @@ -901,7 +901,7 @@ transformations. For example, the static member function in the generated wrapper code. </p> -<H3><a name="SWIGPlus_member_data"></a>6.6.7 Member data</H3> +<H3><a name="SWIGPlus_member_data">6.6.7 Member data</a></H3> <p> @@ -1093,7 +1093,7 @@ a few problems related to structure wrapping and some of SWIG's customization features. </p> -<H2><a name="SWIGPlus_default_args"></a>6.7 Default arguments</H2> +<H2><a name="SWIGPlus_default_args">6.7 Default arguments</a></H2> <p> @@ -1199,7 +1199,7 @@ Keyword arguments are a language feature of some scripting languages, for exampl SWIG is unable to support kwargs when wrapping overloaded methods, so the default approach cannot be used. </p> -<H2><a name="SWIGPlus_nn15"></a>6.8 Protection</H2> +<H2><a name="SWIGPlus_nn15">6.8 Protection</a></H2> <p> @@ -1219,7 +1219,7 @@ until you explicitly give a `<tt>public:</tt>' declaration (This is the same convention used by C++). </p> -<H2><a name="SWIGPlus_nn16"></a>6.9 Enums and constants</H2> +<H2><a name="SWIGPlus_nn16">6.9 Enums and constants</a></H2> <p> @@ -1249,7 +1249,7 @@ Swig_STOUT = Swig::STOUT Members declared as <tt>const</tt> are wrapped as read-only members and do not create constants. </p> -<H2><a name="SWIGPlus_nn17"></a>6.10 Friends</H2> +<H2><a name="SWIGPlus_nn17">6.10 Friends</a></H2> <p> @@ -1310,7 +1310,7 @@ namespace bar { and a wrapper for the method 'blah' will not be generated. </p> -<H2><a name="SWIGPlus_nn18"></a>6.11 References and pointers</H2> +<H2><a name="SWIGPlus_nn18">6.11 References and pointers</a></H2> <p> @@ -1410,7 +1410,7 @@ templates and the STL. This was first added in SWIG-1.3.12. </p> -<H2><a name="SWIGPlus_nn19"></a>6.12 Pass and return by value</H2> +<H2><a name="SWIGPlus_nn19">6.12 Pass and return by value</a></H2> <p> @@ -1514,7 +1514,7 @@ classes that don't define a default constructor. It is not used for C++ pointers or references. </p> -<H2><a name="SWIGPlus_nn20"></a>6.13 Inheritance</H2> +<H2><a name="SWIGPlus_nn20">6.13 Inheritance</a></H2> <p> @@ -1700,7 +1700,7 @@ functions for virtual members that are already defined in a base class. </p> -<H2><a name="SWIGPlus_nn21"></a>6.14 A brief discussion of multiple inheritance, pointers, and type checking</H2> +<H2><a name="SWIGPlus_nn21">6.14 A brief discussion of multiple inheritance, pointers, and type checking</a></H2> <p> @@ -1832,7 +1832,7 @@ int y = B_function((B *) pB); In practice, the pointer is held as an integral number in the target language proxy class. </p> -<H2><a name="SWIGPlus_overloaded_methods"></a>6.15 Wrapping Overloaded Functions and Methods</H2> +<H2><a name="SWIGPlus_overloaded_methods">6.15 Wrapping Overloaded Functions and Methods</a></H2> <p> @@ -1895,7 +1895,7 @@ it might be used like this </pre> </div> -<H3><a name="SWIGPlus_nn24"></a>6.15.1 Dispatch function generation</H3> +<H3><a name="SWIGPlus_nn24">6.15.1 Dispatch function generation</a></H3> <p> @@ -2020,7 +2020,7 @@ checked in the same order as they appear in this ranking. If you're still confused, don't worry about it---SWIG is probably doing the right thing. </p> -<H3><a name="SWIGPlus_nn25"></a>6.15.2 Ambiguity in Overloading</H3> +<H3><a name="SWIGPlus_nn25">6.15.2 Ambiguity in Overloading</a></H3> <p> @@ -2138,7 +2138,7 @@ it means that the target language module has not yet implemented support for ove functions and methods. The only way to fix the problem is to read the next section. </p> -<H3><a name="SWIGPlus_ambiguity_resolution_renaming"></a>6.15.3 Ambiguity resolution and renaming</H3> +<H3><a name="SWIGPlus_ambiguity_resolution_renaming">6.15.3 Ambiguity resolution and renaming</a></H3> <p> @@ -2567,7 +2567,7 @@ to wrapping methods with default arguments was introduced. </ul> -<H3><a name="SWIGPlus_nn27"></a>6.15.4 Comments on overloading</H3> +<H3><a name="SWIGPlus_nn27">6.15.4 Comments on overloading</a></H3> <p> @@ -2584,7 +2584,7 @@ As a general rule, statically typed languages like Java are able to provide more than dynamically typed languages like Perl, Python, Ruby, and Tcl. </p> -<H2><a name="SWIGPlus_nn28"></a>6.16 Wrapping overloaded operators</H2> +<H2><a name="SWIGPlus_nn28">6.16 Wrapping overloaded operators</a></H2> <p> @@ -2768,7 +2768,7 @@ are ignored as well as conversion operators. </li> </ul> -<H2><a name="SWIGPlus_class_extension"></a>6.17 Class extension</H2> +<H2><a name="SWIGPlus_class_extension">6.17 Class extension</a></H2> <p> @@ -2867,7 +2867,7 @@ be used to extend a structure with more than just methods, a more suitable directive name has been chosen. </p> -<H2><a name="SWIGPlus_nn30"></a>6.18 Templates</H2> +<H2><a name="SWIGPlus_nn30">6.18 Templates</a></H2> <p> @@ -3701,7 +3701,7 @@ as the class name. For example: Similar changes apply to typemaps and other customization features. </p> -<H2><a name="SWIGPlus_namespaces"></a>6.19 Namespaces</H2> +<H2><a name="SWIGPlus_namespaces">6.19 Namespaces</a></H2> <p> @@ -4150,7 +4150,7 @@ with any namespace awareness. In the future, language modules may or may not p more advanced namespace support. </p> -<H3><a name="SWIGPlus_nspace"></a>6.19.1 The nspace feature for namespaces</H3> +<H3><a name="SWIGPlus_nspace">6.19.1 The nspace feature for namespaces</a></H3> <p> @@ -4231,7 +4231,7 @@ namespace MyWorld { <b>Compatibility Note:</b> The nspace feature was first introduced in SWIG-2.0.0. </p> -<H2><a name="SWIGPlus_renaming_templated_types_namespaces"></a>6.20 Renaming templated types in namespaces</H2> +<H2><a name="SWIGPlus_renaming_templated_types_namespaces">6.20 Renaming templated types in namespaces</a></H2> <p> @@ -4309,7 +4309,7 @@ namespace Space { </div> -<H2><a name="SWIGPlus_exception_specifications"></a>6.21 Exception specifications</H2> +<H2><a name="SWIGPlus_exception_specifications">6.21 Exception specifications</a></H2> <p> @@ -4360,7 +4360,7 @@ Consult the "<a href="Customization.html#Customization_exception">Exception hand The next section details a way of simulating an exception specification or replacing an existing one. </p> -<H2><a name="SWIGPlus_catches"></a>6.22 Exception handling with %catches</H2> +<H2><a name="SWIGPlus_catches">6.22 Exception handling with %catches</a></H2> <p> @@ -4410,7 +4410,7 @@ just a single catch handler for the base class, <tt>EBase</tt> will be generated </p> -<H2><a name="SWIGPlus_nn33"></a>6.23 Pointers to Members</H2> +<H2><a name="SWIGPlus_nn33">6.23 Pointers to Members</a></H2> <p> @@ -4460,7 +4460,7 @@ when checking types. However, no such support is currently provided for member pointers. </p> -<H2><a name="SWIGPlus_smart_pointers"></a>6.24 Smart pointers and operator->()</H2> +<H2><a name="SWIGPlus_smart_pointers">6.24 Smart pointers and operator->()</a></H2> <p> @@ -4672,7 +4672,7 @@ p = f.__deref__() # Raw pointer from operator-> <b>Note:</b> Smart pointer support was first added in SWIG-1.3.14. </p> -<H2><a name="SWIGPlus_ref_unref"></a>6.25 C++ reference counted objects - ref/unref feature</H2> +<H2><a name="SWIGPlus_ref_unref">6.25 C++ reference counted objects - ref/unref feature</a></H2> <p> @@ -4844,7 +4844,7 @@ exit # 'a' is released, SWIG unref 'a' called in the destructor wra -<H2><a name="SWIGPlus_nn35"></a>6.26 Using declarations and inheritance</H2> +<H2><a name="SWIGPlus_nn35">6.26 Using declarations and inheritance</a></H2> <p> @@ -5007,7 +5007,7 @@ public: </div> </ul> -<H2><a name="SWIGPlus_nested_classes"></a>6.27 Nested classes</H2> +<H2><a name="SWIGPlus_nested_classes">6.27 Nested classes</a></H2> <p> @@ -5071,7 +5071,7 @@ Nested class warnings could also not be suppressed using %warnfilter. </p> -<H2><a name="SWIGPlus_const"></a>6.28 A brief rant about const-correctness</H2> +<H2><a name="SWIGPlus_const">6.28 A brief rant about const-correctness</a></H2> <p> @@ -5129,7 +5129,7 @@ using another tool if maintaining constness is the most important part of your project. </p> -<H2><a name="SWIGPlus_nn42"></a>6.29 Where to go for more information</H2> +<H2><a name="SWIGPlus_nn42">6.29 Where to go for more information</a></H2> <p> diff --git a/Doc/Manual/Scilab.html b/Doc/Manual/Scilab.html index 5a894d587..1f5876270 100644 --- a/Doc/Manual/Scilab.html +++ b/Doc/Manual/Scilab.html @@ -8,7 +8,7 @@ <body bgcolor="#ffffff"> -<H1><a name="Scilab"></a>39 SWIG and Scilab</H1> +<H1><a name="Scilab">39 SWIG and Scilab</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -87,7 +87,7 @@ This chapter explains how to use SWIG for Scilab. After this introduction, you s </p> -<H2><a name="Scilab_preliminaries"></a>39.1 Preliminaries</H2> +<H2><a name="Scilab_preliminaries">39.1 Preliminaries</a></H2> <p> @@ -104,7 +104,7 @@ SWIG for Scilab supports C language. C++ is partially supported. See <a href="#S </p> -<H2><a name="Scilab_running_swig"></a>39.2 Running SWIG</H2> +<H2><a name="Scilab_running_swig">39.2 Running SWIG</a></H2> <p> @@ -138,7 +138,7 @@ Note: a code in an <tt>%inline</tt> section is both parsed and wrapped by SWIG, </p> -<H3><a name="Scilab_running_swig_generating_module"></a>39.2.1 Generating the module</H3> +<H3><a name="Scilab_running_swig_generating_module">39.2.1 Generating the module</a></H3> <p> @@ -181,7 +181,7 @@ The <tt>swig</tt> executable has several other command line options you can use. </p> -<H3><a name="Scilab_running_swig_building_module"></a>39.2.2 Building the module</H3> +<H3><a name="Scilab_running_swig_building_module">39.2.2 Building the module</a></H3> <p> @@ -201,7 +201,7 @@ $ gcc -shared example_wrap.o -o libexample.so Note: we supposed in this example that the path to the Scilab include directory is <tt>/usr/local/include/scilab</tt> (which is the case in a Debian environment), this should be changed for another environment. </p> -<H3><a name="Scilab_running_swig_loading_module"></a>39.2.3 Loading the module</H3> +<H3><a name="Scilab_running_swig_loading_module">39.2.3 Loading the module</a></H3> <p> @@ -225,7 +225,7 @@ Link done. which means that Scilab has successfully loaded the shared library. The module functions and other symbols are now available in Scilab. </p> -<H3><a name="Scilab_running_swig_using_module"></a>39.2.4 Using the module</H3> +<H3><a name="Scilab_running_swig_using_module">39.2.4 Using the module</a></H3> <p> @@ -259,7 +259,7 @@ ans = Note: for conciseness, we assume in the subsequent Scilab code examples that the modules have been beforehand built and loaded in Scilab. </p> -<H3><a name="Scilab_running_swig_options"></a>39.2.5 Scilab command line options</H3> +<H3><a name="Scilab_running_swig_options">39.2.5 Scilab command line options</a></H3> <p> @@ -314,10 +314,10 @@ $ swig -scilab -help </pre></div> -<H2><a name="Scilab_wrapping"></a>39.3 A basic tour of C/C++ wrapping</H2> +<H2><a name="Scilab_wrapping">39.3 A basic tour of C/C++ wrapping</a></H2> -<H3><a name="Scilab_wrapping_overview"></a>39.3.1 Overview</H3> +<H3><a name="Scilab_wrapping_overview">39.3.1 Overview</a></H3> <p> @@ -326,7 +326,7 @@ This means that functions, structs, classes, variables, etc... are interfaced th There are a few exceptions, such as constants and enumerations, which can be wrapped directly as Scilab variables. </p> -<H3><a name="Scilab_wrapping_identifiers"></a>39.3.2 Identifiers</H3> +<H3><a name="Scilab_wrapping_identifiers">39.3.2 Identifiers</a></H3> <p> @@ -337,7 +337,7 @@ In Scilab 5.x, identifier names are composed of 24 characters maximum (this limi In these cases, the <a href="SWIG.html#SWIG_rename_ignore">%rename directive</a> can be used to choose a different Scilab name. </p> -<H3><a name="Scilab_wrapping_functions"></a>39.3.3 Functions</H3> +<H3><a name="Scilab_wrapping_functions">39.3.3 Functions</a></H3> <p> @@ -368,7 +368,7 @@ ans = 24. </pre></div> -<H4><a name="Scilab_nn13"></a>39.3.3.1 Argument passing</H4> +<H4><a name="Scilab_nn13">39.3.3.1 Argument passing</a></H4> <p> @@ -421,7 +421,7 @@ In Scilab, parameters are passed by value. The output (and inout) parameters are 7. </pre></div> -<H4><a name="Scilab_nn14"></a>39.3.3.2 Multiple output arguments</H4> +<H4><a name="Scilab_nn14">39.3.3.2 Multiple output arguments</a></H4> <p> @@ -469,7 +469,7 @@ int divide(int n, int d, int q*, int *r) { </pre></div> -<H3><a name="Scilab_wrapping_global_variables"></a>39.3.4 Global variables</H3> +<H3><a name="Scilab_wrapping_global_variables">39.3.4 Global variables</a></H3> <p> @@ -538,10 +538,10 @@ It works the same:</p> </pre></div> -<H3><a name="Scilab_wrapping_constants_and_enums"></a>39.3.5 Constants and enumerations</H3> +<H3><a name="Scilab_wrapping_constants_and_enums">39.3.5 Constants and enumerations</a></H3> -<H4><a name="Scilab_wrapping_constants"></a>39.3.5.1 Constants</H4> +<H4><a name="Scilab_wrapping_constants">39.3.5.1 Constants</a></H4> <p> @@ -682,7 +682,7 @@ are mapped to Scilab variables, with the same name: 3.14 </pre></div> -<H4><a name="Scilab_wrapping_enums"></a>39.3.5.2 Enumerations</H4> +<H4><a name="Scilab_wrapping_enums">39.3.5.2 Enumerations</a></H4> <p> @@ -747,7 +747,7 @@ typedef enum { RED, BLUE, GREEN } color; </pre></div> -<H3><a name="Scilab_wrapping_pointers"></a>39.3.6 Pointers</H3> +<H3><a name="Scilab_wrapping_pointers">39.3.6 Pointers</a></H3> <p> @@ -789,7 +789,7 @@ These functions can be used in a natural way from Scilab: The user of a pointer is responsible for freeing it or, like in the example, closing any resources associated with it (just as is required in a C program). </p> -<H4><a name="Scilab_wrapping_pointers_pointer_adresses"></a>39.3.6.1 Utility functions</H4> +<H4><a name="Scilab_wrapping_pointers_pointer_adresses">39.3.6.1 Utility functions</a></H4> <p> @@ -820,7 +820,7 @@ SWIG comes with two pointer utility functions: --> fclose(f); </pre></div> -<H4><a name="Scilab_wrapping_pointers_null_pointers"></a>39.3.6.2 Null pointers</H4> +<H4><a name="Scilab_wrapping_pointers_null_pointers">39.3.6.2 Null pointers</a></H4> <p>By default, Scilab does not provide a way to test or create null pointers. @@ -836,7 +836,7 @@ But it is possible to have a null pointer by using the previous functions <tt>SW </pre></div> -<H3><a name="Scilab_wrapping_structs"></a>39.3.7 Structures</H3> +<H3><a name="Scilab_wrapping_structs">39.3.7 Structures</a></H3> <p> @@ -931,7 +931,7 @@ ans = </pre></div> -<H3><a name="Scilab_wrapping_cpp_classes"></a>39.3.8 C++ classes</H3> +<H3><a name="Scilab_wrapping_cpp_classes">39.3.8 C++ classes</a></H3> <p> @@ -981,7 +981,7 @@ ans = --> delete_Point(p2); </pre></div> -<H3><a name="Scilab_wrapping_cpp_inheritance"></a>39.3.9 C++ inheritance</H3> +<H3><a name="Scilab_wrapping_cpp_inheritance">39.3.9 C++ inheritance</a></H3> <p> @@ -1056,7 +1056,7 @@ But we can use either use the <tt>get_perimeter()</tt> function of the parent cl 18.84 </pre></div> -<H3><a name="Scilab_wrapping_pointers_references_values_arrays"></a>39.3.10 Pointers, references, values, and arrays</H3> +<H3><a name="Scilab_wrapping_pointers_references_values_arrays">39.3.10 Pointers, references, values, and arrays</a></H3> <p> @@ -1114,7 +1114,7 @@ All these functions will return a pointer to an instance of <tt>Foo</tt>. As the function <tt>spam7</tt> returns a value, new instance of <tt>Foo</tt> has to be allocated, and a pointer on this instance is returned. </p> -<H3><a name="Scilab_wrapping_cpp_templates"></a>39.3.11 C++ templates</H3> +<H3><a name="Scilab_wrapping_cpp_templates">39.3.11 C++ templates</a></H3> <p> @@ -1174,7 +1174,7 @@ Then in Scilab: More details on template support can be found in the <a href="SWIGPlus.html#SWIGPlus_nn30">templates</a> documentation. </p> -<H3><a name="Scilab_wrapping_cpp_operators"></a>39.3.12 C++ operators</H3> +<H3><a name="Scilab_wrapping_cpp_operators">39.3.12 C++ operators</a></H3> <p> @@ -1227,7 +1227,7 @@ private: </pre></div> -<H3><a name="Scilab_wrapping_cpp_namespaces"></a>39.3.13 C++ namespaces</H3> +<H3><a name="Scilab_wrapping_cpp_namespaces">39.3.13 C++ namespaces</a></H3> <p> @@ -1305,7 +1305,7 @@ Note: the <a href="SWIGPlus.html#SWIGPlus_nspace"><tt>nspace</tt></a> feature is </p> -<H3><a name="Scilab_wrapping_cpp_exceptions"></a>39.3.14 C++ exceptions</H3> +<H3><a name="Scilab_wrapping_cpp_exceptions">39.3.14 C++ exceptions</a></H3> <p> @@ -1388,17 +1388,17 @@ More complex or custom exception types require specific exception typemaps to be See the <a href="SWIGPlus.html#SWIGPlus">SWIG C++ documentation</a> for more details. </p> -<H3><a name="Scilab_wrapping_cpp_stl"></a>39.3.15 C++ STL</H3> +<H3><a name="Scilab_wrapping_cpp_stl">39.3.15 C++ STL</a></H3> <p> The Standard Template Library (STL) is partially supported. See <a href="#Scilab_typemaps_stl">STL</a> for more details. </p> -<H2><a name="Scilab_typemaps"></a>39.4 Type mappings and libraries</H2> +<H2><a name="Scilab_typemaps">39.4 Type mappings and libraries</a></H2> -<H3><a name="Scilab_typemaps_primitive_types"></a>39.4.1 Default primitive type mappings</H3> +<H3><a name="Scilab_typemaps_primitive_types">39.4.1 Default primitive type mappings</a></H3> <p> @@ -1447,7 +1447,7 @@ The default behaviour is for SWIG to generate code that will give a runtime erro </ul> -<H3><a name="Scilab_typemaps_non-primitive_types"></a>39.4.2 Default type mappings for non-primitive types</H3> +<H3><a name="Scilab_typemaps_non-primitive_types">39.4.2 Default type mappings for non-primitive types</a></H3> <p> @@ -1455,7 +1455,7 @@ The default mapped type for C/C++ non-primitive types is the Scilab pointer, for </p> -<H3><a name="Scilab_typemaps_arrays"></a>39.4.3 Arrays</H3> +<H3><a name="Scilab_typemaps_arrays">39.4.3 Arrays</a></H3> <p> @@ -1510,7 +1510,7 @@ void printArray(int values[], int len) { [ 0 1 2 3 ] </pre></div> -<H3><a name="Scilab_typemaps_pointer-to-pointers"></a>39.4.4 Pointer-to-pointers</H3> +<H3><a name="Scilab_typemaps_pointer-to-pointers">39.4.4 Pointer-to-pointers</a></H3> <p> @@ -1583,7 +1583,7 @@ void print_matrix(double **M, int nbRows, int nbCols) { </pre></div> -<H3><a name="Scilab_typemaps_matrices"></a>39.4.5 Matrices</H3> +<H3><a name="Scilab_typemaps_matrices">39.4.5 Matrices</a></H3> <p> @@ -1676,7 +1676,7 @@ The remarks made earlier for arrays also apply here: <li>There is no control while converting <tt>double</tt> values to integers, <tt>double</tt> values are truncated without any checking or warning.</li> </ul> -<H3><a name="Scilab_typemaps_stl"></a>39.4.6 STL</H3> +<H3><a name="Scilab_typemaps_stl">39.4.6 STL</a></H3> <p> @@ -1876,7 +1876,7 @@ ans = --> delete_PersonPtrSet(p); </pre></div> -<H2><a name="Scilab_module_initialization"></a>39.5 Module initialization</H2> +<H2><a name="Scilab_module_initialization">39.5 Module initialization</a></H2> <p> @@ -1900,7 +1900,7 @@ For example, to initialize the module <tt>example</tt>: --> example_Init(); </pre></div> -<H2><a name="Scilab_building_modes"></a>39.6 Building modes</H2> +<H2><a name="Scilab_building_modes">39.6 Building modes</a></H2> <p> @@ -1915,7 +1915,7 @@ To produce a dynamic module, when generating the wrapper, there are two possibil <li>the <tt>builder</tt> mode. In this mode, Scilab is responsible of building. </ul> -<H3><a name="Scilab_building_modes_nobuilder_mode"></a>39.6.1 No-builder mode</H3> +<H3><a name="Scilab_building_modes_nobuilder_mode">39.6.1 No-builder mode</a></H3> <p> @@ -1928,7 +1928,7 @@ This mode is the best option to use when you have to integrate the module build </p> -<H3><a name="Scilab_building_modes_builder_mode"></a>39.6.2 Builder mode</H3> +<H3><a name="Scilab_building_modes_builder_mode">39.6.2 Builder mode</a></H3> <p> @@ -1968,14 +1968,14 @@ The command is: $ swig -scilab -builder -buildercflags -I/opt/foo/include -builderldflags "-L/opt/foo/lib -lfoo" -buildersources baa1.cxx,baa2.cxx example.i </pre></div> -<H2><a name="Scilab_generated_scripts"></a>39.7 Generated scripts</H2> +<H2><a name="Scilab_generated_scripts">39.7 Generated scripts</a></H2> <p> In this part we give some details about the generated Scilab scripts. </p> -<H3><a name="Scilab_generated_scripts_builder_script"></a>39.7.1 Builder script</H3> +<H3><a name="Scilab_generated_scripts_builder_script">39.7.1 Builder script</a></H3> <p> @@ -2000,7 +2000,7 @@ ilib_build(ilib_name,table,files,libs); <li><tt><b>table</b></tt>: two column string matrix containing a table of pairs of 'scilab function name', 'C function name'.</li> </ul> -<H3><a name="Scilab_generated_scripts_loader_script"></a>39.7.2 Loader script</H3> +<H3><a name="Scilab_generated_scripts_loader_script">39.7.2 Loader script</a></H3> <p> @@ -2039,7 +2039,7 @@ clear get_file_path; </ul> -<H2><a name="Scilab_other_resources"></a>39.8 Other resources</H2> +<H2><a name="Scilab_other_resources">39.8 Other resources</a></H2> <ul> diff --git a/Doc/Manual/Scripting.html b/Doc/Manual/Scripting.html index c714fa0d7..9e5e85e7d 100644 --- a/Doc/Manual/Scripting.html +++ b/Doc/Manual/Scripting.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Scripting"></a>4 Scripting Languages</H1> +<H1><a name="Scripting">4 Scripting Languages</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -37,7 +37,7 @@ programming and the mechanisms by which scripting language interpreters access C and C++ code. </p> -<H2><a name="Scripting_nn2"></a>4.1 The two language view of the world</H2> +<H2><a name="Scripting_nn2">4.1 The two language view of the world</a></H2> <p> @@ -68,7 +68,7 @@ languages can be used for rapid prototyping, interactive debugging, scripting, and access to high-level data structures such associative arrays. </p> -<H2><a name="Scripting_nn3"></a>4.2 How does a scripting language talk to C?</H2> +<H2><a name="Scripting_nn3">4.2 How does a scripting language talk to C?</a></H2> <p> @@ -93,7 +93,7 @@ function, arguments, and so forth. The next few sections illustrate the process. </p> -<H3><a name="Scripting_nn4"></a>4.2.1 Wrapper functions</H3> +<H3><a name="Scripting_nn4">4.2.1 Wrapper functions</a></H3> <p> @@ -165,7 +165,7 @@ Python. Both require special wrappers to be written and both need additional initialization code. Only the specific details are different.</p> -<H3><a name="Scripting_nn5"></a>4.2.2 Variable linking</H3> +<H3><a name="Scripting_nn5">4.2.2 Variable linking</a></H3> <p> @@ -201,7 +201,7 @@ typing <tt>$Foo = 4</tt> would call the underlying set function to change the value. </p> -<H3><a name="Scripting_nn6"></a>4.2.3 Constants</H3> +<H3><a name="Scripting_nn6">4.2.3 Constants</a></H3> <p> @@ -222,7 +222,7 @@ functions for creating variables so installing constants is usually a trivial exercise. </p> -<H3><a name="Scripting_nn7"></a>4.2.4 Structures and classes</H3> +<H3><a name="Scripting_nn7">4.2.4 Structures and classes</a></H3> <p> @@ -283,7 +283,7 @@ internals of an object, the interpreter does not need to know anything about the actual representation of a <tt>Vector</tt>. </p> -<H3><a name="Scripting_nn8"></a>4.2.5 Proxy classes</H3> +<H3><a name="Scripting_nn8">4.2.5 Proxy classes</a></H3> <p> @@ -345,7 +345,7 @@ affect both objects equally and for all practical purposes, it appears as if you are simply manipulating a C/C++ object. </p> -<H2><a name="Scripting_nn9"></a>4.3 Building scripting language extensions</H2> +<H2><a name="Scripting_nn9">4.3 Building scripting language extensions</a></H2> <p> @@ -358,7 +358,7 @@ recompile the scripting language interpreter with your extensions added to it. </p> -<H3><a name="Scripting_nn10"></a>4.3.1 Shared libraries and dynamic loading</H3> +<H3><a name="Scripting_nn10">4.3.1 Shared libraries and dynamic loading</a></H3> <p> @@ -400,7 +400,7 @@ changing the link line to the following :</p> c++ -shared example.o example_wrap.o -o example.so </pre></div> -<H3><a name="Scripting_nn11"></a>4.3.2 Linking with shared libraries</H3> +<H3><a name="Scripting_nn11">4.3.2 Linking with shared libraries</a></H3> <p> @@ -447,7 +447,7 @@ the path using linker options instead. </ul> -<H3><a name="Scripting_nn12"></a>4.3.3 Static linking</H3> +<H3><a name="Scripting_nn12">4.3.3 Static linking</a></H3> <p> diff --git a/Doc/Manual/Tcl.html b/Doc/Manual/Tcl.html index 874a5325a..a3e6ae99a 100644 --- a/Doc/Manual/Tcl.html +++ b/Doc/Manual/Tcl.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Tcl"></a>40 SWIG and Tcl</H1> +<H1><a name="Tcl">40 SWIG and Tcl</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -83,7 +83,7 @@ Tcl 8.0 or a later release. Earlier releases of SWIG supported Tcl 7.x, but this is no longer supported. </p> -<H2><a name="Tcl_nn2"></a>40.1 Preliminaries</H2> +<H2><a name="Tcl_nn2">40.1 Preliminaries</a></H2> <p> @@ -109,7 +109,7 @@ build a Tcl extension module. To finish building the module, you need to compile this file and link it with the rest of your program. </p> -<H3><a name="Tcl_nn3"></a>40.1.1 Getting the right header files</H3> +<H3><a name="Tcl_nn3">40.1.1 Getting the right header files</a></H3> <p> @@ -127,7 +127,7 @@ this is the case, you should probably make a symbolic link so that <tt>tcl.h</tt header file. </p> -<H3><a name="Tcl_nn4"></a>40.1.2 Compiling a dynamic module</H3> +<H3><a name="Tcl_nn4">40.1.2 Compiling a dynamic module</a></H3> <p> @@ -163,7 +163,7 @@ The name of the module is specified using the <tt>%module</tt> directive or the <tt>-module</tt> command line option. </p> -<H3><a name="Tcl_nn5"></a>40.1.3 Static linking</H3> +<H3><a name="Tcl_nn5">40.1.3 Static linking</a></H3> <p> @@ -229,7 +229,7 @@ minimal in most situations (and quite frankly not worth the extra hassle in the opinion of this author). </p> -<H3><a name="Tcl_nn6"></a>40.1.4 Using your module</H3> +<H3><a name="Tcl_nn6">40.1.4 Using your module</a></H3> <p> @@ -357,7 +357,7 @@ to the default system configuration (this requires root access and you will need the man pages). </p> -<H3><a name="Tcl_nn7"></a>40.1.5 Compilation of C++ extensions</H3> +<H3><a name="Tcl_nn7">40.1.5 Compilation of C++ extensions</a></H3> <p> @@ -440,7 +440,7 @@ erratic program behavior. If working with lots of software components, you might want to investigate using a more formal standard such as COM. </p> -<H3><a name="Tcl_nn8"></a>40.1.6 Compiling for 64-bit platforms</H3> +<H3><a name="Tcl_nn8">40.1.6 Compiling for 64-bit platforms</a></H3> <p> @@ -467,7 +467,7 @@ also introduce problems on platforms that support more than one linking standard (e.g., -o32 and -n32 on Irix). </p> -<H3><a name="Tcl_nn9"></a>40.1.7 Setting a package prefix</H3> +<H3><a name="Tcl_nn9">40.1.7 Setting a package prefix</a></H3> <p> @@ -486,7 +486,7 @@ option will append the prefix to the name when creating a command and call it "<tt>Foo_bar</tt>". </p> -<H3><a name="Tcl_nn10"></a>40.1.8 Using namespaces</H3> +<H3><a name="Tcl_nn10">40.1.8 Using namespaces</a></H3> <p> @@ -508,7 +508,7 @@ When the <tt>-namespace</tt> option is used, objects in the module are always accessed with the namespace name such as <tt>Foo::bar</tt>. </p> -<H2><a name="Tcl_nn11"></a>40.2 Building Tcl/Tk Extensions under Windows 95/NT</H2> +<H2><a name="Tcl_nn11">40.2 Building Tcl/Tk Extensions under Windows 95/NT</a></H2> <p> @@ -519,7 +519,7 @@ covers the process of using SWIG with Microsoft Visual C++. although the procedure may be similar with other compilers. </p> -<H3><a name="Tcl_nn12"></a>40.2.1 Running SWIG from Developer Studio</H3> +<H3><a name="Tcl_nn12">40.2.1 Running SWIG from Developer Studio</a></H3> <p> @@ -577,7 +577,7 @@ MSDOS > tclsh80 % </pre></div> -<H3><a name="Tcl_nn13"></a>40.2.2 Using NMAKE</H3> +<H3><a name="Tcl_nn13">40.2.2 Using NMAKE</a></H3> <p> @@ -640,7 +640,7 @@ to get you started. With a little practice, you'll be making lots of Tcl extensions. </p> -<H2><a name="Tcl_nn14"></a>40.3 A tour of basic C/C++ wrapping</H2> +<H2><a name="Tcl_nn14">40.3 A tour of basic C/C++ wrapping</a></H2> <p> @@ -651,7 +651,7 @@ classes. This section briefly covers the essential aspects of this wrapping. </p> -<H3><a name="Tcl_nn15"></a>40.3.1 Modules</H3> +<H3><a name="Tcl_nn15">40.3.1 Modules</a></H3> <p> @@ -685,7 +685,7 @@ To fix this, supply an extra argument to <tt>load</tt> like this: </pre> </div> -<H3><a name="Tcl_nn16"></a>40.3.2 Functions</H3> +<H3><a name="Tcl_nn16">40.3.2 Functions</a></H3> <p> @@ -710,7 +710,7 @@ like you think it does: % </pre></div> -<H3><a name="Tcl_nn17"></a>40.3.3 Global variables</H3> +<H3><a name="Tcl_nn17">40.3.3 Global variables</a></H3> <p> @@ -790,7 +790,7 @@ extern char *path; // Read-only (due to %immutable) </pre> </div> -<H3><a name="Tcl_nn18"></a>40.3.4 Constants and enums</H3> +<H3><a name="Tcl_nn18">40.3.4 Constants and enums</a></H3> <p> @@ -874,7 +874,7 @@ When an identifier name is given, it is used to perform an implicit hash-table l conversion. This allows the <tt>global</tt> statement to be omitted. </p> -<H3><a name="Tcl_nn19"></a>40.3.5 Pointers</H3> +<H3><a name="Tcl_nn19">40.3.5 Pointers</a></H3> <p> @@ -970,7 +970,7 @@ C-style cast may return a bogus result whereas as the C++-style cast will return <tt>None</tt> if the conversion can't be performed. </p> -<H3><a name="Tcl_nn20"></a>40.3.6 Structures</H3> +<H3><a name="Tcl_nn20">40.3.6 Structures</a></H3> <p> @@ -1252,7 +1252,7 @@ Note: Tcl only destroys the underlying object if it has ownership. See the memory management section that appears shortly. </p> -<H3><a name="Tcl_nn21"></a>40.3.7 C++ classes</H3> +<H3><a name="Tcl_nn21">40.3.7 C++ classes</a></H3> <p> @@ -1319,7 +1319,7 @@ In Tcl, the static member is accessed as follows: </pre> </div> -<H3><a name="Tcl_nn22"></a>40.3.8 C++ inheritance</H3> +<H3><a name="Tcl_nn22">40.3.8 C++ inheritance</a></H3> <p> @@ -1368,7 +1368,7 @@ For instance: It is safe to use multiple inheritance with SWIG. </p> -<H3><a name="Tcl_nn23"></a>40.3.9 Pointers, references, values, and arrays</H3> +<H3><a name="Tcl_nn23">40.3.9 Pointers, references, values, and arrays</a></H3> <p> @@ -1422,7 +1422,7 @@ to hold the result and a pointer is returned (Tcl will release this memory when the return value is garbage collected). </p> -<H3><a name="Tcl_nn24"></a>40.3.10 C++ overloaded functions</H3> +<H3><a name="Tcl_nn24">40.3.10 C++ overloaded functions</a></H3> <p> @@ -1545,7 +1545,7 @@ first declaration takes precedence. Please refer to the "SWIG and C++" chapter for more information about overloading. </p> -<H3><a name="Tcl_nn25"></a>40.3.11 C++ operators</H3> +<H3><a name="Tcl_nn25">40.3.11 C++ operators</a></H3> <p> @@ -1647,7 +1647,7 @@ There are ways to make this operator appear as part of the class using the <tt>% Keep reading. </p> -<H3><a name="Tcl_nn26"></a>40.3.12 C++ namespaces</H3> +<H3><a name="Tcl_nn26">40.3.12 C++ namespaces</a></H3> <p> @@ -1711,7 +1711,7 @@ utilizes thousands of small deeply nested namespaces each with identical symbol names, well, then you get what you deserve. </p> -<H3><a name="Tcl_nn27"></a>40.3.13 C++ templates</H3> +<H3><a name="Tcl_nn27">40.3.13 C++ templates</a></H3> <p> @@ -1763,7 +1763,7 @@ More details can be found in the <a href="SWIGPlus.html#SWIGPlus">SWIG and C++</ examples will appear later. </p> -<H3><a name="Tcl_nn28"></a>40.3.14 C++ Smart Pointers</H3> +<H3><a name="Tcl_nn28">40.3.14 C++ Smart Pointers</a></H3> <p> @@ -1847,7 +1847,7 @@ simply use the <tt>__deref__()</tt> method. For example: </pre> </div> -<H2><a name="Tcl_nn29"></a>40.4 Further details on the Tcl class interface</H2> +<H2><a name="Tcl_nn29">40.4 Further details on the Tcl class interface</a></H2> <p> @@ -1860,7 +1860,7 @@ of low-level details were omitted. This section provides a brief overview of how the proxy classes work. </p> -<H3><a name="Tcl_nn30"></a>40.4.1 Proxy classes</H3> +<H3><a name="Tcl_nn30">40.4.1 Proxy classes</a></H3> <p> @@ -1925,7 +1925,7 @@ function. This allows objects to be encapsulated objects that look a lot like as shown in the last section. </p> -<H3><a name="Tcl_nn31"></a>40.4.2 Memory management</H3> +<H3><a name="Tcl_nn31">40.4.2 Memory management</a></H3> <p> @@ -2113,7 +2113,7 @@ typemaps--an advanced topic discussed later. </p> -<H2><a name="Tcl_nn32"></a>40.5 Input and output parameters</H2> +<H2><a name="Tcl_nn32">40.5 Input and output parameters</a></H2> <p> @@ -2301,7 +2301,7 @@ set c [lindex $dim 1] </pre> </div> -<H2><a name="Tcl_nn33"></a>40.6 Exception handling </H2> +<H2><a name="Tcl_nn33">40.6 Exception handling </a></H2> <p> @@ -2435,7 +2435,7 @@ Since SWIG's exception handling is user-definable, you are not limited to C++ ex See the chapter on "<a href="Customization.html#Customization">Customization Features</a>" for more examples. </p> -<H2><a name="Tcl_nn34"></a>40.7 Typemaps</H2> +<H2><a name="Tcl_nn34">40.7 Typemaps</a></H2> <p> @@ -2452,7 +2452,7 @@ Typemaps are only used if you want to change some aspect of the primitive C-Tcl interface. </p> -<H3><a name="Tcl_nn35"></a>40.7.1 What is a typemap?</H3> +<H3><a name="Tcl_nn35">40.7.1 What is a typemap?</a></H3> <p> @@ -2569,7 +2569,7 @@ parameter is omitted): </pre> </div> -<H3><a name="Tcl_nn36"></a>40.7.2 Tcl typemaps</H3> +<H3><a name="Tcl_nn36">40.7.2 Tcl typemaps</a></H3> <p> @@ -2707,7 +2707,7 @@ Initialize an argument to a value before any conversions occur. Examples of these methods will appear shortly. </p> -<H3><a name="Tcl_nn37"></a>40.7.3 Typemap variables</H3> +<H3><a name="Tcl_nn37">40.7.3 Typemap variables</a></H3> <p> @@ -2778,7 +2778,7 @@ properly assigned. The Tcl name of the wrapper function being created. </div> -<H3><a name="Tcl_nn38"></a>40.7.4 Converting a Tcl list to a char ** </H3> +<H3><a name="Tcl_nn38">40.7.4 Converting a Tcl list to a char ** </a></H3> <p> @@ -2840,7 +2840,7 @@ argv[2] = Larry 3 </pre></div> -<H3><a name="Tcl_nn39"></a>40.7.5 Returning values in arguments</H3> +<H3><a name="Tcl_nn39">40.7.5 Returning values in arguments</a></H3> <p> @@ -2882,7 +2882,7 @@ result, a Tcl function using these typemaps will work like this : % </pre></div> -<H3><a name="Tcl_nn40"></a>40.7.6 Useful functions</H3> +<H3><a name="Tcl_nn40">40.7.6 Useful functions</a></H3> <p> @@ -2958,7 +2958,7 @@ int Tcl_IsShared(Tcl_Obj *obj); </pre> </div> -<H3><a name="Tcl_nn41"></a>40.7.7 Standard typemaps</H3> +<H3><a name="Tcl_nn41">40.7.7 Standard typemaps</a></H3> <p> @@ -3043,7 +3043,7 @@ work) </pre> </div> -<H3><a name="Tcl_nn42"></a>40.7.8 Pointer handling</H3> +<H3><a name="Tcl_nn42">40.7.8 Pointer handling</a></H3> <p> @@ -3119,7 +3119,7 @@ For example: </pre> </div> -<H2><a name="Tcl_nn43"></a>40.8 Turning a SWIG module into a Tcl Package.</H2> +<H2><a name="Tcl_nn43">40.8 Turning a SWIG module into a Tcl Package.</a></H2> <p> @@ -3191,7 +3191,7 @@ As a final note, most SWIG examples do not yet use the to use the <tt>load</tt> command instead. </p> -<H2><a name="Tcl_nn44"></a>40.9 Building new kinds of Tcl interfaces (in Tcl)</H2> +<H2><a name="Tcl_nn44">40.9 Building new kinds of Tcl interfaces (in Tcl)</a></H2> <p> @@ -3290,7 +3290,7 @@ danger of blowing something up (although it is easily accomplished with an out of bounds array access). </p> -<H3><a name="Tcl_nn45"></a>40.9.1 Proxy classes</H3> +<H3><a name="Tcl_nn45">40.9.1 Proxy classes</a></H3> <p> @@ -3411,7 +3411,7 @@ short, but clever Tcl script can be combined with SWIG to do many interesting things. </p> -<H2><a name="Tcl_nn46"></a>40.10 Tcl/Tk Stubs</H2> +<H2><a name="Tcl_nn46">40.10 Tcl/Tk Stubs</a></H2> <p> diff --git a/Doc/Manual/Typemaps.html b/Doc/Manual/Typemaps.html index 3d6abf88e..770604684 100644 --- a/Doc/Manual/Typemaps.html +++ b/Doc/Manual/Typemaps.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Typemaps"></a>11 Typemaps</H1> +<H1><a name="Typemaps">11 Typemaps</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -97,7 +97,7 @@ -<H2><a name="Typemaps_nn2"></a>11.1 Introduction</H2> +<H2><a name="Typemaps_nn2">11.1 Introduction</a></H2> <p> @@ -114,7 +114,7 @@ to re-read the earlier chapters if you have found your way to this chapter with only a vague idea of what SWIG already does by default. </p> -<H3><a name="Typemaps_nn3"></a>11.1.1 Type conversion</H3> +<H3><a name="Typemaps_nn3">11.1.1 Type conversion</a></H3> <p> @@ -207,7 +207,7 @@ to read the extension documentation for your favorite language to know how it works (an exercise left to the reader). </p> -<H3><a name="Typemaps_nn4"></a>11.1.2 Typemaps</H3> +<H3><a name="Typemaps_nn4">11.1.2 Typemaps</a></H3> <p> @@ -308,7 +308,7 @@ parts of the generated wrapper functions. Because arbitrary code can be insert possible to completely change the way in which values are converted. </p> -<H3><a name="Typemaps_nn5"></a>11.1.3 Pattern matching</H3> +<H3><a name="Typemaps_nn5">11.1.3 Pattern matching</a></H3> <p> @@ -410,7 +410,7 @@ In this case, a single input object is expanded into a pair of C arguments. Thi provides a hint to the unusual variable naming scheme involving <tt>$1</tt>, <tt>$2</tt>, and so forth. </p> -<H3><a name="Typemaps_nn6"></a>11.1.4 Reusing typemaps</H3> +<H3><a name="Typemaps_nn6">11.1.4 Reusing typemaps</a></H3> <p> @@ -466,7 +466,7 @@ typedef int size_t; then SWIG already knows that the <tt>int</tt> typemaps apply. You don't have to do anything. </p> -<H3><a name="Typemaps_nn7"></a>11.1.5 What can be done with typemaps?</H3> +<H3><a name="Typemaps_nn7">11.1.5 What can be done with typemaps?</a></H3> <p> @@ -578,7 +578,7 @@ typemaps that expand upon this list. For example, the Java module defines a var aspects of the Java bindings. Consult language specific documentation for further details. </p> -<H3><a name="Typemaps_nn8"></a>11.1.6 What can't be done with typemaps?</H3> +<H3><a name="Typemaps_nn8">11.1.6 What can't be done with typemaps?</a></H3> <p> @@ -641,7 +641,7 @@ void wrap_foo(char *s, int x) { </pre> </div> -<H3><a name="Typemaps_aspects"></a>11.1.7 Similarities to Aspect Oriented Programming</H3> +<H3><a name="Typemaps_aspects">11.1.7 Similarities to Aspect Oriented Programming</a></H3> <p> @@ -659,7 +659,7 @@ SWIG can also be viewed as has having a second set of aspects based around <a hr Features such as <tt>%exception</tt> are also cross-cutting concerns as they encapsulate code that can be used to add logging or exception handling to any function. </p> -<H3><a name="Typemaps_nn9"></a>11.1.8 The rest of this chapter</H3> +<H3><a name="Typemaps_nn9">11.1.8 The rest of this chapter</a></H3> <p> @@ -679,14 +679,14 @@ of "The C Programming Language" by Kernighan and Ritchie or "The C++ Programming Language" by Stroustrup before going any further. </p> -<H2><a name="Typemaps_nn10"></a>11.2 Typemap specifications</H2> +<H2><a name="Typemaps_nn10">11.2 Typemap specifications</a></H2> <p> This section describes the behavior of the <tt>%typemap</tt> directive itself. </p> -<H3><a name="Typemaps_defining"></a>11.2.1 Defining a typemap</H3> +<H3><a name="Typemaps_defining">11.2.1 Defining a typemap</a></H3> <p> @@ -799,7 +799,7 @@ Admittedly, it's not the most readable syntax at first glance. However, the pur individual pieces will become clear. </p> -<H3><a name="Typemaps_nn12"></a>11.2.2 Typemap scope</H3> +<H3><a name="Typemaps_nn12">11.2.2 Typemap scope</a></H3> <p> @@ -849,7 +849,7 @@ class Foo { </pre> </div> -<H3><a name="Typemaps_nn13"></a>11.2.3 Copying a typemap</H3> +<H3><a name="Typemaps_nn13">11.2.3 Copying a typemap</a></H3> <p> @@ -907,7 +907,7 @@ The patterns for <tt>%apply</tt> follow the same rules as for <tt>%typemap</tt>. </pre> </div> -<H3><a name="Typemaps_nn14"></a>11.2.4 Deleting a typemap</H3> +<H3><a name="Typemaps_nn14">11.2.4 Deleting a typemap</a></H3> <p> @@ -940,7 +940,7 @@ For example: after the clear operation. </p> -<H3><a name="Typemaps_nn15"></a>11.2.5 Placement of typemaps</H3> +<H3><a name="Typemaps_nn15">11.2.5 Placement of typemaps</a></H3> <p> @@ -1020,7 +1020,7 @@ It should be noted that for scoping to work, SWIG has to know that <tt>string</t within a particular namespace. In this example, this is done using the forward class declaration <tt>class string</tt>. </p> -<H2><a name="Typemaps_pattern_matching"></a>11.3 Pattern matching rules</H2> +<H2><a name="Typemaps_pattern_matching">11.3 Pattern matching rules</a></H2> <p> @@ -1028,7 +1028,7 @@ The section describes the pattern matching rules by which C/C++ datatypes are as The matching rules can be observed in practice by using the debugging options also described. </p> -<H3><a name="Typemaps_nn17"></a>11.3.1 Basic matching rules</H3> +<H3><a name="Typemaps_nn17">11.3.1 Basic matching rules</a></H3> <p> @@ -1127,7 +1127,7 @@ void F(int x[1000]); // int [ANY] rule (typemap 5) stripped all qualifiers in one step. </p> -<H3><a name="Typemaps_typedef_reductions"></a>11.3.2 Typedef reductions matching</H3> +<H3><a name="Typemaps_typedef_reductions">11.3.2 Typedef reductions matching</a></H3> <p> @@ -1302,7 +1302,7 @@ void go(Struct aStruct); </pre> </div> -<H3><a name="Typemaps_nn19"></a>11.3.3 Default typemap matching rules</H3> +<H3><a name="Typemaps_nn19">11.3.3 Default typemap matching rules</a></H3> <p> @@ -1440,7 +1440,7 @@ Finally the best way to view the typemap matching rules in action is via the <a simpler scheme to match the current C++ class template partial specialization matching rules. </p> -<H3><a name="Typemaps_multi_argument_typemaps_patterns"></a>11.3.4 Multi-arguments typemaps</H3> +<H3><a name="Typemaps_multi_argument_typemaps_patterns">11.3.4 Multi-arguments typemaps</a></H3> <p> @@ -1470,7 +1470,7 @@ but all subsequent arguments must match exactly. </p> -<H3><a name="Typemaps_matching_template_comparison"></a>11.3.5 Matching rules compared to C++ templates</H3> +<H3><a name="Typemaps_matching_template_comparison">11.3.5 Matching rules compared to C++ templates</a></H3> <p> @@ -1629,7 +1629,7 @@ are similar to those for specialized template handling. </p> -<H3><a name="Typemaps_debugging_search"></a>11.3.6 Debugging typemap pattern matching</H3> +<H3><a name="Typemaps_debugging_search">11.3.6 Debugging typemap pattern matching</a></H3> <p> @@ -1842,7 +1842,7 @@ Also the types may be displayed slightly differently - <tt>char const *</tt> and </li> </ul> -<H2><a name="Typemaps_nn21"></a>11.4 Code generation rules</H2> +<H2><a name="Typemaps_nn21">11.4 Code generation rules</a></H2> <p> @@ -1850,7 +1850,7 @@ This section describes rules by which typemap code is inserted into the generated wrapper code. </p> -<H3><a name="Typemaps_nn22"></a>11.4.1 Scope</H3> +<H3><a name="Typemaps_nn22">11.4.1 Scope</a></H3> <p> @@ -1928,7 +1928,7 @@ a block scope when it is emitted. This sometimes results in a less complicated Note that only the third of the three typemaps have the typemap code passed through the SWIG preprocessor. </p> -<H3><a name="Typemaps_nn23"></a>11.4.2 Declaring new local variables</H3> +<H3><a name="Typemaps_nn23">11.4.2 Declaring new local variables</a></H3> <p> @@ -2095,7 +2095,7 @@ each type must have its own local variable declaration. </div> -<H3><a name="Typemaps_special_variables"></a>11.4.3 Special variables</H3> +<H3><a name="Typemaps_special_variables">11.4.3 Special variables</a></H3> <p> @@ -2347,7 +2347,7 @@ Another approach, which only works for arrays is to use the <tt>$1_basetype</tt> </pre> </div> -<H3><a name="Typemaps_special_variable_macros"></a>11.4.4 Special variable macros</H3> +<H3><a name="Typemaps_special_variable_macros">11.4.4 Special variable macros</a></H3> <p> @@ -2359,7 +2359,7 @@ it is done during the SWIG parsing/compilation stages. The following special variable macros are available across all language modules. </p> -<H4><a name="Typemaps_special_macro_descriptor"></a>11.4.4.1 $descriptor(type)</H4> +<H4><a name="Typemaps_special_macro_descriptor">11.4.4.1 $descriptor(type)</a></H4> <p> @@ -2370,7 +2370,7 @@ For example, <tt>$descriptor(std::vector<int> *)</tt> will expand into <tt This macro is mostly used in the scripting target languages and is demonstrated later in the <a href="#Typemaps_runtime_type_checker_usage">Run-time type checker usage</a> section. </p> -<H4><a name="Typemaps_special_macro_typemap"></a>11.4.4.2 $typemap(method, typepattern)</H4> +<H4><a name="Typemaps_special_macro_typemap">11.4.4.2 $typemap(method, typepattern)</a></H4> <p> @@ -2428,7 +2428,7 @@ The result is the following expansion </div> -<H3><a name="Typemaps_special_variable_attributes"></a>11.4.5 Special variables and typemap attributes</H3> +<H3><a name="Typemaps_special_variable_attributes">11.4.5 Special variables and typemap attributes</a></H3> <p> @@ -2455,7 +2455,7 @@ is equivalent to the following as <tt>$*1_ltype</tt> expands to <tt>unsigned int </pre> </div> -<H3><a name="Typemaps_special_variables_and_macros"></a>11.4.6 Special variables combined with special variable macros</H3> +<H3><a name="Typemaps_special_variables_and_macros">11.4.6 Special variables combined with special variable macros</a></H3> <p> @@ -2497,7 +2497,7 @@ which then expands to: </div> -<H2><a name="Typemaps_nn25"></a>11.5 Common typemap methods</H2> +<H2><a name="Typemaps_nn25">11.5 Common typemap methods</a></H2> <p> @@ -2505,7 +2505,7 @@ The set of typemaps recognized by a language module may vary. However, the following typemap methods are nearly universal: </p> -<H3><a name="Typemaps_nn26"></a>11.5.1 "in" typemap</H3> +<H3><a name="Typemaps_nn26">11.5.1 "in" typemap</a></H3> <p> @@ -2565,7 +2565,7 @@ Usually <tt>numinputs</tt> is not specified, whereupon the default value is 1, t is the same as the old "ignore" typemap. </p> -<H3><a name="Typemaps_nn27"></a>11.5.2 "typecheck" typemap</H3> +<H3><a name="Typemaps_nn27">11.5.2 "typecheck" typemap</a></H3> <p> @@ -2591,7 +2591,7 @@ If you define new "in" typemaps <em>and</em> your program uses overloaded method "typecheck" typemaps. More details about this follow in the <a href="#Typemaps_overloading">Typemaps and overloading</a> section. </p> -<H3><a name="Typemaps_nn28"></a>11.5.3 "out" typemap</H3> +<H3><a name="Typemaps_nn28">11.5.3 "out" typemap</a></H3> <p> @@ -2622,7 +2622,7 @@ $symname - Name of function/method being wrapped The "out" typemap supports an optional attribute flag called "optimal". This is for code optimisation and is detailed in the <a href="#Typemaps_optimal">Optimal code generation when returning by value</a> section. </p> -<H3><a name="Typemaps_nn29"></a>11.5.4 "arginit" typemap</H3> +<H3><a name="Typemaps_nn29">11.5.4 "arginit" typemap</a></H3> <p> @@ -2641,7 +2641,7 @@ For example: </pre> </div> -<H3><a name="Typemaps_nn30"></a>11.5.5 "default" typemap</H3> +<H3><a name="Typemaps_nn30">11.5.5 "default" typemap</a></H3> <p> @@ -2674,7 +2674,7 @@ See the <a href="SWIG.html#SWIG_default_args">Default/optional arguments</a> sec for further information on default argument wrapping. </p> -<H3><a name="Typemaps_nn31"></a>11.5.6 "check" typemap</H3> +<H3><a name="Typemaps_nn31">11.5.6 "check" typemap</a></H3> <p> @@ -2693,7 +2693,7 @@ converted. For example: </pre> </div> -<H3><a name="Typemaps_nn32"></a>11.5.7 "argout" typemap</H3> +<H3><a name="Typemaps_nn32">11.5.7 "argout" typemap</a></H3> <p> @@ -2739,7 +2739,7 @@ return values are often appended to return value of the function. See the <tt>typemaps.i</tt> library file for examples. </p> -<H3><a name="Typemaps_nn33"></a>11.5.8 "freearg" typemap</H3> +<H3><a name="Typemaps_nn33">11.5.8 "freearg" typemap</a></H3> <p> @@ -2772,7 +2772,7 @@ be used in other typemaps whenever a wrapper function needs to abort prematurely. </p> -<H3><a name="Typemaps_nn34"></a>11.5.9 "newfree" typemap</H3> +<H3><a name="Typemaps_nn34">11.5.9 "newfree" typemap</a></H3> <p> @@ -2801,7 +2801,7 @@ string *foo(); See <a href="Customization.html#Customization_ownership">Object ownership and %newobject</a> for further details. </p> -<H3><a name="Typemaps_nn35"></a>11.5.10 "memberin" typemap</H3> +<H3><a name="Typemaps_nn35">11.5.10 "memberin" typemap</a></H3> <p> @@ -2823,7 +2823,7 @@ It is rarely necessary to write "memberin" typemaps---SWIG already provides a default implementation for arrays, strings, and other objects. </p> -<H3><a name="Typemaps_nn36"></a>11.5.11 "varin" typemap</H3> +<H3><a name="Typemaps_nn36">11.5.11 "varin" typemap</a></H3> <p> @@ -2831,7 +2831,7 @@ The "varin" typemap is used to convert objects in the target language to C for t purposes of assigning to a C/C++ global variable. This is implementation specific. </p> -<H3><a name="Typemaps_nn37"></a>11.5.12 "varout" typemap</H3> +<H3><a name="Typemaps_nn37">11.5.12 "varout" typemap</a></H3> <p> @@ -2839,7 +2839,7 @@ The "varout" typemap is used to convert a C/C++ object to an object in the targe language when reading a C/C++ global variable. This is implementation specific. </p> -<H3><a name="throws_typemap"></a>11.5.13 "throws" typemap</H3> +<H3><a name="throws_typemap">11.5.13 "throws" typemap</a></H3> <p> @@ -2885,7 +2885,7 @@ Note that if your methods do not have an exception specification yet they do thr For a neat way to handle these, see the <a href="Customization.html#Customization_exception">Exception handling with %exception</a> section. </p> -<H2><a name="Typemaps_nn39"></a>11.6 Some typemap examples</H2> +<H2><a name="Typemaps_nn39">11.6 Some typemap examples</a></H2> <p> @@ -2893,7 +2893,7 @@ This section contains a few examples. Consult language module documentation for more examples. </p> -<H3><a name="Typemaps_nn40"></a>11.6.1 Typemaps for arrays</H3> +<H3><a name="Typemaps_nn40">11.6.1 Typemaps for arrays</a></H3> <p> @@ -3152,7 +3152,7 @@ Now, you will find that member access is quite nice: useless and has since been eliminated. To return structure members, simply use the "out" typemap. </p> -<H3><a name="Typemaps_nn41"></a>11.6.2 Implementing constraints with typemaps</H3> +<H3><a name="Typemaps_nn41">11.6.2 Implementing constraints with typemaps</a></H3> <p> @@ -3200,7 +3200,7 @@ a NULL pointer. As a result, SWIG can often prevent a potential segmentation faults or other run-time problems by raising an exception rather than blindly passing values to the underlying C/C++ program.</p> -<H2><a name="Typemaps_nn43"></a>11.7 Typemaps for multiple target languages</H2> +<H2><a name="Typemaps_nn43">11.7 Typemaps for multiple target languages</a></H2> <p> @@ -3230,7 +3230,7 @@ The example above also shows a common approach of issuing a warning for an as ye <tt>%typemap(ruby,in) int "$1 = NUM2INT($input);"</tt>. </p> -<H2><a name="Typemaps_optimal"></a>11.8 Optimal code generation when returning by value</H2> +<H2><a name="Typemaps_optimal">11.8 Optimal code generation when returning by value</a></H2> <p> @@ -3419,7 +3419,7 @@ example.i:7: Warning 475: optimal attribute usage in the out typemap. However, it doesn't always get it right, for example when <tt>$1</tt> is within some commented out code. </p> -<H2><a name="Typemaps_multi_argument_typemaps"></a>11.9 Multi-argument typemaps</H2> +<H2><a name="Typemaps_multi_argument_typemaps">11.9 Multi-argument typemaps</a></H2> <p> @@ -3686,7 +3686,7 @@ with non-consecutive C/C++ arguments; a workaround such as a helper function re- the arguments to make them consecutive will need to be written. </p> -<H2><a name="Typemaps_warnings"></a>11.10 Typemap warnings</H2> +<H2><a name="Typemaps_warnings">11.10 Typemap warnings</a></H2> <p> @@ -3695,7 +3695,7 @@ See the information in the <a href="Warnings.html#Warnings_nn5">issuing warnings </p> -<H2><a name="Typemaps_fragments"></a>11.11 Typemap fragments</H2> +<H2><a name="Typemaps_fragments">11.11 Typemap fragments</a></H2> <p> @@ -3948,7 +3948,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>11.11.1 Fragment type specialization</H3> +<H3><a name="Typemaps_fragment_type_specialization">11.11.1 Fragment type specialization</a></H3> <p> @@ -3981,7 +3981,7 @@ struct A { </pre> </div> -<H3><a name="Typemaps_automatic_specialization"></a>11.11.2 Fragments and automatic typemap specialization</H3> +<H3><a name="Typemaps_automatic_specialization">11.11.2 Fragments and automatic typemap specialization</a></H3> <p> @@ -4027,7 +4027,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>11.12 The run-time type checker</H2> +<H2><a name="Typemaps_runtime_type_checker">11.12 The run-time type checker</a></H2> <p> @@ -4053,7 +4053,7 @@ language modules.</li> <li>Modules can be unloaded from the type system.</li> </ul> -<H3><a name="Typemaps_nn45"></a>11.12.1 Implementation</H3> +<H3><a name="Typemaps_nn45">11.12.1 Implementation</a></H3> <p> @@ -4239,7 +4239,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>11.12.2 Usage</H3> +<H3><a name="Typemaps_runtime_type_checker_usage">11.12.2 Usage</a></H3> <p>This section covers how to use these functions from typemaps. To learn how to @@ -4333,7 +4333,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>11.13 Typemaps and overloading</H2> +<H2><a name="Typemaps_overloading">11.13 Typemaps and overloading</a></H2> <p> @@ -4664,7 +4664,7 @@ Subsequent "in" typemaps would then perform more extensive type-checking. </li> </ul> -<H2><a name="Typemaps_nn48"></a>11.14 More about <tt>%apply</tt> and <tt>%clear</tt></H2> +<H2><a name="Typemaps_nn48">11.14 More about <tt>%apply</tt> and <tt>%clear</tt></a></H2> <p> @@ -4750,7 +4750,7 @@ example: </div> -<H2><a name="Typemaps_nn47"></a>11.15 Passing data between typemaps</H2> +<H2><a name="Typemaps_nn47">11.15 Passing data between typemaps</a></H2> <p> @@ -4787,7 +4787,7 @@ sure that the typemaps sharing information have exactly the same types and names </p> -<H2><a name="Typemaps_nn52"></a>11.16 C++ "this" pointer</H2> +<H2><a name="Typemaps_nn52">11.16 C++ "this" pointer</a></H2> <p> @@ -4847,7 +4847,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>11.17 Where to go for more information?</H2> +<H2><a name="Typemaps_nn51">11.17 Where to go for more information?</a></H2> <p> diff --git a/Doc/Manual/Varargs.html b/Doc/Manual/Varargs.html index 360bbaa12..c2f55b019 100644 --- a/Doc/Manual/Varargs.html +++ b/Doc/Manual/Varargs.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Varargs"></a>14 Variable Length Arguments</H1> +<H1><a name="Varargs">14 Variable Length Arguments</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -42,7 +42,7 @@ added in SWIG-1.3.12. Most other wrapper generation tools have wisely chosen to avoid this issue. </p> -<H2><a name="Varargs_nn2"></a>14.1 Introduction</H2> +<H2><a name="Varargs_nn2">14.1 Introduction</a></H2> <p> @@ -139,7 +139,7 @@ List make_list(const char *s, ...) { </pre> </div> -<H2><a name="Varargs_nn3"></a>14.2 The Problem</H2> +<H2><a name="Varargs_nn3">14.2 The Problem</a></H2> <p> @@ -232,7 +232,7 @@ can also support real varargs wrapping (with stack-frame manipulation) if you are willing to get hands dirty. Keep reading. </p> -<H2><a name="Varargs_nn4"></a>14.3 Default varargs support</H2> +<H2><a name="Varargs_nn4">14.3 Default varargs support</a></H2> <p> @@ -301,7 +301,7 @@ Read on for further solutions. </p> -<H2><a name="Varargs_nn5"></a>14.4 Argument replacement using %varargs</H2> +<H2><a name="Varargs_nn5">14.4 Argument replacement using %varargs</a></H2> <p> @@ -412,7 +412,7 @@ mixed argument types such as <tt>printf()</tt>. Providing general purpose wrappers to such functions presents special problems (covered shortly). </p> -<H2><a name="Varargs_nn6"></a>14.5 Varargs and typemaps</H2> +<H2><a name="Varargs_nn6">14.5 Varargs and typemaps</a></H2> <p> @@ -589,7 +589,7 @@ really want to elevate your guru status and increase your job security, continue to the next section. </p> -<H2><a name="Varargs_nn7"></a>14.6 Varargs wrapping with libffi</H2> +<H2><a name="Varargs_nn7">14.6 Varargs wrapping with libffi</a></H2> <p> @@ -841,7 +841,7 @@ provide an argument number for the first extra argument. This can be used to in values. Please consult the chapter on each language module for more details. </p> -<H2><a name="Varargs_nn8"></a>14.7 Wrapping of va_list</H2> +<H2><a name="Varargs_nn8">14.7 Wrapping of va_list</a></H2> <p> @@ -895,7 +895,7 @@ int my_vprintf(const char *fmt, ...) { </pre> </div> -<H2><a name="Varargs_nn9"></a>14.8 C++ Issues</H2> +<H2><a name="Varargs_nn9">14.8 C++ Issues</a></H2> <p> @@ -964,7 +964,7 @@ design or to provide an alternative interface using a helper function than it is fully general wrapper to a varargs C++ member function. </p> -<H2><a name="Varargs_nn10"></a>14.9 Discussion</H2> +<H2><a name="Varargs_nn10">14.9 Discussion</a></H2> <p> diff --git a/Doc/Manual/Warnings.html b/Doc/Manual/Warnings.html index 2336120d3..92ec5000c 100644 --- a/Doc/Manual/Warnings.html +++ b/Doc/Manual/Warnings.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Warnings"></a>15 Warning Messages</H1> +<H1><a name="Warnings">15 Warning Messages</a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -35,7 +35,7 @@ -<H2><a name="Warnings_nn2"></a>15.1 Introduction</H2> +<H2><a name="Warnings_nn2">15.1 Introduction</a></H2> <p> @@ -55,7 +55,7 @@ where the generated wrapper code will probably compile, but it may not work like you expect. </p> -<H2><a name="Warnings_suppression"></a>15.2 Warning message suppression</H2> +<H2><a name="Warnings_suppression">15.2 Warning message suppression</a></H2> <p> @@ -147,7 +147,7 @@ your interface. Ignore the warning messages at your own peril. </p> -<H2><a name="Warnings_nn4"></a>15.3 Enabling extra warnings</H2> +<H2><a name="Warnings_nn4">15.3 Enabling extra warnings</a></H2> <p> @@ -220,7 +220,7 @@ that is, any warnings suppressed or added in <tt>%warnfilter</tt>, <tt>#pragma S or the <tt>-w</tt> option. </p> -<H2><a name="Warnings_nn5"></a>15.4 Issuing a warning message</H2> +<H2><a name="Warnings_nn5">15.4 Issuing a warning message</a></H2> <p> @@ -274,7 +274,7 @@ example.i:24: Warning 901: You are really going to regret this usage of blah * s </pre> </div> -<H2><a name="Warnings_symbolic_symbols"></a>15.5 Symbolic symbols</H2> +<H2><a name="Warnings_symbolic_symbols">15.5 Symbolic symbols</a></H2> <p> @@ -309,7 +309,7 @@ or </pre> </div> -<H2><a name="Warnings_nn6"></a>15.6 Commentary</H2> +<H2><a name="Warnings_nn6">15.6 Commentary</a></H2> <p> @@ -326,7 +326,7 @@ no obvious recovery. There is no mechanism for suppressing error messages. </p> -<H2><a name="Warnings_nn7"></a>15.7 Warnings as errors</H2> +<H2><a name="Warnings_nn7">15.7 Warnings as errors</a></H2> <p> @@ -335,7 +335,7 @@ option. This will cause SWIG to exit with a non successful exit code if a warning is encountered. </p> -<H2><a name="Warnings_nn8"></a>15.8 Message output format</H2> +<H2><a name="Warnings_nn8">15.8 Message output format</a></H2> <p> @@ -354,10 +354,10 @@ $ swig -python -Fmicrosoft example.i example.i(4) : Syntax error in input(1). </pre></div> -<H2><a name="Warnings_nn9"></a>15.9 Warning number reference</H2> +<H2><a name="Warnings_nn9">15.9 Warning number reference</a></H2> -<H3><a name="Warnings_nn10"></a>15.9.1 Deprecated features (100-199)</H3> +<H3><a name="Warnings_nn10">15.9.1 Deprecated features (100-199)</a></H3> <ul> @@ -385,7 +385,7 @@ example.i(4) : Syntax error in input(1). <li>126. The 'nestedworkaround' feature is deprecated. </ul> -<H3><a name="Warnings_nn11"></a>15.9.2 Preprocessor (200-299)</H3> +<H3><a name="Warnings_nn11">15.9.2 Preprocessor (200-299)</a></H3> <ul> @@ -397,7 +397,7 @@ example.i(4) : Syntax error in input(1). <li>206. Unexpected tokens after #<em>directive</em> directive. </ul> -<H3><a name="Warnings_nn12"></a>15.9.3 C/C++ Parser (300-399)</H3> +<H3><a name="Warnings_nn12">15.9.3 C/C++ Parser (300-399)</a></H3> <ul> @@ -474,7 +474,7 @@ example.i(4) : Syntax error in input(1). <li>395. operator delete[] ignored. </ul> -<H3><a name="Warnings_nn13"></a>15.9.4 Types and typemaps (400-499) </H3> +<H3><a name="Warnings_nn13">15.9.4 Types and typemaps (400-499) </a></H3> <ul> @@ -505,7 +505,7 @@ example.i(4) : Syntax error in input(1). -<H3><a name="Warnings_nn14"></a>15.9.5 Code generation (500-599)</H3> +<H3><a name="Warnings_nn14">15.9.5 Code generation (500-599)</a></H3> <ul> @@ -534,7 +534,7 @@ example.i(4) : Syntax error in input(1). <li>523. Use of an illegal destructor name '<em>name</em>' in %extend is deprecated, the destructor name should be '<em>name</em>'. </ul> -<H3><a name="Warnings_nn15"></a>15.9.6 Language module specific (700-899) </H3> +<H3><a name="Warnings_nn15">15.9.6 Language module specific (700-899) </a></H3> <ul> @@ -585,14 +585,14 @@ example.i(4) : Syntax error in input(1). <li>871. Unrecognized pragma <em>pragma</em>. (Php). </ul> -<H3><a name="Warnings_nn16"></a>15.9.7 User defined (900-999)</H3> +<H3><a name="Warnings_nn16">15.9.7 User defined (900-999)</a></H3> <p> These numbers can be used by your own application. </p> -<H2><a name="Warnings_nn17"></a>15.10 History</H2> +<H2><a name="Warnings_nn17">15.10 History</a></H2> <p> diff --git a/Doc/Manual/Windows.html b/Doc/Manual/Windows.html index d85737e52..fecdf48ed 100644 --- a/Doc/Manual/Windows.html +++ b/Doc/Manual/Windows.html @@ -6,7 +6,7 @@ </head> <body bgcolor="#ffffff"> -<H1><a name="Windows"></a>3 Getting started on Windows </H1> +<H1><a name="Windows">3 Getting started on Windows </a></H1> <!-- INDEX --> <div class="sectiontoc"> <ul> @@ -52,7 +52,7 @@ Usage within the Unix like environments MinGW and Cygwin is also detailed. </p> -<H2><a name="Windows_installation"></a>3.1 Installation on Windows</H2> +<H2><a name="Windows_installation">3.1 Installation on Windows</a></H2> <p> @@ -63,7 +63,7 @@ SWIG does not come with the usual Windows type installation program, however it <li>Set environment variables as described in the <a href="#Windows_examples">SWIG Windows Examples</a> section in order to run examples using Visual C++. </ul> -<H3><a name="Windows_executable"></a>3.1.1 Windows Executable</H3> +<H3><a name="Windows_executable">3.1.1 Windows Executable</a></H3> <p> @@ -72,7 +72,7 @@ If you want to build your own swig.exe have a look at <a href="#Windows_swig_exe </p> -<H2><a name="Windows_examples"></a>3.2 SWIG Windows Examples</H2> +<H2><a name="Windows_examples">3.2 SWIG Windows Examples</a></H2> <p> @@ -87,7 +87,7 @@ Alternatively run the <a href="#Windows_examples_cygwin">examples using Cygwin</ <p> More information on each of the examples is available with the examples distributed with SWIG (Examples/index.html). -<H3><a name="Windows_visual_studio"></a>3.2.1 Instructions for using the Examples with Visual Studio</H3> +<H3><a name="Windows_visual_studio">3.2.1 Instructions for using the Examples with Visual Studio</a></H3> <p> @@ -105,7 +105,7 @@ If you don't want to use environment variables then change all occurrences of th If you are interested in how the project files are set up there is explanatory information in some of the language module's documentation. </p> -<H4><a name="Windows_csharp"></a>3.2.1.1 C#</H4> +<H4><a name="Windows_csharp">3.2.1.1 C#</a></H4> <p> @@ -115,7 +115,7 @@ The accompanying C# and C++ project files are automatically used by the solution </p> -<H4><a name="Windows_java"></a>3.2.1.2 Java</H4> +<H4><a name="Windows_java">3.2.1.2 Java</a></H4> <p> @@ -129,7 +129,7 @@ JAVA_BIN: D:\jdk1.3\bin<br> </p> -<H4><a name="Windows_perl"></a>3.2.1.3 Perl</H4> +<H4><a name="Windows_perl">3.2.1.3 Perl</a></H4> <p> @@ -143,7 +143,7 @@ PERL5_LIB: D:\nsPerl5.004_04\lib\CORE\perl.lib<br> </p> -<H4><a name="Windows_python"></a>3.2.1.4 Python</H4> +<H4><a name="Windows_python">3.2.1.4 Python</a></H4> <p> @@ -157,7 +157,7 @@ PYTHON_LIB: D:\python21\libs\python21.lib<br> </p> -<H4><a name="Windows_tcl"></a>3.2.1.5 TCL</H4> +<H4><a name="Windows_tcl">3.2.1.5 TCL</a></H4> <p> @@ -171,7 +171,7 @@ TCL_LIB: D:\tcl\lib\tcl83.lib<br> </p> -<H4><a name="Windows_r"></a>3.2.1.6 R</H4> +<H4><a name="Windows_r">3.2.1.6 R</a></H4> <p> @@ -185,7 +185,7 @@ R_LIB: C:\Program Files\R\R-2.5.1\bin\Rdll.lib<br> </p> -<H4><a name="Windows_ruby"></a>3.2.1.7 Ruby</H4> +<H4><a name="Windows_ruby">3.2.1.7 Ruby</a></H4> <p> @@ -199,21 +199,21 @@ RUBY_LIB: D:\ruby\lib\mswin32-ruby16.lib<br> </p> -<H3><a name="Windows_other_compilers"></a>3.2.2 Instructions for using the Examples with other compilers</H3> +<H3><a name="Windows_other_compilers">3.2.2 Instructions for using the Examples with other compilers</a></H3> <p> If you do not have access to Visual C++ you will have to set up project files / Makefiles for your chosen compiler. There is a section in each of the language modules detailing what needs setting up using Visual C++ which may be of some guidance. Alternatively you may want to use Cygwin as described in the following section. </p> -<H2><a name="Windows_cygwin_mingw"></a>3.3 SWIG on Cygwin and MinGW</H2> +<H2><a name="Windows_cygwin_mingw">3.3 SWIG on Cygwin and MinGW</a></H2> <p> SWIG can also be compiled and run using <a href="http://www.cygwin.com">Cygwin</a> or <a href="http://www.mingw.org">MinGW</a> which provides a Unix like front end to Windows and comes free with gcc, an ANSI C/C++ compiler. However, this is not a recommended approach as the prebuilt executable is supplied. </p> -<H3><a name="Windows_swig_exe"></a>3.3.1 Building swig.exe on Windows</H3> +<H3><a name="Windows_swig_exe">3.3.1 Building swig.exe on Windows</a></H3> <p> @@ -223,7 +223,7 @@ This information is provided for those that want to modify the SWIG source code Normally this is not needed, so most people will want to ignore this section. </p> -<H4><a name="Windows_mingw_msys"></a>3.3.1.1 Building swig.exe using MinGW and MSYS</H4> +<H4><a name="Windows_mingw_msys">3.3.1.1 Building swig.exe using MinGW and MSYS</a></H4> <p> @@ -341,7 +341,7 @@ make </ol> -<H4><a name="Windows_cygwin"></a>3.3.1.2 Building swig.exe using Cygwin</H4> +<H4><a name="Windows_cygwin">3.3.1.2 Building swig.exe using Cygwin</a></H4> <p> @@ -352,7 +352,7 @@ Note that the Cygwin environment will also allow one to regenerate the autotool These files are generated using the <tt>autogen.sh</tt> script and will only need regenerating in circumstances such as changing the build system. </p> -<H4><a name="Windows_building_alternatives"></a>3.3.1.3 Building swig.exe alternatives</H4> +<H4><a name="Windows_building_alternatives">3.3.1.3 Building swig.exe alternatives</a></H4> <p> @@ -362,7 +362,7 @@ file in order to build swig.exe from the Visual C++ IDE. </p> -<H3><a name="Windows_examples_cygwin"></a>3.3.2 Running the examples on Windows using Cygwin</H3> +<H3><a name="Windows_examples_cygwin">3.3.2 Running the examples on Windows using Cygwin</a></H3> <p> @@ -371,7 +371,7 @@ The modules which are known to work are Python, Tcl, Perl, Ruby, Java and C#. Follow the Unix instructions in the README file in the SWIG root directory to build the examples. </p> -<H2><a name="Windows_interface_file"></a>3.4 Microsoft extensions and other Windows quirks</H2> +<H2><a name="Windows_interface_file">3.4 Microsoft extensions and other Windows quirks</a></H2> <p> |