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

Fix lots of typos in the manual.

Browse source 
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk/SWIG@9368 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
Olly Betts 2006-09-27 17:25:04 +00:00
commit 05ff62fcc2
17 changed files with 53 additions and 53 deletions
Download patch file Download diff file Expand all files Collapse all files

8
Doc/Manual/SWIG.html
View file

@ -1830,7 +1830,7 @@ constants in the target scripting language. This allows you to use them as foll
</div>
<p>
Unfortunately, by declaring the callback functions as constants, they are no longer accesible
Unfortunately, by declaring the callback functions as constants, they are no longer accessible
as functions. For example:
</p>
@ -2335,7 +2335,7 @@ typedef struct {
</pre></div>
<p>
You can make a <tt>Vector</tt> look alot like a class by writing a SWIG interface like this:
You can make a <tt>Vector</tt> look a lot like a class by writing a SWIG interface like this:
</p>
<div class="code"><pre>
@ -2471,7 +2471,7 @@ const double Vector_magnitude_get(Vector *v) {
</div>
<p>
Now, for all practial purposes, <tt>magnitude</tt> will appear like an attribute
Now, for all practical purposes, <tt>magnitude</tt> will appear like an attribute
of the object.
</p>
@ -2940,7 +2940,7 @@ are several reasons why you might want to do this:
<ul>
<li>It is rarely necessary to access every single function in a large
package. Many C functions might have little or no use in a scripted
environment. Therfore, why wrap them?
environment. Therefore, why wrap them?
<li>Separate interface files provide an opportunity to provide more
precise rules about how an interface is to be constructed.