Fix a few documentation typos
This commit is contained in:
parent
9a4dea06c8
commit
3bf1da4298
4 changed files with 7 additions and 7 deletions
4
CHANGES
4
CHANGES
|
|
@ -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+.
|
||||
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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>
|
||||
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue