diff --git a/SWIG/Doc/Manual/CSharp.html b/SWIG/Doc/Manual/CSharp.html index bac6f7417..32132dbab 100644 --- a/SWIG/Doc/Manual/CSharp.html +++ b/SWIG/Doc/Manual/CSharp.html @@ -137,7 +137,7 @@ Visual Studio .NET 2003 solution and project files are available for compiling w If your SWIG installation went well on a Unix environment and your C# compiler was detected, you should be able to type make in each example directory, then ilrun runme (Portable.NET C# compiler) or mono runme (Mono C# compiler) to run the examples. Windows users can also get the examples working using a -Cygwin or MinGW environment for automatic configuration of the example makefiles. +Cygwin or MinGW environment for automatic configuration of the example makefiles. Any one of the three C# compilers (Portable.NET, Mono or Microsoft) can be detected from within a Cygwin or Mingw environment if installed in your path. diff --git a/SWIG/Doc/Manual/Makefile b/SWIG/Doc/Manual/Makefile index 3deec7519..7517ac1a5 100644 --- a/SWIG/Doc/Manual/Makefile +++ b/SWIG/Doc/Manual/Makefile @@ -53,3 +53,6 @@ test: grep "href=\".*\.html\"" Sections.html all=`sed '/^#/d' chapters`; for a in $$all; do grep -l "href=\".*\.html\"" $$a; done; +validate: + all=`sed '/^#/d' chapters`; for a in $$all; do /home/william/builds/wdg_validate/validate --emacs $$a; done; + diff --git a/SWIG/Doc/Manual/Modula3.html b/SWIG/Doc/Manual/Modula3.html index 81afe4851..40ef31248 100644 --- a/SWIG/Doc/Manual/Modula3.html +++ b/SWIG/Doc/Manual/Modula3.html @@ -419,8 +419,8 @@ Is it possible to sub-class C++ classes with Modula-3 code? This issue is addressed by directors, a feature that was experimentally added to some Language modules like -Java and -Python. +Java and +Python.
  • How to manage storage with the garbage collector of Modula-3? diff --git a/SWIG/Doc/Manual/Perl5.html b/SWIG/Doc/Manual/Perl5.html index 5e808d7ab..c25dabdc4 100644 --- a/SWIG/Doc/Manual/Perl5.html +++ b/SWIG/Doc/Manual/Perl5.html @@ -551,7 +551,7 @@ source has a list of macros that are known to conflict with either standard head other headers. But if you get macro type conflicts from other macros not included in Lib/perl5/noembed.h while compiling the wrapper, you will have to find the macro that conflicts and add an #undef into the .i file. Please report -any conflicting macros you find to swig@cs.uchicago.edu. +any conflicting macros you find to swig mailing list.

    22.2.7 Compiling for 64-bit platforms

    diff --git a/SWIG/Doc/Manual/Preface.html b/SWIG/Doc/Manual/Preface.html index d54ced852..a925853c5 100644 --- a/SWIG/Doc/Manual/Preface.html +++ b/SWIG/Doc/Manual/Preface.html @@ -196,8 +196,8 @@ port. Although every attempt has been made to make SWIG bug-free, we are also trying to make feature improvements that may introduce bugs. To report a bug, either send mail to the SWIG developer -list at swig-dev@cs.uchicago.edu or report a bug -at http://www.swig.org. In your report, be as specific as +list at the swig-dev mailing list or report a bug +at the SWIG bug tracker. In your report, be as specific as possible, including (if applicable), error messages, tracebacks (if a core dump occurred), corresponding portions of the SWIG interface file used, and any important pieces of the SWIG generated wrapper code. We diff --git a/SWIG/Doc/Manual/SWIG.html b/SWIG/Doc/Manual/SWIG.html index 619cf1ce8..fe41746af 100644 --- a/SWIG/Doc/Manual/SWIG.html +++ b/SWIG/Doc/Manual/SWIG.html @@ -2617,7 +2617,8 @@ In the process of building an interface, SWIG may encounter syntax errors or other problems. The best way to deal with this is to simply copy the offending code into a separate interface file and edit it. However, the SWIG developers have worked very hard to improve the SWIG parser--you should report parsing errors -to swig-dev@cs.uchicago.edu or to the SWIG bug tracker on www.swig.org. +to the swig-dev mailing list or to the +SWIG bug tracker.

    5.7.2 The SWIG interface file

    diff --git a/SWIG/Doc/Manual/SWIGPlus.html b/SWIG/Doc/Manual/SWIGPlus.html index 3751f0534..e537feb65 100644 --- a/SWIG/Doc/Manual/SWIGPlus.html +++ b/SWIG/Doc/Manual/SWIGPlus.html @@ -1506,8 +1506,8 @@ rule for 'int'). This error means that the target language module supports overloading, but for some reason there is no type-checking rule that can be used to generate a working dispatch function. The resulting behavior is then -undefined. You should report this as a bug to -swig-dev@cs.uchicago.edu. +undefined. You should report this as a bug to the +SWIG bug tracking database.

    If you get an error message such as the following, @@ -1661,7 +1661,7 @@ members (of all classes): Note: the *:: syntax is non-standard C++, but the '*' is meant to be a wildcard that matches any class name (we couldn't think of a better alternative so if you have a better idea, send email to -swig-dev@cs.uchicago.edu). +the swig-dev mailing list.

    Although this discussion has primarily focused on %rename all of the same rules diff --git a/SWIG/Doc/Manual/Typemaps.html b/SWIG/Doc/Manual/Typemaps.html index 5dc114717..3fa4c1bfc 100644 --- a/SWIG/Doc/Manual/Typemaps.html +++ b/SWIG/Doc/Manual/Typemaps.html @@ -1,3 +1,4 @@ + Typemaps diff --git a/SWIG/Doc/Manual/Windows.html b/SWIG/Doc/Manual/Windows.html index 814eb5e04..fbfce26a1 100644 --- a/SWIG/Doc/Manual/Windows.html +++ b/SWIG/Doc/Manual/Windows.html @@ -160,7 +160,7 @@ If you do not have access to Visual C++ you will have to set up project files /

    3.3 SWIG on Cygwin and MinGW

    -SWIG can also be compiled and run using Cygwin or MinGW which provides a Unix like front end to Windows and comes free with gcc, an ANSI C/C++ compiler. However, this is not a recommended approach as the prebuilt executable is supplied. +SWIG can also be compiled and run using Cygwin or MinGW which provides a Unix like front end to Windows and comes free with gcc, an ANSI C/C++ compiler. However, this is not a recommended approach as the prebuilt executable is supplied.

    3.3.1 Building swig.exe on Windows