Change Doxygen error codes to start at 740 instead of at 720 as the latter was
taken by Scilab in the meanwhile.
Resolve conflicts in autodoc_runme.py once again.
* clang-warning-fixes:
Correct Examples makefile for guile
Suppress clang warning in testcase
preproc_constants warning suppression when using clang
Warning suppression in li_std_vector_extra testcase for clang
preproc_constants warning suppression when using clang
Modify preproc testcase to remove clang warning
Rename test warning suppressions when using clang
primitive_types testcase improvement
* stricter-warnings:
Go changes for wrappers to compile as ISO C90
Scilab typecheck typemaps fix for C90
No error for one Javascript node warning
Warning fix in testcase for Javascript node
nested_extend_c testcase fix when compiled by C++ target languages
Temporarily remove -Werror for Scilab testing
C90 fixes for Javascript JSC
There are a couple of testcases that aren't compliant and supression via pragmas doesn't work for gcc < 4.8
Warning suppression change
Scilab typemap fixes for C89
compiler warning suppression correction in testcase
Suppress pedantic warnings in C# testcases
Suppress pedantic warnings in testcases
Pedantic warning fix in testcase
pedantic warning fix for D wrappers
Travis testing to use testflags.py for setting CFLAGS and CXXFLAGS
Add travis build for error-declaration-after-statement branch
Javascript v8 and node compiles the wrappers as C++, fix this warning:
anonymous type with no linkage used to declare variable ‘<anonymous struct> THING’ with linkage
* ptomulik-fix/py-object-const:
constant_directive_runme.py and classic classes
additional fixes to %constant directive
make %constant directive to work with structs/classes
The fix for #217 means that blocks of target code delimited by { } with
'#' comments in now give errors (previously these lines were quietly
discarded).
The fix is generally to use %{ %} delimiters instead, so suggest this
might be the issue in the error message to help users hitting this issue
with wrappers which were apparently working before.
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.
