Permalink
Browse files

Correct spelling of compatibility.

  • Loading branch information...
1 parent 29c98fa commit 5f53503b7d7fa62a351edc7d3d579d69c55c9952 @BrantKyser BrantKyser committed Oct 22, 2013
View
@@ -11,7 +11,7 @@
<ul>
<li><a href="#CSharp_introduction">Introduction</a>
<ul>
-<li><a href="#CSharp_introduction_swig2_compatability">SWIG 2 Compatability</a>
+<li><a href="#CSharp_introduction_swig2_compatibility">SWIG 2 Compatibility</a>
</ul>
<li><a href="#CSharp_differences_java">Differences to the Java module</a>
<li><a href="#CSharp_void_pointers">Void pointers</a>
@@ -72,10 +72,10 @@
Monodoc, available from the Mono project, has a very useful section titled <a href="http://www.mono-project.com/Interop_with_Native_Libraries">Interop with native libraries</a>.
</p>
-<H3><a name="CSharp_introduction_swig2_compatability"></a>19.1.1 SWIG 2 Compatability</H3>
+<H3><a name="CSharp_introduction_swig2_compatibility"></a>19.1.1 SWIG 2 Compatibility</H3>
<p>
-In order to minimize name collisions between names generated based on input to SWIG and names used in the generated code from the .NET framework, SWIG 3 fully qualifies the use of all .NET types. Furthermore, SWIG 3 avoids <tt>using</tt> directives in generated code. This breaks backwards compatability with typemaps, pragmas, etc written for use with SWIG 2 that assume the presence of <tt>using System;</tt> or <tt>using System.Runtime.InteropServices;</tt> directives in the intermediate class imports, module imports, or proxy imports. SWIG 3 supports backwards compatability though the use of the <tt>SWIG2_CSHARP</tt> macro. If <tt>SWIG2_CSHARP</tt> is defined, SWIG 3 generates <tt>using</tt> directives in the intermediate class, module class, and proxy class code similar to those generated by SWIG 2. This can be done without modifying any of the input code by passing the <tt>-DSWIG2_CSHARP</tt> commandline parameter when executing <tt>swig</tt>.
+In order to minimize name collisions between names generated based on input to SWIG and names used in the generated code from the .NET framework, SWIG 3 fully qualifies the use of all .NET types. Furthermore, SWIG 3 avoids <tt>using</tt> directives in generated code. This breaks backwards compatibility with typemaps, pragmas, etc written for use with SWIG 2 that assume the presence of <tt>using System;</tt> or <tt>using System.Runtime.InteropServices;</tt> directives in the intermediate class imports, module imports, or proxy imports. SWIG 3 supports backwards compatibility though the use of the <tt>SWIG2_CSHARP</tt> macro. If <tt>SWIG2_CSHARP</tt> is defined, SWIG 3 generates <tt>using</tt> directives in the intermediate class, module class, and proxy class code similar to those generated by SWIG 2. This can be done without modifying any of the input code by passing the <tt>-DSWIG2_CSHARP</tt> commandline parameter when executing <tt>swig</tt>.
</p>
<H2><a name="CSharp_differences_java"></a>19.2 Differences to the Java module</H2>
@@ -14,7 +14,7 @@ top_builddir = ../@top_builddir@
CPP_TEST_CASES = \
csharp_attributes \
- csharp_swig2_compatability \
+ csharp_swig2_compatibility \
csharp_exceptions \
csharp_features \
csharp_lib_arrays \
@@ -37,7 +37,7 @@ CSHARPFLAGSSPECIAL =
# Custom tests - tests with additional commandline options
intermediary_classname.cpptest: SWIGOPT += -dllimport intermediary_classname
csharp_lib_arrays.cpptest: CSHARPFLAGSSPECIAL = -unsafe
-csharp_swig2_compatability.cpptest: SWIGOPT += -DSWIG2_CSHARP
+csharp_swig2_compatibility.cpptest: SWIGOPT += -DSWIG2_CSHARP
# Rules for the different types of tests
%.cpptest:
@@ -1,9 +1,9 @@
-%module csharp_swig2_compatability
+%module csharp_swig2_compatibility
%typemap(cscode) Foo %{
// Without the using directives generated by the
-// SWIG 2 compatability mode, this code would fail
+// SWIG 2 compatibility mode, this code would fail
// to build.
public void FooBar(string input)
{
@@ -15,7 +15,7 @@ public void FooBar(string input)
%pragma(csharp) imclasscode=%{
// Without the using directives generated by the
-// SWIG 2 compatability mode, this code would fail
+// SWIG 2 compatibility mode, this code would fail
// to build.
public void IntermediateClassMethod(string input)
{
@@ -27,7 +27,7 @@ public void IntermediateClassMethod(string input)
%pragma(csharp) modulecode=%{
// Without the using directives generated by the
-// SWIG 2 compatability mode, this code would fail
+// SWIG 2 compatibility mode, this code would fail
// to build.
public void ModuleClassMethod(string input)
{
View
@@ -11,7 +11,7 @@
* The imtype typemap contains the C# type used in the intermediary class.
* The cstype typemap contains the C# type used in the C# proxy classes, type wrapper classes and module class. */
-/* SWIG 3 no longer inserts using directives into generated C# code. For backwards compatability, the SWIG2_CSHARP
+/* SWIG 3 no longer inserts using directives into generated C# code. For backwards compatibility, the SWIG2_CSHARP
macro can be defined to have SWIG 3 generate using directives similar to those generated by SWIG 2. */
#ifdef SWIG2_CSHARP

0 comments on commit 5f53503

Please sign in to comment.