| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Issue reported by Carlos Frederico Biscaya on swig-user mailing list.
|
|
|
|
| |
Based on Ruby's li_std_pair_runme.rb
|
|\
| |
| |
| |
| |
| | |
* directors-comparison-operators:
Use %rename
Fix wrapping of virtual comparison operators with directors
|
| | |
|
| |
| |
| |
| | |
Closes #1642.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Reportedly failing. Failure can be replicated with 2.5.1 by increasing
number of loops.
Workaround is to disable GC.
Closes #1646
|
|\ \
| |/
|/|
| |
| |
| | |
* python-doxygen-quotes:
Fix generated Python code for Doxygen comments with triple quotes
Fix generated Python code for Doxygen comments ending with quote
|
| |
| |
| |
| |
| |
| |
| |
| | |
In addition to the changes in the previous commit, also avoid syntax
errors in the generated Python docstrings by splitting them into several
parts if there are 3 quotes in a row in the input, as it's impossible to
have them inside triple-quoted strings, generally speaking (i.e. if
there are occurrences of both """ and ''' inside the string).
|
| |
| |
| |
| |
| |
| | |
Single-line Doxygen comments ending with a double quote resulted in
syntactically-invalid Python docstrings in the output, so use triple
single quotes as delimiters in this case to avoid it.
|
|\ \
| | |
| | |
| | |
| | |
| | | |
* r-script-fixes:
Fix further missing semicolons in R code.
fixed some missing semicolons. Each one caused a compile error in generated code
|
| |/
| |
| |
| | |
Fixes errors in R code when using -small as this option causes lines to be joined.
|
| | |
|
|\ \
| | |
| | | |
Fix for missing space after \endlink in doxygen
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The "endlink" command is processed in processWordCommands, which by
default skips space occuring after the command, which is intended for
removing leading space from a command argument. For "end" commands,
we don't want to do this. Note that certain end commands such as
"endcode" aren't processed by processWordCommands (believe
addCommandUnique ends up handling them).
Update usage of \link in doxygen_translate_all_tags.i to test handling
of space after \endlink.
Tweaking some of the usage in doxygen_misc_constructs.i to remove what
seems to be an extra space from the input (otherwise we would need to
add an extra space to the expected output).
|
|/
|
|
|
|
|
|
|
| |
This error is given for any use of variable called "l" (and also "I" and
"O", but we don't seem to have any of those) and it doesn't seem to be
worth changing this variable name in the tests code, as it's really not
that meaningful there anyhow, so just disable the warning to let the CI
builds, which now use pycodestyle 2.6, instead of 2.5 which didn't have
this error and which is still the latest available in Debian Sid, pass.
|
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
* abstract-conversion-operators:
Add test cases for abstract user-defined conversion operators
Recognize C++ conversion operators with trailing '= 0' as abstract
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
This test code tests the upcast code:
swig_assert_equal_simple(-1, base_num2([Derived(7)]))
Although there is no explicit memory leak fix test, it does at least run the code.
Handling of None needs fixing in Python (it is working in Ruby)
Note that the Ruby implementation has a partial template specialization
for shared_ptr, whereas the Python implementation is in the generic
code!
Issue #1512
|
|
|
|
|
|
|
|
|
|
| |
Don't attempt to use the class's __dict__ for setting 'this' when
a user has extended a class with:
__slots__ = ['this'].
Was segfaulting. Now we fall back to a simple PyObject_SetAttr if the
usual approach to setting 'this' in __dict__ does not work.
Closes #1673 Closes #1674
|
| |
|
|\
| |
| |
| |
| | |
* ruby-autoptr:
Extend std::auto_ptr<> support to Ruby
|
| |
| |
| |
| |
| |
| | |
This is trivial as exactly the same typemap as for Python can be used
for Ruby too, all the differenced are abstracted by the unified typemap
library.
|
|\ \
| | |
| | |
| | |
| | | |
* autodoc-doxygen-fix:
Fix crash in Python backend when using empty docstrings
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Due to confusion in build_combined_docstring(), we could call
DohDelete() on the "feature:docstring" string, which resulted in a crash
when trying to use it later.
Fix this and simplify the code at the same time by ensuring that we
always use a copy of "feature:docstring" if it's not empty or don't use
it at all if it's empty -- like this we don't have to check for its
length each time before using it.
Closes #1648.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There is a possible memory leak in case the SWIG_exception_fail macro
is called. The problem is related to its definition that call the
function Rf_warning. This function (as well as Rf_error) involves
a longjmp over C++ destructors on the stack. Thus, all the objects
allocated on the heap are not freed.
Closes #914
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* RMemberListTrialSimplify2019:
ENH R abstract_access_runme
ENH R accessor processing test
Removed some remaining commented sections
moved registration routine and use swig_name_get
calling Swig_name_setget
Used Swig_name_register so that Swig_name_wrapper produces the correct name without a separate replace call.
Removed last instance of using Strcmp to check for a set/get method. Replaced with check for flag.
Alternative version of using memberlist processing. This clarifies the logic within OutputMemberReferenceMethod by filtering the lists into classes, rather than doing it internally. Code isn't any shorter.
commenting out unused code
first pass at removing string comparisons for set/get methods
trial changing member list processing
|
| | | |
| | | |
| | | |
| | | | |
Improved the exception handling components of test.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Test of accessors generated via the new internal structures.
This test confirms that the old incorrect accessors are not
present and runs the correct version, confirming the values.
|
| |/ /
|/| | |
|
| | | |
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* shared-ptr-template-upcast:
comments
Applying shared_ptr template upcast fix to CSharp, adding CSharp test, and cleanup
Adding test case demonstrating issue where SWIG does not generate a correctly typed, upcasted shared_ptr for a template instantiation deriving from a base class
WIP - Use the non-encoded type string for upcasting a shared_ptr of a derived type to a shared_ptr of the base type
comments
Applying shared_ptr template upcast fix to CSharp, adding CSharp test, and cleanup
Adding test case demonstrating issue where SWIG does not generate a correctly typed, upcasted shared_ptr for a template instantiation deriving from a base class
WIP - Use the non-encoded type string for upcasting a shared_ptr of a derived type to a shared_ptr of the base type
|
| | | |
|
| | |
| | |
| | |
| | | |
cleanup
|
| | |
| | |
| | |
| | | |
correctly typed, upcasted shared_ptr for a template instantiation deriving from a base class
|
| | |
| | |
| | |
| | | |
parameter support
|
| | | |
|
| | |
| | |
| | |
| | | |
See 66a78261924174791a4952d05b58d52c16a36a57
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
* Issue-1643:
Fix pydoc null pointer dereference with missing arg type
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Processing doxygen @param comments for a parameter whose name did not
appear in the function declaration would cause a segfault due to a
null pointer dereference.
Adding test cases for both variadic function (no specified arguments)
and @param comment that references an argument that is not named in
the function prototype. Both of these cases previously segfaulted.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* Issue-1632:
Minor workaround in doxygen_basic_translate_style3 test
Add new test doxygen_basic_translate_style3.i
Fix for newline handling in doxygen "///" style comments
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
With the "///" doxygen comment style, comments within a code block do
not get handled correctly. Modifying the test to remove this case and
adding a note about it for future reference.
|
| |/ / /
| | | |
| | | |
| | | |
| | | | |
This is used to test the "///" style of doxygen comments. Previously,
newlines in these doxygen comments were not handled correctly.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixes:
./director_string_runme.java:53: warning: [deprecation] Integer(int) in Integer has been deprecated
|
|\ \ \ \
| | | | |
| | | | | |
Fix doxygen crash with empty comment (Issue #1647)
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Parsing "/**/" with -doxygen would result in a crash due to
calculation of comment start/end that does not work for an empty
comment. Fixed by catching this case prior to processing. Added
simple regression test to doxygen_basic_translate.
|
| | | |
| | | |
| | | |
| | | | |
See 66a78261924174791a4952d05b58d52c16a36a57
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* doxy/commands:
Update documentation for doxygen tags
Fix doxygen translation of \p command for python
Fix doxygen handling of \em tag for python
Minor formatting updates to doxygen docs
Reformat tag lists in doxygen documentation
Add doxygen_code_blocks_runme.java
Special handling for python doctest code blocks
Add new doxygen test doxygen_code_blocks
Handle doxygen code command with language option
Improve doxygen parser handling of \code content
Flag optional arguments in doxygen pydoc output
Add parameter direction to doxygen pydoc output
Support doxygen \param[] commands
|