summaryrefslogtreecommitdiff
path: root/Doc/Manual/Introduction.html
diff options
context:
space:
mode:
authorWilliam S Fulton <wsf@fultondesigns.co.uk>2015-12-22 07:54:57 +0000
committerWilliam S Fulton <wsf@fultondesigns.co.uk>2015-12-30 22:22:32 +0000
commit8288ac15a030b851c18dee2cf5e4e5769f0bc024 (patch)
treecd16459ad1cbc3b94dd5a3869dfbab94a70f68d1 /Doc/Manual/Introduction.html
parentabe42bbb162396b4440c096b33b2bd98514af84e (diff)
downloadswig-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.
Diffstat (limited to 'Doc/Manual/Introduction.html')
-rw-r--r--Doc/Manual/Introduction.html28
1 files changed, 14 insertions, 14 deletions
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 &gt;
</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>