Fix typos in docs and comments
This commit is contained in:
parent
b5544a1812
commit
b127e11f1e
27 changed files with 46 additions and 46 deletions
|
|
@ -75,7 +75,7 @@ Functionality
|
|||
https://www.doxygen.nl/manual/commands.html. If a tag is
|
||||
marked as 'ignored', then the tag is ignored, but the text is copied
|
||||
to the destination documentation. 'Not implemented' means that the
|
||||
tag with it's contents is stripped out of the output.
|
||||
tag with its contents is stripped out of the output.
|
||||
|
||||
Doxygen tags:
|
||||
|
||||
|
|
|
|||
|
|
@ -181,7 +181,7 @@ or enum element comments:
|
|||
<div class="code"><pre>
|
||||
enum E_NUMBERS
|
||||
{
|
||||
EN_ZERO, ///< The first enum item, gets zero as it's value
|
||||
EN_ZERO, ///< The first enum item, gets zero as its value
|
||||
EN_ONE, ///< The second, EN_ONE=1
|
||||
EN_THREE
|
||||
};
|
||||
|
|
|
|||
|
|
@ -644,7 +644,7 @@ java::
|
|||
|
||||
<p>
|
||||
To build the DLL and compile the java code, run NMAKE (you may need to run <tt>vcvars32</tt> first).
|
||||
This is a pretty simplistic Makefile, but hopefully its enough to get you started.
|
||||
This is a pretty simplistic Makefile, but hopefully it's 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 option for swig and replacing .c with .cxx.
|
||||
</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -1520,7 +1520,7 @@ function
|
|||
nil
|
||||
>
|
||||
</pre></div>
|
||||
<p> This behaviour was changed. Now unless -squash-bases option is provided, Derived store a list of it's bases and if some symbol is not found in it's own service tables
|
||||
<p> This behaviour was changed. Now unless -squash-bases option is provided, Derived stores a list of its bases and if some symbol is not found in its own service tables
|
||||
then its bases are searched for it. Option -squash-bases will effectively return old behaviour.
|
||||
</p>
|
||||
|
||||
|
|
@ -1638,7 +1638,7 @@ More details can be found in the <a href="Library.html#Library_carrays">carrays.
|
|||
|
||||
<div class="code"><pre>// using the C-array
|
||||
%include <carrays.i>
|
||||
// this declares a batch of function for manipulating C integer arrays
|
||||
// this declares a batch of functions for manipulating C integer arrays
|
||||
%array_functions(int, int)
|
||||
|
||||
extern void sort_int(int* arr, int len); // the function to wrap
|
||||
|
|
@ -1997,10 +1997,10 @@ So when 'p:Print()' is called, the __index looks on the object metatable for a '
|
|||
In theory, you can play with this usertable & add new features, but remember that it is a shared table between all instances of one class, and you could very easily corrupt the functions in all the instances.
|
||||
</p>
|
||||
<p>
|
||||
Note: Both the opaque structures (like the FILE*) and normal wrapped classes/structs use the same 'swig_lua_userdata' structure. Though the opaque structures has do not have a metatable attached, or any information on how to dispose of them when the interpreter has finished with them.
|
||||
Note: Both the opaque structures (like the FILE*) and normal wrapped classes/structs use the same 'swig_lua_userdata' structure. Though the opaque structures do not have a metatable attached, or any information on how to dispose of them when the interpreter has finished with them.
|
||||
</p>
|
||||
<p>
|
||||
Note: Operator overloads are basically done in the same way, by adding functions such as '__add' & '__call' to the class' metatable. The current implementation is a bit rough as it will add any member function beginning with '__' into the metatable too, assuming its an operator overload.
|
||||
Note: Operator overloads are basically done in the same way, by adding functions such as '__add' & '__call' to the class' metatable. The current implementation is a bit rough as it will add any member function beginning with '__' into the metatable too, assuming it's an operator overload.
|
||||
</p>
|
||||
<H3><a name="Lua_nn38">29.7.3 Memory management</a></H3>
|
||||
|
||||
|
|
|
|||
|
|
@ -2319,7 +2319,7 @@ typedef struct {
|
|||
|
||||
<p>
|
||||
By default, SWIG doesn't know how to the handle the values structure
|
||||
member it's an array, not a pointer. In this case, SWIG makes the array member
|
||||
member because it's an array, not a pointer. In this case, SWIG makes the array member
|
||||
read-only. Reading will simply return a pointer to the first item in the array.
|
||||
To make the member writable, a "memberin" typemap can be used.
|
||||
</p>
|
||||
|
|
@ -2747,7 +2747,7 @@ from the internal <tt>%OWNER</tt> hash).
|
|||
The <tt>%OWNER</tt> hash is an implementation detail, discussed here
|
||||
only to help clarify the operation of <tt>ACQUIRE</tt> and <tt>DISOWN</tt>.
|
||||
You should not access <tt>%OWNER</tt> directly - the details of how it
|
||||
works (and possibly even its existence) may chance in future SWIG versions.
|
||||
works (and possibly even its existence) may change in future SWIG versions.
|
||||
</p>
|
||||
|
||||
<div class="targetlang"><pre>
|
||||
|
|
|
|||
|
|
@ -636,7 +636,7 @@ tcl:
|
|||
|
||||
<p>
|
||||
To build the extension, run NMAKE (you may need to run vcvars32
|
||||
first). This is a pretty minimal Makefile, but hopefully its enough
|
||||
first). This is a pretty minimal Makefile, but hopefully it's enough
|
||||
to get you started. With a little practice, you'll be making lots of
|
||||
Tcl extensions.
|
||||
</p>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue