More typos
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk/SWIG@9369 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
parent
05ff62fcc2
commit
d6c5455edc
2 changed files with 6 additions and 6 deletions
|
|
@ -174,7 +174,7 @@ To minimize compilation time, please include as few other header files as possib
|
|||
|
||||
Each file in a module should be given a filename that is all lowercase letters
|
||||
such as "parser.c", not "Parser.c" or "PARSER.c". Please note that filenames
|
||||
are case-insensitive on Windows so this convention will prevent you from inadvertantly
|
||||
are case-insensitive on Windows so this convention will prevent you from inadvertently
|
||||
creating two files that differ in case-only.
|
||||
|
||||
<p>
|
||||
|
|
@ -224,7 +224,7 @@ makes it possible to extract version information from a raw binary
|
|||
(sometimes useful in debugging).
|
||||
|
||||
<p>
|
||||
As a general rule, files start to get unmanagable once they exceed
|
||||
As a general rule, files start to get unmanageable once they exceed
|
||||
about 2000 lines. Files larger than this should be broken up into
|
||||
multiple files. Similarly, you should avoid the temptation to create
|
||||
many small files as this increases compilation time and makes the
|
||||
|
|
|
|||
|
|
@ -193,7 +193,7 @@ everything else.
|
|||
<li> In "help" mode, clean up open files and exit.
|
||||
<li> In "checkout" mode, copy specified files from the SWIG library
|
||||
to the current directory. Errors cause error messages but no
|
||||
non-lcoal exits.
|
||||
non-local exits.
|
||||
<li> Otherwise, do wrapping: determine output file name(s), define
|
||||
some preprocessor symbols and run the preprocessor, initialize
|
||||
the interface-definition parser, set up the typemap for handling
|
||||
|
|
@ -230,7 +230,7 @@ dumped---DOH!").
|
|||
The development of DOH is influenced heavily by the problems
|
||||
encountered during earlier attempts to create a C++ based version of
|
||||
SWIG2.0. In each of these attempts (over a 3 year period), the
|
||||
resulting system always ended up growing into a collossal nightmare of
|
||||
resulting system always ended up growing into a colossal nightmare of
|
||||
large inheritance hierarchies and dozens of specialized classes for
|
||||
different types of objects (functions, variables, constants, etc.).
|
||||
The end result was that the system was tremendously complicated,
|
||||
|
|
@ -415,7 +415,7 @@ are copied by reference.
|
|||
|
||||
The DOH String type is perhaps the most flexible object. First, it supports a variety of string-oriented
|
||||
operations. Second, it supports many of the same operations as lists. Finally, strings provide file I/O
|
||||
operations that allow them to be used interchangably with DOH file objects.
|
||||
operations that allow them to be used interchangeably with DOH file objects.
|
||||
|
||||
[ TODO ]
|
||||
|
||||
|
|
@ -896,7 +896,7 @@ have taken care of the type conversions for the <tt>Vector</tt> type automatical
|
|||
and return values so that language module writers don't have to worry about it too much.
|
||||
|
||||
<p>
|
||||
<li>These functions may be superceded by features in the new typemap system which provide hooks
|
||||
<li>These functions may be superseded by features in the new typemap system which provide hooks
|
||||
for specifying local variable declarations and argument conversions.
|
||||
|
||||
</ul>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue