diff --git a/Doc/Manual/Preprocessor.html b/Doc/Manual/Preprocessor.html index 8d41efccf..332d2a576 100644 --- a/Doc/Manual/Preprocessor.html +++ b/Doc/Manual/Preprocessor.html @@ -306,7 +306,13 @@ interface building. However, they are used internally to implement a number of SWIG directives and are provided to make SWIG more compatible with C99 code.
-+The preprocessor handles { }, " " and %{ %} delimiters differently. +
+ +@@ -331,7 +337,7 @@ the contents of the %{ ... %} block are copied without modification to the output (including all preprocessor directives).
-diff --git a/Doc/Manual/Typemaps.html b/Doc/Manual/Typemaps.html index b6e8cf3ce..b3b0bc7a9 100644 --- a/Doc/Manual/Typemaps.html +++ b/Doc/Manual/Typemaps.html @@ -3673,17 +3673,21 @@ generated into the wrapper code before any typemap code that calls it.
To define a fragment you need a fragment name, a section name for generating the fragment code into, and the code itself. See Code insertion blocks for a full list of section names. -Usually the section name used is "header". Both string and curly braces can be used: +Usually the section name used is "header". Different delimiters can be used:
+%fragment("my_name", "header") %{ ... %}
%fragment("my_name", "header") { ... }
%fragment("my_name", "header") " ... "
+and these follow the usual preprocessing rules mentioned in the +Preprocessing delimiters +section. The following are some rules and guidelines for using fragments:
@@ -3761,8 +3765,8 @@ A fragment can use one or more additional fragments, for example:
-%fragment("<limits.h>", "header") {
- #include <limits.h>
+%fragment("<limits.h>", "header") {
+ %#include <limits.h>
}