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

Correct some whitespace changes

Browse source
This commit is contained in:
William S Fulton 2017-01-01 14:28:49 +00:00
commit 5b49ad3485
4 changed files with 12 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

4
Doc/Manual/Allegrocl.html
View file

@ -1526,8 +1526,8 @@ overload>
%rename(__predecr__) *::operator--();
%rename(__postdecr__) *::operator--(int);
%rename(__comma__) *::operator, ();
%rename(__comma__) *::operator, () const;
%rename(__comma__) *::operator,();
%rename(__comma__) *::operator,() const;
%rename(__member_ref__) *::operator->;
%rename(__member_func_ref__) *::operator->*;

2
Doc/Manual/Extending.html
View file

@ -1754,7 +1754,7 @@ int variableHandler(Node *n) {
String *symname = Getattr(n, "sym:name");
SwigType *type = Getattr(n, "type");
...
Append(symname, "_global"); // Change symbol name
Append(symname, "_global"); // Change symbol name
SwigType_add_pointer(type); // Add pointer
...
generate wrappers

4
Doc/Manual/SWIG.html
View file

@ -750,7 +750,7 @@ form of type-checking however).</p>
<p>
For enumerations, it is critical that the original enum definition be
included somewhere in the interface file (either in a header file or
in the <tt>%{, %}</tt> block). SWIG only translates the enumeration
in the <tt>%{ %}</tt> block). SWIG only translates the enumeration
into code needed to add the constants to a scripting language. It
needs the original enumeration declaration in order to get the correct
enum values as assigned by the C compiler.
@ -3442,7 +3442,7 @@ header files.
<p>
Sometimes, it is necessary to use certain header files in order for
the code generated by SWIG to compile properly. Make sure you
include certain header files by using a <tt>%{, %}</tt> block like this:
include certain header files by using a <tt>%{ %}</tt> block like this:
</p>
<div class="code"><pre>

14
Doc/Manual/Warnings.html
View file

@ -68,7 +68,7 @@ First, you can run SWIG with the <tt>-w</tt> command line option. For example:
<div class="shell">
<pre>
% swig -python -w501 example.i
% swig -python -w501, 505, 401 example.i
% swig -python -w501,505,401 example.i
</pre>
</div>
@ -81,7 +81,7 @@ into the input file:
<pre>
%module example
#pragma SWIG nowarn=501
#pragma SWIG nowarn=501, 505, 401
#pragma SWIG nowarn=501,505,401
</pre>
</div>
@ -170,7 +170,7 @@ previous section--simply add a "+" to all warning numbers. For example:
<div class="shell">
<pre>
% swig -w+309, +452 example.i
% swig -w+309,+452 example.i
</pre>
</div>
@ -180,7 +180,7 @@ or in your interface file use either
<div class="code">
<pre>
#pragma SWIG nowarn=+309, +452
#pragma SWIG nowarn=+309,+452
</pre>
</div>
@ -190,7 +190,7 @@ or
<div class="code">
<pre>
%warnfilter(+309, +452) foo;
%warnfilter(+309,+452) foo;
</pre>
</div>
@ -205,12 +205,12 @@ You can of course also enable all warnings and suppress a select few, for exampl
<div class="shell">
<pre>
% swig -Wextra -w309, 452 example.i
% swig -Wextra -w309,452 example.i
</pre>
</div>
<p>
The warnings on the right take precedence over the warnings on the left, so in the above example <tt>-Wextra</tt> adds numerous warnings including 452, but then <tt>-w309, 452</tt> overrides this and so 452 is suppressesed.
The warnings on the right take precedence over the warnings on the left, so in the above example <tt>-Wextra</tt> adds numerous warnings including 452, but then <tt>-w309,452</tt> overrides this and so 452 is suppressesed.
</p>
<p>