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

Better linkchecker configuration for checking html links. Fix broken links and update redirected links.

Browse source 
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@12381 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
William S Fulton 2011-01-08 23:17:23 +00:00
commit 162ced78f4
13 changed files with 26 additions and 23 deletions
Download patch file Download diff file Expand all files Collapse all files

2
Doc/Manual/CSharp.html
View file

@ -57,7 +57,7 @@ PInvoke is part of the ECMA/ISO C# specification.
It is also better suited for robust production environments due to the Managed C++ flaw called the It is also better suited for robust production environments due to the Managed C++ flaw called the
<a href="http://msdn.microsoft.com/en-us/library/aa290048(VS.71).aspx">Mixed DLL Loading Problem</a>. <a href="http://msdn.microsoft.com/en-us/library/aa290048(VS.71).aspx">Mixed DLL Loading Problem</a>.
SWIG C# works equally well on non-Microsoft operating systems such as Linux, Solaris and Apple Mac using SWIG C# works equally well on non-Microsoft operating systems such as Linux, Solaris and Apple Mac using
<a href="http://www.mono-project.com/">Mono</a> and <a href="http://www.dotgnu.org/pnet.html">Portable.NET</a>. <a href="http://www.mono-project.com/Main_Page">Mono</a> and <a href="http://www.dotgnu.org/pnet.html">Portable.NET</a>.
</p> </p>
<p> <p>

2
Doc/Manual/Contents.html
View file

@ -5,7 +5,7 @@
<TITLE>SWIG Users Manual</TITLE> <TITLE>SWIG Users Manual</TITLE>
</HEAD> </HEAD>
<BODY BGCOLOR="#ffffff"> <BODY BGCOLOR="#ffffff">
<H1>SWIG Users Manual</H1> <H1><a name="Contents"></a>SWIG Users Manual</H1>
<p> <p>

2
Doc/Manual/Guile.html
View file

@ -429,7 +429,7 @@ upper half of the CAR is read from this struct.
To get the pointer represented by a smob, the wrapper code calls the To get the pointer represented by a smob, the wrapper code calls the
function <code>SWIG_ConvertPtr()</code>, passing a pointer to a struct function <code>SWIG_ConvertPtr()</code>, passing a pointer to a struct
representing the expected pointer type. See also representing the expected pointer type. See also
<a href="Typemaps.html#runtime_type_checker">The run-time type checker</a>. <a href="Typemaps.html#Typemaps_runtime_type_checker">The run-time type checker</a>.
If the Scheme object passed was not a SWIG smob representing a compatible If the Scheme object passed was not a SWIG smob representing a compatible
pointer, a <code>wrong-type-arg</code> exception is raised. pointer, a <code>wrong-type-arg</code> exception is raised.

6
Doc/Manual/Introduction.html
View file

@ -372,9 +372,9 @@ Microsoft Visual Studio.
<p> <p>
If you are using the GNU Autotools If you are using the GNU Autotools
(<a href="http://www.gnu.org/software/autoconf">Autoconf</a>/ (<a href="http://www.gnu.org/software/autoconf/">Autoconf</a>/
<a href="http://www.gnu.org/software/automake">Automake</a>/ <a href="http://www.gnu.org/software/automake/">Automake</a>/
<a href="http://www.gnu.org/software/libtool">Libtool</a>) <a href="http://www.gnu.org/software/libtool/">Libtool</a>)
to configure SWIG use in your project, the SWIG Autoconf macros can be used. to configure SWIG use in your project, the SWIG Autoconf macros can be used.
The primary macro is <tt>ax_pkg_swig</tt>, see The primary macro is <tt>ax_pkg_swig</tt>, see
<a href="http://www.gnu.org/software/autoconf-archive/ax_pkg_swig.html#ax_pkg_swig">http://www.gnu.org/software/autoconf-archive/ax_pkg_swig.html#ax_pkg_swig</a>. <a href="http://www.gnu.org/software/autoconf-archive/ax_pkg_swig.html#ax_pkg_swig">http://www.gnu.org/software/autoconf-archive/ax_pkg_swig.html#ax_pkg_swig</a>.

2
Doc/Manual/Java.html
View file

@ -2745,7 +2745,7 @@ Call the <tt>System.runFinalizersOnExit(true)</tt> or <tt>Runtime.getRuntime().r
This method is inherently unsafe. It may result in finalizers being called on live objects while other threads are concurrently manipulating those objects, resulting in erratic behavior or deadlock. This method is inherently unsafe. It may result in finalizers being called on live objects while other threads are concurrently manipulating those objects, resulting in erratic behavior or deadlock.
</i></div> </i></div>
<p>In many cases you will be lucky and find that it works, but it is not to be advocated. <p>In many cases you will be lucky and find that it works, but it is not to be advocated.
Have a look at <a href="http://java.sun.com">Sun's Java web site</a> and search for <tt>runFinalizersOnExit</tt>. Have a look at <a href="http://www.oracle.com/technetwork/java/index.html">Java web site</a> and search for <tt>runFinalizersOnExit</tt>.
</p></li> </p></li>
<li><p> <li><p>

7
Doc/Manual/Makefile
View file

@ -69,7 +69,10 @@ test:
validate: validate:
all=`sed '/^#/d' chapters`; for a in $$all; do validate --emacs $$a; done; all=`sed '/^#/d' chapters`; for a in $$all; do validate --emacs $$a; done;
# Link checking using linkchecker (can take a while - 30 mins) # Link checking using linkchecker
linkchecker: linkchecker:
linkchecker --anchors Contents.html @echo -----------------------------------------------------------------------
@echo Note linkchecker versions prior to 6.1 do not work properly wrt anchors
@echo -----------------------------------------------------------------------
linkchecker --config=./linkchecker.config index.html

13
Doc/Manual/Modula3.html
View file

@ -142,7 +142,7 @@ Modula-3 has integrated support for calling C functions.
This is also extensively used by the standard Modula-3 libraries This is also extensively used by the standard Modula-3 libraries
to call OS functions. to call OS functions.
The Modula-3 part of SWIG and the corresponding SWIG library The Modula-3 part of SWIG and the corresponding SWIG library
<a href="../../Lib/modula3/modula3.swg"><tt>modula3.swg</tt></a> modula3.swg
contain code that uses these features. contain code that uses these features.
Because of the built-in support there is no need Because of the built-in support there is no need
for calling the SWIG kernel to generate wrappers written in C. for calling the SWIG kernel to generate wrappers written in C.
@ -394,8 +394,7 @@ so I'm not sure if this is possible or sensible, yet.
There are different Modula-3 compilers around: There are different Modula-3 compilers around:
cm3, pm3, ezm3, Klagenfurth Modula-3, Cambridge Modula-3. cm3, pm3, ezm3, Klagenfurth Modula-3, Cambridge Modula-3.
SWIG itself does not contain compiler specific code SWIG itself does not contain compiler specific code
but the library file but the modula3.swg library file
<a href="../../Lib/modula3/modula3.swg"><tt>modula3.swg</tt></a>
may do so. may do so.
For testing examples I use Critical Mass cm3. For testing examples I use Critical Mass cm3.
</p> </p>
@ -499,9 +498,7 @@ or for a return value.
A further typemap may specify A further typemap may specify
the direction that is used for certain parameters. the direction that is used for certain parameters.
I have chosen this separation I have chosen this separation
in order to be able to write general typemaps for the typemap library in order to be able to write general typemaps for the modula3.swg typemap library.
<a href="../../Lib/modula3/modula3.swg"><tt>modula3.swg</tt></a>
.
In the library code the final usage of the type is not known. In the library code the final usage of the type is not known.
Using separate typemaps for each possible use Using separate typemaps for each possible use
allows appropriate definitions for each case. allows appropriate definitions for each case.
@ -782,9 +779,7 @@ Unqualified import is not supported.
<p> <p>
It is cumbersome to add this typemap to each piece of Modula-3 code. It is cumbersome to add this typemap to each piece of Modula-3 code.
It is especially useful when writing general typemaps It is especially useful when writing general typemaps
for the typemap library for the modula3.swg typemap library.
<a href="../../Lib/modula3/modula3.swg"><tt>modula3.swg</tt></a>
.
For a monolithic module you might be better off For a monolithic module you might be better off
if you add the imports directly: if you add the imports directly:
</p> </p>

2
Doc/Manual/Ocaml.html
View file

@ -93,7 +93,7 @@ examples and test-suite which come with SWIG. You can do this by running
The Ocaml module has been tested using the system's dynamic linking (the The Ocaml module has been tested using the system's dynamic linking (the
usual -lxxx against libxxx.so, as well as with Gerd Stolpmann's usual -lxxx against libxxx.so, as well as with Gerd Stolpmann's
<a <a
href="http://www.ocaml-programming.de/packages/documentation/dl/">Dl package href="http://download.camlcity.org/download/">Dl package
</a>. The ocaml_dynamic and ocaml_dynamic_cpp targets in the </a>. The ocaml_dynamic and ocaml_dynamic_cpp targets in the
file Examples/Makefile illustrate how to compile and link SWIG modules that 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. will be loaded dynamically. This has only been tested on Linux so far.

2
Doc/Manual/Octave.html
View file

@ -46,7 +46,7 @@
<p> <p>
Octave is a high-level language intended for numerical programming that is mostly compatible with MATLAB. Octave is a high-level language intended for numerical programming that is mostly compatible with MATLAB.
More information can be found at <a href="http://www.octave.org">www.octave.org</a>. More information can be found at <a href="http://www.gnu.org/software/octave/">Octave web site</a>.
</p> </p>
<p> <p>

2
Doc/Manual/Python.html
View file

@ -262,7 +262,7 @@ how you might go about compiling and using the generated files.
<p> <p>
The preferred approach to building an extension module for python is to compile it with The preferred approach to building an extension module for python is to compile it with
distutils, which comes with all recent versions of python distutils, which comes with all recent versions of python
(<a href="http://docs.python.org/dist/dist.html">Distutils Docs</a>). (<a href="http://docs.python.org/distutils/index.html">Distutils Docs</a>).
</p> </p>
<p> <p>

2
Doc/Manual/Sections.html
View file

@ -43,7 +43,7 @@ Last update : SWIG-2.0.2 (in progress)
<li><a href="Lisp.html#Lisp">Common Lisp support</a></li> <li><a href="Lisp.html#Lisp">Common Lisp support</a></li>
<li><a href="Lua.html#Lua">Lua support</a></li> <li><a href="Lua.html#Lua">Lua support</a></li>
<li><a href="Modula3.html#Modula3">Modula3 support</a></li> <li><a href="Modula3.html#Modula3">Modula3 support</a></li>
<li><a href="Mzscheme.html#MzScheme">MzScheme support</a></li> <li><a href="Mzscheme.html#Mzscheme">MzScheme support</a></li>
<li><a href="Ocaml.html#Ocaml">Ocaml support</a></li> <li><a href="Ocaml.html#Ocaml">Ocaml support</a></li>
<li><a href="Octave.html#Octave">Octave support</a></li> <li><a href="Octave.html#Octave">Octave support</a></li>
<li><a href="Perl5.html#Perl5">Perl5 support</a></li> <li><a href="Perl5.html#Perl5">Perl5 support</a></li>

5
Doc/Manual/linkchecker.config Normal file
View file

@ -0,0 +1,5 @@
[checking]
anchors=1
[filtering]
ignorewarnings=http-robots-denied

2
Doc/Manual/maketoc.py
View file

@ -12,7 +12,7 @@ print >>f, """
<TITLE>SWIG Users Manual</TITLE> <TITLE>SWIG Users Manual</TITLE>
</HEAD> </HEAD>
<BODY BGCOLOR="#ffffff"> <BODY BGCOLOR="#ffffff">
<H1>SWIG Users Manual</H1> <H1><a name="Contents"></a>SWIG Users Manual</H1>
<p> <p>
""" """