To activate the D module, pass the -d option to SWIG at the command line. The same standard command line switches as with any other language module are available, plus the following D specific ones:
+To activate the D module, pass the -d option to SWIG at the command line. The same standard command line options as with any other language module are available, plus the following D specific ones:
By default, SWIG generates two D modules: the proxy module, named like the source module (either specified via the %module directive or via the module command line switch), which contains all the proxy classes, functions, enums, etc., and the intermediary module (named like the proxy module, but suffixed with _im), which contains all the extern(C) function declarations and other private parts only used internally by the proxy module.
-If the split proxy mode is enabled by passing this switch at the command line, all proxy classes and enums are emitted to their own D module instead. The main proxy module only contains free functions and constants in this case.
+By default, SWIG generates two D modules: the proxy module, named like the source module (either specified via the %module directive or via the module command line option), which contains all the proxy classes, functions, enums, etc., and the intermediary module (named like the proxy module, but suffixed with _im), which contains all the extern(C) function declarations and other private parts only used internally by the proxy module.
+If the split proxy mode is enabled by passing this option at the command line, all proxy classes and enums are emitted to their own D module instead. The main proxy module only contains free functions and constants in this case.
The code SWIG generates to dynamically load the C/C++ wrapper layer looks for a library called $module_wrap by default. With this switch, you can override the name of the file the wrapper code loads at runtime (the lib prefix and the suffix for shared libraries are appended automatically, depending on the OS).
+The code SWIG generates to dynamically load the C/C++ wrapper layer looks for a library called $module_wrap by default. With this option, you can override the name of the file the wrapper code loads at runtime (the lib prefix and the suffix for shared libraries are appended automatically, depending on the OS).
This might especially be useful if you want to invoke SWIG several times on separate modules, but compile the resulting code into a single shared library.
Doxygen comments translation is disabled by default and needs to be explicitly -enabled using the command line -doxygen switch for the languages that +enabled using the command line -doxygen option for the languages that do support it (currently Java and Python).
@@ -1639,12 +1639,12 @@ TO BE ADDED.-When running SWIG with command line switch -doxygen, it may happen +When running SWIG with command line option -doxygen, it may happen that SWIG will fail to parse the code, which is valid C++ code and -is parsed without problems without the switch. The problem is, -that Doxygen comments are not tokens (C/C++ compiler actually never +is parsed without problems without the option. The problem is, +that Doxygen comments are not tokens (the C/C++ compiler actually never sees them) and that they can appear anywhere in the code. That's why it is -practically impossible to handle all corner cases with parser. +practically impossible to handle all corner cases with the parser. However, these problems can usually be avoided by minor changes in the code or comment. Known problems and solutions are shown in this section.
@@ -1652,8 +1652,8 @@ code or comment. Known problems and solutions are shown in this section.Recommended approach is to first run SWIG without command line -switch -doxygen. When it successfully processes the code, -include the switch and fix problems with Doxygen comments. +option -doxygen. When it successfully processes the code, +include the option and fix problems with Doxygen comments.
@@ -1661,8 +1661,8 @@ include the switch and fix problems with Doxygen comments.- Inserting conditional compilation preprocessor directive between - Doxygen comment and commented item may break parsing: + Inserting a conditional compilation preprocessor directive between a + Doxygen comment and a commented item may break parsing:
@@ -1680,7 +1680,7 @@ class A {- Solution is to move the directive above comment: + The solution is to move the directive above the comment:
@@ -1734,7 +1734,7 @@ example, JavaDocConverter is the Javadoc module class.-There are two handy command line switches, that enable lots of +There are two handy command line options, that enable lots of detailed debug information printing.
diff --git a/Doc/Manual/Java.html b/Doc/Manual/Java.html index e0c6aed03..db5f041e4 100644 --- a/Doc/Manual/Java.html +++ b/Doc/Manual/Java.html @@ -477,7 +477,7 @@ Exception in thread "main" java.lang.UnsatisfiedLinkError: exampleJNI.gcd(II)Iwhere gcd is the missing JNI function that SWIG generated into the wrapper file. Also make sure you pass all of the required libraries to the linker. -The java -verbose:jni commandline switch is also a great way to get more information on unresolved symbols. +The java -verbose:jni commandline option is also a great way to get more information on unresolved symbols. One last piece of advice is to beware of the common faux pas of having more than one native library version in your path.
@@ -645,7 +645,7 @@ java::To build the DLL and compile the java code, run NMAKE (you may need to run vcvars32 first). This is a pretty simplistic Makefile, but hopefully its enough to get you started. -Of course you may want to make changes for it to work for C++ by adding in the -c++ command line switch for swig and replacing .c with .cxx. +Of course you may want to make changes for it to work for C++ by adding in the -c++ command line option for swig and replacing .c with .cxx.
diff --git a/Doc/Manual/Preprocessor.html b/Doc/Manual/Preprocessor.html index f28f7b2be..3d1bb453e 100644 --- a/Doc/Manual/Preprocessor.html +++ b/Doc/Manual/Preprocessor.html @@ -458,7 +458,7 @@ would generateLike many compilers, SWIG supports a -E command line option to display the output from the preprocessor. -When the -E switch is used, SWIG will not generate any wrappers. +When the -E option is used, SWIG will not generate any wrappers. Instead the results after the preprocessor has run are displayed. This might be useful as an aid to debugging and viewing the results of macro expansions.