Fix some typos in directive names

This commit is contained in:
William S Fulton 2013-05-12 13:18:01 +01:00
commit ea2e615cec
4 changed files with 5 additions and 5 deletions

View file

@ -1613,7 +1613,7 @@ opoverload>
<p> <p>
Variable length argument lists are not supported, by default. If Variable length argument lists are not supported, by default. If
such a function is encountered, a warning will generated to such a function is encountered, a warning will generated to
stderr. Varargs are supported via the SWIG <tt>%vararg</tt> stderr. Varargs are supported via the SWIG <tt>%varargs</tt>
directive. This directive allows you to specify a (finite) directive. This directive allows you to specify a (finite)
argument list which will be inserted into the wrapper in place argument list which will be inserted into the wrapper in place
of the variable length argument indicator. As an example, of the variable length argument indicator. As an example,
@ -1624,7 +1624,7 @@ opoverload&gt;
<p> <p>
See the following section See the following section
on <a href="Varargs.html#Varargs">Variable Length arguments</a> on <a href="Varargs.html#Varargs">Variable Length arguments</a>
provides examples on how <tt>%vararg</tt> can be used, along provides examples on how <tt>%varargs</tt> can be used, along
with other ways such functions can be wrapped. with other ways such functions can be wrapped.
</p> </p>

View file

@ -1359,7 +1359,7 @@ extern void sort_double(double* arr, int len);
to create an array in C/C++ then this can be filled within Lua and passed into the function. It works, but it's a bit tedious. to create an array in C/C++ then this can be filled within Lua and passed into the function. It works, but it's a bit tedious.
More details can be found in the <a href="Library.html#Library_carrays">carrays.i</a> documentation.</p> More details can be found in the <a href="Library.html#Library_carrays">carrays.i</a> documentation.</p>
<p>The second and more intuitive way, would be to pass a Lua table directly into the function, and have SWIG automatically convert between Lua-table and C-array. Within the <tt>&lt;typemaps.i&gt;</tt> file there are typemaps ready written to perform this task. To use them is again a matter of using %appy in the correct manner.</p> <p>The second and more intuitive way, would be to pass a Lua table directly into the function, and have SWIG automatically convert between Lua-table and C-array. Within the <tt>&lt;typemaps.i&gt;</tt> file there are typemaps ready written to perform this task. To use them is again a matter of using %apply in the correct manner.</p>
<p>The wrapper file below, shows both the use of carrays as well as the use of the typemap to wrap arrays. </p> <p>The wrapper file below, shows both the use of carrays as well as the use of the typemap to wrap arrays. </p>

View file

@ -398,7 +398,7 @@ int execlp(const char *path, const char *arg, ...);
</div> </div>
<p> <p>
Note that <tt>str3</tt> is the name of the last argument, as we have used <tt>%vargars</tt> with 3. Note that <tt>str3</tt> is the name of the last argument, as we have used <tt>%varargs</tt> with 3.
Now <tt>execlp("a", "b", "c", "d", "e")</tt> will result in an error as one too many arguments has been passed, Now <tt>execlp("a", "b", "c", "d", "e")</tt> will result in an error as one too many arguments has been passed,
as now only 2 additional 'str' arguments can be passed with the 3rd one always using the specified default <tt>NULL</tt>. as now only 2 additional 'str' arguments can be passed with the 3rd one always using the specified default <tt>NULL</tt>.
</p> </p>

View file

@ -1,5 +1,5 @@
/* /*
The %implict macro allows a SwigType (Class) to be accepted The %implicit macro allows a SwigType (Class) to be accepted
as an input parameter and use its implicit constructors when needed. as an input parameter and use its implicit constructors when needed.
For example: For example: