| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
| |
Without this you get two set_transform() functions defined in the
.py file, which can trigger warnings from linting tools.
Renaming the SWIG-generated wrapper is a reasonably clean solution
(though does leave an unused _set_transform() Python function).
See #2578
|
| |
|
|
|
|
|
|
|
| |
So far C#, Java, Lua and PHP are supported.
Closes: #2540
See #1567
|
| |
|
|
|
|
|
| |
The format was changed from that the manual shows in 2010 by
5a3ba0d607132bfe78c5c23b3d8d2694a9250957!
|
|
|
|
| |
Fixes #2528
|
|
|
|
|
|
|
|
|
|
|
| |
We were providing an example set of typemaps in the manual, but they
were specific to Python2 which isn't helpful these days.
For typical cases argcargv.i is a better option. It doesn't currently
seem to directly support the "argv without argc" case which this example
actually shows, but generally APIs take a length as well as a char**.
Closes: #2040
|
|
|
|
| |
Closes: #1944
|
| |
|
| |
|
|
|
|
|
| |
PHP7 security support ended 2022-11-28 so it doesn't make sense to
include support for it in the SWIG 4.2.x release series.
|
| |
|
|
|
|
|
|
|
| |
Remove warning SWIGWARN_CPP11_VARIADIC_TEMPLATE which was issued if more
than one argument was used for a variadic template.
SwigType enhancement: 'v.' now represents a variadic argument.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
decltype now accepts C++ expressions instead of just an ID, such as:
int i,j;
... decltype(i+j) ...
... decltype(&i) ...
These result in a warning for non-trivial expressions which SWIG cannot evaluate:
Warning 344: Unable to deduce decltype for 'i+j'.
See 'Type Inference' in CPlusPlus.html for workarounds.
Issue #1589
Issue #1590
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* rtests2:
more r tests
more r tests
added testcase pointer_reference
[PHP] Update docs for removal of -noproxy in SWIG 4.1.0
Conflicts:
CHANGES.current
|
| |
| |
| |
| | |
Closes #2419
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
| |
Named duplicate class template instantiations now issue a warning and are ignored.
Duplicate empty class template instantiations are quietly ignored.
The test cases are fixed for this new behaviour.
This commit is a pre-requisite for the near future so that the Python
builtin wrappers can correctly use the SwigType_namestr function without
generating duplicate symbol names.
|
| |
|
| |
|
| |
|
|
|
|
| |
Fix for version 0.12.6, see https://github.com/wkhtmltopdf/wkhtmltopdf/issues/4536
|
| |
|
|
|
|
|
|
|
|
| |
This reverts commit 22a4355f340e9a844d5e5d8d0528d767c4808ebb.
Conflicts:
CHANGES.current
RELEASENOTES
|
|
|
|
| |
The minimum version we now support is Python 2.7.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
No meaningful progress to update CFFI to experimental status
has been made since CFFI was disabled in SWIG-4.0.0 as the first
stage to removal. This commit is the final stage to remove it.
See issue #1966 for an attempt at updating CFFI to experimental
status. Anyone wishing for SWIG to support CFFI again might
want to utilise this work.
|
|
|
|
|
|
| |
This has only been present for backward compatibility since 2006
and now has the value 0 so doesn't do anything, so don't use it
as an example of a flag in the docs.
|
|
|
|
|
| |
The mingw.org domain is no longer associated with the project, and
they've also moved from sourceforge to osdn.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Such as:
class X final {};
This no longer gives a syntax error.
This change has introduced one more shift-reduce conflict in the parser.
with a conflict with a C style variable declaration with name final:
class X final;
resulting in a syntax error (for C++ not C). This is an an unusual style
for C++ code and more typical declarations do work:
X final;
Closes #672
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Until now SWIG quietly ignored such errors unless -Wextra (or -Wall
which implies -Wextra) was passed, but this is unhelpful as it hides
problems. To illustrate this point, enabling this warning by
default revealled a typo in the preproc_defined.i testcase in
SWIG's own testsuite.
If you really don't want to see this warning, you can suppress it
with command line option -w202 or by using this in your interface
file:
%warnfilter(SWIGWARN_PP_EVALUATION);
Both will work with older versions of SWIG too.
Fixes #1465
Fixes #2389
|
|
|
|
| |
The upcoming release is 4.1.0 not 4.2.0.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Ensure that SWIG_VERSION is defined both at SWIG-time and in the
generated C/C++ wrapper code (it was only defined in the wrapper
for some target languages previously).
SWIGGO and SWIGJAVASCRIPT are now defined in the generated wrappers
to match behaviour for all other target languages.
Stop defining SWIGVERSION in the wrapper. This only happened as a
side-effect of how SWIG_VERSION was defined but was never documented and
is redundant.
The new testcase also checks that SWIG is defined at SWIG-time but not
in the generated wrapper, and that exactly one of a list of
target-language specific macros is defined.
Fixes #1050
|
|\
| |
| | |
Update Windows CMake builds to use NuGet package for PCRE2
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Returns a list of sorted keys in a DOH Hash.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
This follows PHP 8.2 deprecating dynamic features.
The new feature also provides a clean way to fix the remaining PHP
test case failure under PHP 8.2.
|
| |
| |
| |
| |
| |
| | |
Octave has more operators than C++. These operators can be overloaded for
the type swig_ref using the standard Octave Object Oriented Programming mechanism.
This is now added to the documentation.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
For implementing full move semantics when passing parameters by value.
Based on SWIGTYPE && and std::unique_ptr typemaps which implement move
semantics.
Added for all languages, but untested for: Go, Ocaml, R, Scilab (and
unlikely to be fully functional for same reasons as for std::unique_ptr
support).
Issue #999
|
| |
| |
| |
| |
| | |
Document rvalue reference outputs behaviour
Test rvalue reference outputs
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
SWIG has always marshalled the null matrix into a NULL pointer; this remains
and now we have consistency in representing a NULL pointer.
This is a pre-requisite for a pending commit to fully support std::unique_ptr.
|
| | |
|