Using { and } to delimit means Python comments will cause errors with
SWIG 3.0.3 and later. With older SWIG it usually just meant such
comments failed to appear in the generated output. See issue #221.
Default values are no longer generated as Python code by default.
They must be explicitly turned on using the "python:defaultargs" feature.
Closes#294Closes#296
The problems in these two issues when "python:defaultargs" is turned
on still need to be fixed and should be addressed in separate patches.
The important thing is the default code generation is now fixed.
when the end of the file is reached, report it at the start line rather
than "EOF" as then tools like editors and IDEs will take you to a
generally more useful place for fixing the problem.
Support for -stat was removed in SWIG 1.3 Alpha 1 nearly 15 years ago,
and the documentation options were removed prior to that, so issuing a
warning that they are deprecated and ignoring them serves no useful
purpose now.
Provide -cppext as a general command line option for setting the
extension used for generated C++ files (previously it was specific
to the PHP backend). Deprecate the equivalent -suffix option
provided by the Ocaml backend, but continue to support that for
now.
I believe the aim is to keep these below 2KB to avoid string literal
length limits on some compiler, but they slowly creep up in size, so
split into more chunks and rebalance the contents.
$* is subject to word-splitting and pathname expansion, whereas "$@"
expands to each parameter as a separate quoted word.
Some ancient shells expand "$@" to "" if there are no parameters, but
that isn't really a concern here as running swig without arguments isn't
useful.
* Fixesswig/swig#266.
* Added links to working examples.
* Added link to runtime.SetFinalizer documentation.
* Added recommendation to read the runtime.SetFinalizer documentation before using it.
* Clarified that C++ objects ownership is not tracked and thus objects need to be freed manually.
