Correct links in html documentation using new version of makechap.py
Corrects position of heading text within A and H1, H2, ... elements.
This commit is contained in:
parent
abe42bbb16
commit
8288ac15a0
41 changed files with 1262 additions and 1262 deletions
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue