| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
See #1567
|
|
|
|
|
|
|
|
|
| |
The "deprecation" warning has been changed to a "removal" warning
with newer JDK versions. This needs to be addressed, but meanwhile
it makes running the testsuite unusably noisy so suppressing it
seems more helpful than not.
Closes: #2556
|
|
|
|
|
|
|
| |
So far C#, Java, Lua and PHP are supported.
Closes: #2540
See #1567
|
| |
|
|
|
|
| |
See #2538
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We aim to produce code that works with C90 or C++98 so we can't
assume snprintf() is available, but it almost always is (even
on systems from before it was standardised) so having a way to
use it is helpful.
Enable this automatically if the compiler claims conformance
with at least C90 or C++98 and check SWIG_HAVE_SNPRINTF to allow
turning on manually, but disable if SWIG_NO_SNPRINTF if defined.
The fallback is to call sprintf() without a buffer size check -
checking after the call is really shutting the stable door after
the horse has bolted, and most of our uses either have a fixed maximum
possible size or dynamically allocate a buffer that's large enough.
Fixes: #2502 (sprintf deprecation warnings on macos)
Fixes: #2548
|
|
|
|
|
|
|
|
|
|
|
|
| |
SWIG_LUA_CONSTTAB_INT can be called with a constant expression
containing commas (e.g. `SizeOf< int,int >::size`). This was
addressed in b13f584258079dd88a4ca87412b87ac4464686df by making
its second argument variadic, but (a) this doesn't work with
our baseline of C90/C++98 and (b) the variadic syntax used is
a GCC extension which doesn't work with all compilers (e.g. MSVC).
We can solve this without needing variadic macros by simply wrapping
this argument in an extra pair of parentheses when calling.
|
|
|
|
| |
This reverts commit b13f584258079dd88a4ca87412b87ac4464686df.
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* python-iterator-protocol:
Finish removal of SwigPySequence_Cont
Remove undocumented and non-existent STL std::carray
Remove assign method uses by the removed Python Sequence Protocol
Remove now redundant use of Python Sequence protocol in STL wrappers
Add support for all STL containers to be constructible from a Python set
Iterator Protocol support for std::array wrappers
STL support for copying Python objects supporting Iterator protocol
Closes #2515
Conflicts:
CHANGES.current
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Removes SwigPySequence_Cont and support classes:
SwigPySequence_ArrowProxy, SwigPySequence_Cont, SwigPySequence_Ref
The recently added Iterator Protocol support should cover the Sequence
Protocol usage for converting from Python containers to STL containers.
|
| | |
|
| |
| |
| |
| |
| | |
Introduce swig::IteratorProtocol class and assign which can be partially
specialized by different container types, such as std::array.
|
| |
| |
| |
| | |
std::array not working though
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Use c_str() only when we need a terminating zero byte and data() when
we don't (as we already did in most cases). The two methods in fact
do the same thing as of C++11 (and in practice did for all C++98
implementations I'm aware of) but it's useful to make clear when we need
a terminating zero byte and when we don't, for example for adding
string_view support (string_view supports data(), but can't support
c_str() (since it could be a slice from the middle of a std::string).
|
| |
| |
| |
| |
| |
| |
| | |
By default SWIG/PHP wraps std::string& as a pass-by-reference PHP
string parameter, but sometimes such a parameter is only for input
or only for output, so add support for the named typemaps that other
target languages support.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This method checks if the range of the input variable is fine.
However if the errno variable was already set, it fails even for valid inputs.
This fixes at least some random failures in the python castmode.
Fixes: #2519
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix warnings in the extend_template_method, li_std_string, and
template_methods tests. std::string was missing a typecheck typemap.
Add extend_template_method_runme.ml, li_std_string_runme.ml, and
template_methods_runme.ml.
Add INPUT, OUTPUT and INOUT typemaps for string &
Use the INOUT typemap in the strings_test example. In the
strings_test example, takes_and_gives_std_string() was relying on the
silly fact that an argout typemap for string & was enabled by
default.
Remove the in, out, and typecheck typemaps for string &.
Closes: #1439
|
| |
| |
| |
| |
| | |
The bulk of this was already removed in
e3b112c69ceed5c39cb07fa45a3ba62b27712679.
|
| | |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Make argc and argv test works in C.
Signed-off-by: Erez Geva <ErezGeva2@gmail.com>
|
| | | |
|
|\ \ \ |
|
| | | | |
|
| | | | |
|
| | |/
| |/|
| | |
| | |
| | | |
Ruby 3.2 issue: https://bugs.ruby-lang.org/issues/18007
Similar to https://github.com/robinst/swig/commit/9b5d37fd174331fa2b7113fe968fcf0570de43bf
|
| |/
|/|
| |
| | |
Fixes #894
|
|/
|
|
|
| |
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.
|
|\
| |
| |
| |
| |
| |
| | |
* alatina-master:
Update octruntime.swg
Update octrun.swg to work with Octave v8.1.0
Update octruntime.swg to work with Octave v8.1.0
|
| | |
|
| |\
| | |
| | | |
Update octruntime.swg to work with Octave v8.1.0
|
| | | |
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | |
| | | |
* bda_resolve_warnings:
Use $self instead of self
Lib/csharp: Resolve a few warnings about unused parameters
|
| | | |
|
| |/ |
|
|\ \
| | |
| | | |
[Java] Added usage of nullptr instead of NULL
|
| |/ |
|
| |
| |
| |
| |
| |
| |
| | |
Efficiency fixes and tidy up from previous commit.
Add test case for constructing from differently sized containers.
Issue #2478
|
|/ |
|
|\
| |
| | |
[Python] Eliminate sprintf in generated code
|
| |
| |
| |
| |
| |
| |
| | |
Newer clang versions emit warnings in generated code:
```
warning: 'sprintf' is deprecated: This function is provided for compatibility reasons only. Due to security concerns inherent in the design of sprintf(3), it is highly recommended that you use snprintf(3) instead. [-Wdeprecated-declarations]
```
|
|/ |
|
|
|
|
|
|
|
|
|
| |
Without this, perlhead.swg does `#pragma GCC diagnostic pop`
if `__GNUC__ >= 10` - without any prior `#pragma GCC diagnostic push`.
There's also a mismatch between the conditions that trigger
`#pragma GCC diagnostic ignored` (where the `push` should be)
and the attempt to `#pragma GCC diagnostic pop`.
|