diff options
author | Olly Betts <olly@survex.com> | 2022-09-29 18:17:32 +1300 |
---|---|---|
committer | Olly Betts <olly@survex.com> | 2022-09-29 18:17:32 +1300 |
commit | 3bf1da4298a31bf5bd18f1ec1cd07e8725b2d54a (patch) | |
tree | cbcd3fd46928081cedd48efb80e20a687a110f00 | |
parent | 9a4dea06c81448f86187c115912b4062ad1b3031 (diff) | |
download | swig-3bf1da4298a31bf5bd18f1ec1cd07e8725b2d54a.tar.gz |
Fix a few documentation typos
-rw-r--r-- | CHANGES | 4 | ||||
-rw-r--r-- | CHANGES.current | 6 | ||||
-rw-r--r-- | Doc/Manual/R.html | 2 | ||||
-rw-r--r-- | Examples/python/import_packages/split_modules/README | 2 |
4 files changed, 7 insertions, 7 deletions
@@ -115,7 +115,7 @@ Version 4.0.2 (8 Jun 2020) 2020-01-13: wsfulton [Python] #1595 Python -builtin constructors silently ignored keyword arguments. - Instead of silenty ignoring them, now a "TypeError: f() takes no keyword arguments" + Instead of silently ignoring them, now a "TypeError: f() takes no keyword arguments" exception is thrown if keyword arguments are used. Hence constructors and normal methods/ functions behave in the same way. Note, -keyword should be used with -builtin to obtain keyword argument support. @@ -200,7 +200,7 @@ Version 4.0.1 (21 Aug 2019) VectorOverload(std::vector< Number,std::allocator< Number > >) VectorOverload(std::vector< int,std::allocator< int > >) - The problem was due to some error handling that was not cleared during typehecking. + The problem was due to some error handling that was not cleared during typechecking. In this case an error was not cleared when the elements in the list failed the typecheck for converting to X. Only occurs in Python 3+. diff --git a/CHANGES.current b/CHANGES.current index bbdcdfb3b..2475aa5f4 100644 --- a/CHANGES.current +++ b/CHANGES.current @@ -75,17 +75,17 @@ Version 4.1.0 (in progress) the rvalue reference parameter has been moved. The parameter's proxy class that owns the C++ object thus has the underlying pointer set to null so that the (moved from, but still valid) C++ object cannot be used again - and the the object is additionally deleted. + and the object is additionally deleted. *** POTENTIAL INCOMPATIBILITY *** 2022-08-28: wsfulton - [Octave] SWIG now marshalls a C/C++ NULL pointer into the null matrix, []. + [Octave] SWIG now marshals a C/C++ NULL pointer into the null matrix, []. SWIG has always marshalled the null matrix into a NULL pointer; this remains and now we have consistency in representing a NULL pointer. 2022-08-26: wsfulton - [Racket] SWIG now marshalls a C/C++ NULL pointer into a null value by calling + [Racket] SWIG now marshals a C/C++ NULL pointer into a null value by calling scheme_make_null(), so that scheme's null? is true for a NULL C/C++ pointer value. 2022-08-18: wsfulton diff --git a/Doc/Manual/R.html b/Doc/Manual/R.html index 9b05922fd..25d86bdeb 100644 --- a/Doc/Manual/R.html +++ b/Doc/Manual/R.html @@ -321,7 +321,7 @@ and forth between integers. <p> The details of enumeration names and contents are stored in hidden R -environments, which are named according the the enumeration name - for +environments, which are named according to the enumeration name - for example, an enumeration colour: </p> diff --git a/Examples/python/import_packages/split_modules/README b/Examples/python/import_packages/split_modules/README index d2ca15e7a..41de834c1 100644 --- a/Examples/python/import_packages/split_modules/README +++ b/Examples/python/import_packages/split_modules/README @@ -4,7 +4,7 @@ and the C/C++ part is not in any package at all. Historically SWIG has supported this sort of thing. From SWIG 4.0.0 onwards, split modules are not supported by default. The %module directive needs to be customised with the moduleimport attribute -in order to import the a global C/C++ module. +in order to import a global C/C++ module. vanilla # "plane Jane" module both halves in pkg1 vanilla_split # python 1/2 in pkg1 C 1/2 in global namespace |