Fix some minor typos in the doc
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@13560 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
parent
7dac1bc524
commit
ff2df5b288
2 changed files with 2 additions and 2 deletions
|
|
@ -498,7 +498,7 @@ into Go types.
|
|||
<p>Because of limitations in the way output arguments are processed in swig,
|
||||
a function with output arguments will not have multiple return values.
|
||||
Instead, you must pass a pointer into the C++ function to tell it where to
|
||||
store the ouput value. In go, you supply a slice in the place of the output
|
||||
store the output value. In go, you supply a slice in the place of the output
|
||||
argument.</p>
|
||||
|
||||
<p>For example, suppose you were trying to wrap the modf() function in the
|
||||
|
|
|
|||
|
|
@ -126,7 +126,7 @@ the resulting .ml and .mli files as well, and do the final link with -custom
|
|||
|
||||
|
||||
<p>
|
||||
The O'Caml SWIG module now requires you to compile a module (<tt>Swig</tt>)
|
||||
The OCaml SWIG module now requires you to compile a module (<tt>Swig</tt>)
|
||||
separately. In addition to aggregating common SWIG functionality, the Swig
|
||||
module contains the data structure that represents C/C++ values. This allows
|
||||
easier data sharing between modules if two or more are combined, because
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue