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

Update html chapter numbering for added Doxygen chapter

Browse source
This commit is contained in:
William S Fulton 2018-05-24 18:36:20 +01:00
commit 4cdca98709
31 changed files with 1062 additions and 1039 deletions
Download patch file Download diff file Expand all files Collapse all files

62
Doc/Manual/Ocaml.html
View file

@ -7,7 +7,7 @@
</head>
<body bgcolor="#ffffff">
<H1><a name="Ocaml">32 SWIG and Ocaml</a></H1>
<H1><a name="Ocaml">33 SWIG and Ocaml</a></H1>
<!-- INDEX -->
<div class="sectiontoc">
<ul>
@ -84,7 +84,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">32.1 Preliminaries</a></H2>
<H2><a name="Ocaml_nn2">33.1 Preliminaries</a></H2>
<p>
@ -102,7 +102,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">32.1.1 Running SWIG</a></H3>
<H3><a name="Ocaml_nn3">33.1.1 Running SWIG</a></H3>
<p>
@ -125,7 +125,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">32.1.2 Compiling the code</a></H3>
<H3><a name="Ocaml_nn4">33.1.2 Compiling the code</a></H3>
<p>
@ -162,7 +162,7 @@ in C++ mode, you must:</p>
</pre>
</div>
<H3><a name="Ocaml_nn5">32.1.3 The camlp4 module</a></H3>
<H3><a name="Ocaml_nn5">33.1.3 The camlp4 module</a></H3>
<p>
@ -238,7 +238,7 @@ let b = C_string (getenv "PATH")
</td></tr>
</table>
<H3><a name="Ocaml_nn6">32.1.4 Using your module</a></H3>
<H3><a name="Ocaml_nn6">33.1.4 Using your module</a></H3>
<p>
@ -252,7 +252,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">32.1.5 Compilation problems and compiling with C++</a></H3>
<H3><a name="Ocaml_nn7">33.1.5 Compilation problems and compiling with C++</a></H3>
<p>
@ -263,7 +263,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">32.2 The low-level Ocaml/C interface</a></H2>
<H2><a name="Ocaml_nn8">33.2 The low-level Ocaml/C interface</a></H2>
<p>
@ -363,7 +363,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">32.2.1 The generated module</a></H3>
<H3><a name="Ocaml_nn9">33.2.1 The generated module</a></H3>
<p>
@ -397,7 +397,7 @@ it describes the output SWIG will generate for class definitions.
</td></tr>
</table>
<H3><a name="Ocaml_nn10">32.2.2 Enums</a></H3>
<H3><a name="Ocaml_nn10">33.2.2 Enums</a></H3>
<p>
@ -460,7 +460,7 @@ val x : Enum_test.c_obj = C_enum `a
</pre>
</div>
<H4><a name="Ocaml_nn11">32.2.2.1 Enum typing in Ocaml</a></H4>
<H4><a name="Ocaml_nn11">33.2.2.1 Enum typing in Ocaml</a></H4>
<p>
@ -473,10 +473,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">32.2.3 Arrays</a></H3>
<H3><a name="Ocaml_nn12">33.2.3 Arrays</a></H3>
<H4><a name="Ocaml_nn13">32.2.3.1 Simple types of bounded arrays</a></H4>
<H4><a name="Ocaml_nn13">33.2.3.1 Simple types of bounded arrays</a></H4>
<p>
@ -497,7 +497,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">32.2.3.2 Complex and unbounded arrays</a></H4>
<H4><a name="Ocaml_nn14">33.2.3.2 Complex and unbounded arrays</a></H4>
<p>
@ -510,7 +510,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">32.2.3.3 Using an object</a></H4>
<H4><a name="Ocaml_nn15">33.2.3.3 Using an object</a></H4>
<p>
@ -524,7 +524,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">32.2.3.4 Example typemap for a function taking float * and int</a></H4>
<H4><a name="Ocaml_nn16">33.2.3.4 Example typemap for a function taking float * and int</a></H4>
<p>
@ -575,7 +575,7 @@ void printfloats( float *tab, int len );
</pre></td></tr></table>
<H3><a name="Ocaml_nn17">32.2.4 C++ Classes</a></H3>
<H3><a name="Ocaml_nn17">33.2.4 C++ Classes</a></H3>
<p>
@ -618,7 +618,7 @@ the underlying pointer, so using create_[x]_from_ptr alters the
returned value for the same object.
</p>
<H4><a name="Ocaml_nn18">32.2.4.1 STL vector and string Example</a></H4>
<H4><a name="Ocaml_nn18">33.2.4.1 STL vector and string Example</a></H4>
<p>
@ -698,7 +698,7 @@ baz
#
</pre></div>
<H4><a name="Ocaml_nn19">32.2.4.2 C++ Class Example</a></H4>
<H4><a name="Ocaml_nn19">33.2.4.2 C++ Class Example</a></H4>
<p>
@ -728,7 +728,7 @@ public:
};
</pre></td></tr></table>
<H4><a name="Ocaml_nn20">32.2.4.3 Compiling the example</a></H4>
<H4><a name="Ocaml_nn20">33.2.4.3 Compiling the example</a></H4>
<div class="code"><pre>
@ -746,7 +746,7 @@ bash-2.05a$ ocamlmktop -custom swig.cmo -I `camlp4 -where` \
-L$QTPATH/lib -cclib -lqt
</pre></div>
<H4><a name="Ocaml_nn21">32.2.4.4 Sample Session</a></H4>
<H4><a name="Ocaml_nn21">33.2.4.4 Sample Session</a></H4>
<div class="code"><pre>
@ -773,10 +773,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">32.2.5 Director Classes</a></H3>
<H3><a name="Ocaml_nn22">33.2.5 Director Classes</a></H3>
<H4><a name="Ocaml_nn23">32.2.5.1 Director Introduction</a></H4>
<H4><a name="Ocaml_nn23">33.2.5.1 Director Introduction</a></H4>
<p>
@ -803,7 +803,7 @@ class foo {
};
</pre></div>
<H4><a name="Ocaml_nn24">32.2.5.2 Overriding Methods in Ocaml</a></H4>
<H4><a name="Ocaml_nn24">33.2.5.2 Overriding Methods in Ocaml</a></H4>
<p>
@ -831,7 +831,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">32.2.5.3 Director Usage Example</a></H4>
<H4><a name="Ocaml_nn25">33.2.5.3 Director Usage Example</a></H4>
<table border="1" bgcolor="#dddddd" summary="Director usage example">
@ -890,7 +890,7 @@ in a more effortless style in ocaml, while leaving the "engine" part of the
program in C++.
</p>
<H4><a name="Ocaml_nn26">32.2.5.4 Creating director objects</a></H4>
<H4><a name="Ocaml_nn26">33.2.5.4 Creating director objects</a></H4>
<p>
@ -931,7 +931,7 @@ object from causing a core dump, as long as the object is destroyed
properly.
</p>
<H4><a name="Ocaml_nn27">32.2.5.5 Typemaps for directors, directorin, directorout, directorargout</a></H4>
<H4><a name="Ocaml_nn27">33.2.5.5 Typemaps for directors, directorin, directorout, directorargout</a></H4>
<p>
@ -942,7 +942,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">32.2.5.6 typemap</a></H4>
<H4><a name="Ocaml_nn28">33.2.5.6 typemap</a></H4>
<p>
@ -953,7 +953,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">32.2.5.7 directorout typemap</a></H4>
<H4><a name="Ocaml_nn29">33.2.5.7 directorout typemap</a></H4>
<p>
@ -964,7 +964,7 @@ for the same type, except when there are special requirements for object
ownership, etc.
</p>
<H4><a name="Ocaml_nn30">32.2.5.8 directorargout typemap</a></H4>
<H4><a name="Ocaml_nn30">33.2.5.8 directorargout typemap</a></H4>
<p>
@ -981,7 +981,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">32.2.6 Exceptions</a></H3>
<H3><a name="Ocaml_nn31">33.2.6 Exceptions</a></H3>
<p>