| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | | |
std::array not working though
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
I don't have access to jsc atm
|
| | |/
| |/| |
|
| | |
| | |
| | |
| | | |
There's no need to do a substring check here.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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).
|
|/ /
| |
| |
| |
| | |
The format was changed from that the manual shows in 2010 by
5a3ba0d607132bfe78c5c23b3d8d2694a9250957!
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously the default was always "node", even if nodejs wasn't
detected by configure. This leads to a confusing failure from
"make check" if you have another support JS engine installed
but not node.
Now the default it picked based on which engines configure
found. If only one was detected, that should be used. If
multiple are, you can override the default choice by specifying
e.g. ENGINE=jsc on the make command line.
Fixes #2453
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Nodejs is like V8 and needs C++ output enabled when wrapping C code.
The testsuite was masking this bug by using SWIG options
`-v8 -DBUILDING_NODE_EXTENSION=1` rather than `-node` when testing
with nodejs, while the javascript examples currently all seem to all get
processed with -c++.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| | |
Fixes #2528
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
|
| |
| |
| |
| | |
Should fix "Node.js 12 actions are deprecated" warning.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| | |
Fixes failure for cpp20_spaceship_operator.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Previously they were silently ignored in this context (but #if defined
already worked here if you need a workaround which works for older
versions).
Fixes #2183
|
| |
| |
| |
| |
| |
| |
| | |
Go is happy with the testcase if the type is changed from int to
char, so just go with that.
See https://sourceforge.net/p/swig/bugs/983/
|
| |
| |
| |
| | |
I accidentally dropped this in 8fb15fcc922a302b88937a68e089223fb90640f9.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously we'd fail an assertion and dump core, which isn't nice:
Bad template type passed to SwigType_remember: a(std::numeric_limits< unsigned char >::max()).unsigned char
swig: ../../Source/Swig/typesys.c:1709: SwigType_remember_clientdata: Assertion `0' failed.
Aborted (core dumped)
We also now know that this situation can be triggered by particular
user inputs, so an assertion is not an appropriate check anyway.
Now we report an error and exit with non-zero status:
:1: Error: Array size expressions containing a '<' character not fully supported
The `:1:` part isn't ideal but happens because the SwigType doesn't seem
to have file:line information.
See #2486.
|
| |
| |
| |
| |
| | |
The bulk of this was already removed in
e3b112c69ceed5c39cb07fa45a3ba62b27712679.
|
| | |
|
| | |
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | | |
This is a C++ testcase so these aren't useful.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Make argc and argv test works in C.
Signed-off-by: Erez Geva <ErezGeva2@gmail.com>
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
Closes #2524
|
| | | | |
|
|/ / / |
|
| | | |
|
| | |
| | |
| | |
| | | |
Needed to get compilable code for Lua and guile.
|
|\ \ \ |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add a regression test based on https://sourceforge.net/p/swig/bugs/1163/
since this patch solves that case too.
Replace the __attribute__ test case from #2525 with a variant of the
1163 regression test, since __attribute__ is specific to certain
compilers.
Adjust the self-referential test case to actually work - it wasn't
valid C code before.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
We need to insert newlines for a multi-line macro invocation, and
we shouldn't leak memory.
|
| | | | |
|
| | | | |
|