diff options
author | Olly Betts <olly@survex.com> | 2010-05-23 03:43:31 +0000 |
---|---|---|
committer | Olly Betts <olly@survex.com> | 2010-05-23 03:43:31 +0000 |
commit | 3f47ff6988c5e48617f5b4b43a50582a56c72919 (patch) | |
tree | dce152ddd3ee38513c700b740e2d70376a8acbfe | |
parent | 51bbc83fdd2cff376b5814c24f94e1e0b40bc17a (diff) | |
download | swig-3f47ff6988c5e48617f5b4b43a50582a56c72919.tar.gz |
Fix more doubled word typos
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@12040 626c5289-ae23-0410-ae9c-e8d60b6d4f22
-rw-r--r-- | Doc/Manual/Allegrocl.html | 2 | ||||
-rw-r--r-- | Doc/Manual/CSharp.html | 2 | ||||
-rw-r--r-- | Doc/Manual/Customization.html | 2 | ||||
-rw-r--r-- | Doc/Manual/Introduction.html | 2 | ||||
-rw-r--r-- | Doc/Manual/Java.html | 8 | ||||
-rw-r--r-- | Doc/Manual/Lua.html | 4 | ||||
-rw-r--r-- | Doc/Manual/Octave.html | 2 | ||||
-rw-r--r-- | Doc/Manual/Pike.html | 2 | ||||
-rw-r--r-- | Doc/Manual/Python.html | 4 | ||||
-rw-r--r-- | Doc/Manual/Ruby.html | 4 | ||||
-rw-r--r-- | Doc/Manual/SWIG.html | 2 | ||||
-rw-r--r-- | Doc/Manual/Windows.html | 2 |
12 files changed, 18 insertions, 18 deletions
diff --git a/Doc/Manual/Allegrocl.html b/Doc/Manual/Allegrocl.html index 5cedee26b..5d00c4cd0 100644 --- a/Doc/Manual/Allegrocl.html +++ b/Doc/Manual/Allegrocl.html @@ -1777,7 +1777,7 @@ return-val wrapper-name(parm0, parm1, ..., parmN) </div> <p> - These three typemaps are specifically employed by the the + These three typemaps are specifically employed by the Allegro CL interface generator. SWIG also implements a number of other typemaps that can be used for generating code in the C/C++ wrappers. You can read about diff --git a/Doc/Manual/CSharp.html b/Doc/Manual/CSharp.html index 21b319e29..ea8b66e65 100644 --- a/Doc/Manual/CSharp.html +++ b/Doc/Manual/CSharp.html @@ -511,7 +511,7 @@ In the P/Invoke default marshalling scheme, one needs to designate whether the i array parameter as input, output, or both. When the function is invoked, the CLR allocates a separate chunk of memory as big as the given managed array, which is automatically released at the end of the function call. If the array parameter is marked as being input, the content of the managed array is copied into this buffer when the call is made. Correspondingly, if the array parameter is marked as being output, the contents of the reserved buffer are copied -back into the managed array after the call returns. A pointer to to this buffer +back into the managed array after the call returns. A pointer to this buffer is passed to the native function. </p> diff --git a/Doc/Manual/Customization.html b/Doc/Manual/Customization.html index 734067475..b43075991 100644 --- a/Doc/Manual/Customization.html +++ b/Doc/Manual/Customization.html @@ -775,7 +775,7 @@ involving <tt>%feature</tt>: <p> The name matching rules outlined in the <a href="SWIGPlus.html#SWIGPlus_ambiguity_resolution_renaming">Ambiguity resolution and renaming</a> section applies to all <tt>%feature</tt> directives. -In fact the the <tt>%rename</tt> directive is just a special form of <tt>%feature</tt>. +In fact the <tt>%rename</tt> directive is just a special form of <tt>%feature</tt>. The matching rules mean that features are very flexible and can be applied with pinpoint accuracy to specific declarations if needed. Additionally, if no declaration name is given, a global feature is said to be defined. diff --git a/Doc/Manual/Introduction.html b/Doc/Manual/Introduction.html index df8d03fdf..4b954040b 100644 --- a/Doc/Manual/Introduction.html +++ b/Doc/Manual/Introduction.html @@ -365,7 +365,7 @@ possible to support different types of interfaces depending on the application. <p> SWIG is a command line tool and as such can be incorporated into any build system that supports invoking external tools/compilers. -SWIG is most commonly invoked from within a Makefile, but is also known to be invoked from from popular IDEs such as +SWIG is most commonly invoked from within a Makefile, but is also known to be invoked from popular IDEs such as Microsoft Visual Studio. </p> diff --git a/Doc/Manual/Java.html b/Doc/Manual/Java.html index 857363840..366736eb7 100644 --- a/Doc/Manual/Java.html +++ b/Doc/Manual/Java.html @@ -1094,7 +1094,7 @@ C++ enums defined within a C++ class are generated into a static final inner Jav </p> <p> -Typesafe enums have their advantages over using plain integers in that they they can be used in a typesafe manner. +Typesafe enums have their advantages over using plain integers in that they can be used in a typesafe manner. However, there are limitations. For example, they cannot be used in switch statements and serialization is an issue. Please look at the following references for further information: @@ -2270,7 +2270,7 @@ For example, let's change the intermediary JNI class access to just the default </div> <p> -All the methods in the intermediary JNI class will then not be be callable outside of the package as the method modifiers have been changed from public access to default access. This is useful if you want to prevent users calling these low level functions. +All the methods in the intermediary JNI class will then not be callable outside of the package as the method modifiers have been changed from public access to default access. This is useful if you want to prevent users calling these low level functions. </p> <H3><a name="Java_module_class"></a>21.4.2 The Java module class</H3> @@ -2758,7 +2758,7 @@ You can encourage the garbage collector to call the finalizers, for example, add } </pre></div> <p>Although this usually works, the documentation doesn't guarantee that <tt>runFinalization()</tt> will actually call the finalizers. -As the the shutdown hook is guaranteed you could also make a JNI call to clean up any resources that are being tracked by the C/C++ code.</p> +As the shutdown hook is guaranteed you could also make a JNI call to clean up any resources that are being tracked by the C/C++ code.</p> </li> <li> @@ -4521,7 +4521,7 @@ code. <p> This section describes how you can modify SWIG's default wrapping behavior for various C/C++ datatypes using the <tt>%typemap</tt> directive. -You are advised to be familiar with the the material in the "<a href="Typemaps.html#Typemaps">Typemaps</a>" chapter. +You are advised to be familiar with the material in the "<a href="Typemaps.html#Typemaps">Typemaps</a>" chapter. While not absolutely essential knowledge, this section assumes some familiarity with the Java Native Interface (JNI). JNI documentation can be consulted either online at <a href="http://java.sun.com">Sun's Java web site</a> or from a good JNI book. The following two books are recommended:</p> diff --git a/Doc/Manual/Lua.html b/Doc/Manual/Lua.html index 53687d3de..a1544d21e 100644 --- a/Doc/Manual/Lua.html +++ b/Doc/Manual/Lua.html @@ -334,7 +334,7 @@ extern double Foo; %mutable; </pre></div> <p> -SWIG will allow the the reading of <tt>Foo</tt> but when a set attempt is made, an error function will be called. +SWIG will allow the reading of <tt>Foo</tt> but when a set attempt is made, an error function will be called. </p> <div class="targetlang"><pre> > print(e.Foo) -- reading works ok @@ -1099,7 +1099,7 @@ userdata: 0003D880 </pre></div> <p> -Note: is is also possible (though tedious) to have a function throw several different kinds of exceptions. To process this +Note: it is also possible (though tedious) to have a function throw several different kinds of exceptions. To process this will require a pcall, followed by a set of if statements checking the type of the error. </p> <p> diff --git a/Doc/Manual/Octave.html b/Doc/Manual/Octave.html index 63663a474..de28a1427 100644 --- a/Doc/Manual/Octave.html +++ b/Doc/Manual/Octave.html @@ -239,7 +239,7 @@ extern double Foo; </pre></div> <p> - SWIG will allow the the reading of <tt>Foo</tt> but when a set attempt is made, an error function will be called. + SWIG will allow the reading of <tt>Foo</tt> but when a set attempt is made, an error function will be called. </p> <div class="targetlang"><pre>octave:1> example diff --git a/Doc/Manual/Pike.html b/Doc/Manual/Pike.html index a47d07865..ad8976a14 100644 --- a/Doc/Manual/Pike.html +++ b/Doc/Manual/Pike.html @@ -172,7 +172,7 @@ exactly as you'd expect it to: <p> -Global variables are currently wrapped as a pair of of functions, one to get +Global variables are currently wrapped as a pair of functions, one to get the current value of the variable and another to set it. For example, the declaration </p> diff --git a/Doc/Manual/Python.html b/Doc/Manual/Python.html index aa50630be..8f876316e 100644 --- a/Doc/Manual/Python.html +++ b/Doc/Manual/Python.html @@ -1282,7 +1282,7 @@ something like this: <p> This object is actually a Python instance that has been wrapped around a pointer to the low-level C structure. This instance doesn't actually do anything--it just serves as a proxy. -The pointer to the C object can be found in the the <tt>.this</tt> +The pointer to the C object can be found in the <tt>.this</tt> attribute. For example: </p> @@ -3101,7 +3101,7 @@ customization features. <p>Sometimes you may want to replace or modify the wrapper function that SWIG creates in the proxy <tt>.py</tt> file. The Python module -in SWIG provides some features that enable you do do this. First, to +in SWIG provides some features that enable you to do this. First, to entirely replace a proxy function you can use <tt>%feature("shadow")</tt>. For example:</p> diff --git a/Doc/Manual/Ruby.html b/Doc/Manual/Ruby.html index 8684c355f..8b43962c5 100644 --- a/Doc/Manual/Ruby.html +++ b/Doc/Manual/Ruby.html @@ -10204,7 +10204,7 @@ the same underlying C++ object. This can cause problems. For example:<br> -<p>After the the garbage collector runs, as a result of our call +<p>After the garbage collector runs, as a result of our call to <tt>GC.start</tt>, calling<tt>tiger2.get_name()</tt> causes a segmentation fault. The problem is that when <tt>tiger1</tt> is garbage collected, it frees the underlying C++ object. Thus, when <tt>tiger2</tt> @@ -10649,7 +10649,7 @@ initialization a normal Ruby interpreter will call the ruby_init() function which in turn will call a function called Init_stack or similar. This function will store a pointer to the location where -the stack points at at that point in time.</p> +the stack points at that point in time.</p> diff --git a/Doc/Manual/SWIG.html b/Doc/Manual/SWIG.html index e4a2a8c42..b4f332b14 100644 --- a/Doc/Manual/SWIG.html +++ b/Doc/Manual/SWIG.html @@ -92,7 +92,7 @@ chapters. <p> -To run SWIG, use the <tt>swig</tt> command with options options and a filename like this: +To run SWIG, use the <tt>swig</tt> command with options and a filename like this: </p> <div class="shell"><pre> diff --git a/Doc/Manual/Windows.html b/Doc/Manual/Windows.html index 5d16a8b9f..e295fe307 100644 --- a/Doc/Manual/Windows.html +++ b/Doc/Manual/Windows.html @@ -272,7 +272,7 @@ Execute the steps in the order shown and don't use spaces in path names. In fact <ul> <li>Answer y to the "do you wish to continue with the post install?"</li> <li>Answer y to the "do you have MinGW installed?"</li> - <li>Type in the the folder in which you installed MinGW (C:/MinGW is default)</li> + <li>Type in the folder in which you installed MinGW (C:/MinGW is default)</li> </ul> </li> |