For templates only, the template parameters are fully resolved when
handling typemaps. Without this, it is too hard to have decent rules
to apply typemaps when parameter types are typedef'd and template
parameters have default values.
Fixes %clear for typedefs in templates, eg:
%typemap("in") XXX<int>::Long "..."
template typename<T> struct XXX {
typedef long Long;
};
%clear XXX<int>::Long;
as the typemap was previously incorrectly stored as a typemap for long
instead of XXX<int>::Long.
* fflexo-javalist:
Java std::vector minor improvement
Fix Java container tests for change in vector constructor declaration
Add in missing Java std::list listIterator index range checking
Minor correction in C# std::list doNextIndex
Add missing typedefs to Java std::vector
Consistent destructor declarations
Remove Java std::list::max_size
Java std::list std::vector - test addAll and subList
Handle length_error exceptions in Java std::vector::reserve
Remove Java std::list::assign
Additional add/remove methods added to Java std::list wrappers
More efficient add implementation for Java std::list
Java std::vector std::list: add missing exception handling
Java std::vector std::list enhancements
Modify std::list declarations to match the C++ standard
Fix removing elements from std::list Java wrapper
Improve Java std::list std::vector runtime tests and wrap std::list::clear
Wrap std::list::empty as isEmpty in Java
javabase typemap improvement for std::list
Java std::list - fully qualifiy Java class name to avoid potential name ambiguity
cosmetics
Remove redundant code
Java std::list rework to be consistent with std::vector wrappers
li_std_list testcase not working for most languages
re-enabled li_std_list test
Switched from autobox to jboxtype per #842
Document autobox.i
Made the conversion from long->int for size_type mapping onto Java interfaces cleaner.
Be consistent in semantics of %extend on std::list::iterator
Comment on consideration of making iterator non-static.
Java style fix: iterator->Iterator
Moving iterator functionality into nested Java class now.
Removed typedef from li_std_list test as it's not expected to work properly in templated code
Added a best case workaround for std::list::size_type vs jint problem. There's a bit of commentry added around it too for clarity.
Drop non-const reference from autobox typemap macro to be consistent.
just use a forward declaration for C++ iterator types to fix enum errors
Added enum to li_std_list tests
Added li_std_list to the Java test-suit makefile
added more comments in a few places
Base _runme.java for li_std_list off li_std_vector_runme.java
Expose more types from li_std_list.i
Don't expose sort() to avoid adding dependencies on all std::list users
Target each method specificly for setting modifiers
Don't expose remove() method from std::list to avoid confusing it with Java's remove() in List
- added std_list.i implemenatation that extends Java's AbstractSequentialList base class - added autobox.i that provides supporting typemaps for generics in containers
- Add missing vector copy constructor
- Add constructor to initialize the containers. Note that Java's
equivalent constructor for ArrayList just sets the capacity, whereas
the wrappers behave like the C++ constructor and set the size. I've
done this mainly because there has been a vector(size_type) constructor
in the Java wrappers for many years, so best to keep this unchanged.
1. Fix negative octals. Currently not handled correctly by `-py3`
(unusual case, but incorrect).
2. Fix arguments of type "octal + something" (e.g. `0640 | 04`).
Currently drops everything after the first octal. Nasty!
3. Fix bool arguments "0 + something" (e.g. `0 | 1`) are always
"False" (unusual case, but incorrect).
4. Remove special handling of "TRUE" and "FALSE" from
`convertValue` since there's no reason these have to match
"true" and "false".
5. Remove the Python 2 vs. Python 3 distinction based on the
`-py3` flag. Now the same python code is produced for default
arguments for Python 2 and Python 3. For this, octal default
arguments, e.g. 0644, are now wrapped as `int('644', 8)`. This
is required, as Python 2 and Python 3 have incompatible syntax
for octal literals.
Fixes#707
* tamuratak-fix_ruby_wstring:
[ruby] use %fragment to clarify the dependency of code.
[ruby] should initialize static variables inside %init{}, in which it will not be excuted concurrently by multiple threads.
[ruby] * use static variable to avoid creating stirngs every time. * fix possible overflow.
[ruby] add std::wstring tests for string including a null terminator.
[ruby] * rewrite SWIG_AsWCharPtrAndSize and SWIG_FromWCharPtrAndSize * use UTF-32LE and UTF-16LE to avoid BOM * add tests
[ruby] use WCHAR_MAX to determine the encoding of std::wstring.
[ruby] add a few tests for std::wstring
[ruby] fix support for std::wstring.
This ensures NotImplemented is returned on error so that the Python
interpreter will handle the operators correctly instead of throwing an
exception. NotImplemented was not being returned for non-builtin wrappers
when the operator overload did not have a function overload.
See PEP 207 and https://docs.python.org/3/library/constants.html#NotImplemented
Mentioned in SF patch #303 and SF bug #1208.
"." was removed from @INC in Perl 5.26 for security reasons, and has
also been removed from older versions in some distros.
Fixes https://github.com/swig/swig/issues/997 reported by lfam.
* vadz-java-vector:
Fix potential STL std::vector wrappers <: digraphs problems.
Add runtime checks for vector size in Java
Make std::vector<> wrappers conform to List interface in Java
Add helper macro to avoid duplication in Java vector typemaps
Conflicts:
CHANGES.current
For shared_ptr proxy proxy classes, add a protected method swigSetCMemOwn for modifying
the swigCMemOwn and swigCMemOwnDerived member variables which are used by various other
methods for controlling memory ownership.
Closes#230Closes#759
* vadz-csharp-complex:
Add header to std_complex.i
Fix linkage problems in C# std::complex wrappers
C# std::complex wrappers marshalling by value
C# std::complex wrappers SwigValueWrapper fix
Use %naturalvar for C# std::complex wrappers
Allow avoiding generation of unwanted std::complex<T> typemaps
Also apply csvar{in,out} typemaps to std::complex references
Add std_complex.i for C# too
Extend C# complex support to member variables of this type
Add support for std::complex<> to C#
Use new unified Mono mcs compiler if available under Unix
