GoLang:fix overload functions with polymorphic issue
del tmp files
Go: fix overload functions with polymorphic issue
Don't use C++ features when building test code as C.

This fixes the build after a6efdb7 which added a method to a test used in both
C++ and C test cases.
Revert "Don't use C++ features when building test code as C."

This reverts commit 6d93d57ab03f4c13dca65921cadc6f1e6d244cff.
Revert "Fix when is 'self' used as a parameter name in Python"

This reverts commit a6efdb7999298de6be8c5b4f1fca4ff60ac1fb20.
Fix autodoc testcase for python -builtin
Fix R Lib files and testcase failing due to new preprocessor checks

Fixes unknown preprocessor directive error introduced in #217
commit 255c929c5636f54c16261bd92b8eea2005d61b11
These were probably intended as script comments using # when C/C++
comments using // or /* */ should have been used.
Update changes file
Fix for 'self' being used as a parameter name
Fix 'self' parameter name clash when generating for Python builtin
fixes "flatnested"  feature for out-of-scope defined nested classes
Fix doc typos reported by tounsi67 in issue#260
delete unmeaningful macro
D: Fix li_boost_shared_ptr_runme.2.d compilation.

The overload of Thread.sleep taking a bare integer has been
deprecated/removed.
D: Fix allprotected_not.i compilation.

The director cycle breaking code was emitted when protectors
were not actually enabled on the parent class, leading to
swigIsMethodOverridden being called but not declared.
D: Fix preproc_constants/preproc_constants_c test cases.
D: Fix class/method name ambiguity in test-suite/c_delete.i.

There might be other cases where this happens when $dclassname
is used for code emitted into the proxy class itself, but so
far, there are none in the test suite or any bug reports.
D: Fix name collision between im D module function pointer and actual C function.

Previously, the function pointers were not only declared with
extern(C) calling convention, but actually had C linkage
themselves. Thus, they were exported under their bare names,
potentially colliding with the actual function definitions
in the wrapped library if the dynamic linker decided to
resolve them the wrong way.

This fixes the sneaky1 test case, although I have no idea why
the add() reference in D_add() (via the PLT) is rebound to the
function pointer there and not in all other test cases and
real-world libraries. As far as I can see, there don't seem to
be any special symbol visibility/binding settings involved in
our build system.
Work around D test suite failure due to issue #254.

Object is currently a D keyword for the purposes of SWIG
(that's in fact a little too strict, but Object is the root
of the class hierarchy and some parts of the code break).
'template_typedef_typedef' is supposed to test.