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

Correct links in html documentation using new version of makechap.py

Browse source 
Corrects position of heading text within A and H1, H2, ... elements.
This commit is contained in:
William S Fulton 2015-12-22 07:54:57 +00:00
commit 8288ac15a0
41 changed files with 1262 additions and 1262 deletions
Download patch file Download diff file Expand all files Collapse all files

40
Doc/Manual/Library.html
View file

@ -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 &amp;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>