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

Fix a few more typos in comments

Browse source 
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@9372 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
Olly Betts 2006-09-28 06:39:07 +00:00
commit 1249f48ce0
4 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

2
SWIG/Lib/typemaps/README
View file

@ -1,4 +1,4 @@
Still in developing, but if you are interested into looking around, Still in development, but if you are interested into looking around,
start with start with

12
SWIG/Lib/typemaps/fragments.swg
View file

@ -2,9 +2,9 @@
Fragments: Fragments:
========== ==========
Second to typemaps, fragments is one the most powerfull and Second to typemaps, fragments are one the most powerful and
dangerous swig feature. So, if you are starting to read about them, dangerous swig features. So, if you are starting to read about them,
make sure you read all the document. make sure you read all of this document.
Basics: Basics:
======= =======
@ -26,9 +26,9 @@
$result = value; $result = value;
} }
very soon you will discoverd yourself copying the same long very soon you will discover yourself copying the same long
conversion code in several typemaps, such as varin, directorout, conversion code in several typemaps, such as varin, directorout,
etc. Also, you wil discover that swig copy verbatim the same very etc. Also, you will discover that swig copes verbatim the same very
long conversion code for every argument that requires it, making the long conversion code for every argument that requires it, making the
code very large too. code very large too.
@ -111,7 +111,7 @@
Note that this behavior is opposite to the typemaps, where the Note that this behavior is opposite to the typemaps, where the
last typemap applied or defined prevails. Fragment follows the last typemap applied or defined prevails. Fragment follows the
first-in-first-out convention since they are intended to be first-in-first-out convention since they are intended to be
"global", while typemaps intend to be "locally" specialyzed. "global", while typemaps intend to be "locally" specialized.
3.- Fragments names can not contain commas. 3.- Fragments names can not contain commas.

2
SWIG/Lib/typemaps/inoutlist.swg
View file

@ -154,7 +154,7 @@ multiple output values, they are returned in the form of a list.
For example, suppose you were trying to wrap the modf() function in the For example, suppose you were trying to wrap the modf() function in the
C math library which splits x into integral and fractional parts (and C math library which splits x into integral and fractional parts (and
returns the integer part in one of its parameters).K: returns the integer part in one of its parameters):
double modf(double x, double *ip); double modf(double x, double *ip);

2
SWIG/Lib/typemaps/swigtypemaps.swg
View file

@ -11,7 +11,7 @@
This file provides the frontend to the Unified Typemap Library. This file provides the frontend to the Unified Typemap Library.
When using this library in a SWIG target language, you need to When using this library in a SWIG target language, you need to
define a minimum set of fragments, specialized a couple of macros, define a minimum set of fragments, specialize a couple of macros,
and then include this file. and then include this file.
Typically you will create a 'mytypemaps.swg' file in each target Typically you will create a 'mytypemaps.swg' file in each target