Write inititializations in topological order

Add methods to various places in the hierarchy so that the generator can
access the topologically ordered class list (in addition to the
unordered class list). Modify CppGenerator::finishGeneration to use
this.

This fixes a failure to correctly create Python wrapper classes due to
subclass wrappers being initialized before their base class (with the
result that the looked-up type object for the base class is null,
causing the derived class to be created without referencing the base).
Also change one of the test cases to test that we correctly wrap a
typedef of a template class derived from a non-template base (which was
failing before this change for the aforementioned reason).

Change-Id: Ib4dc2626a41cb7bb905ff4a302c2613ea12d026b
Reviewed-by: John Cummings <jcummings2@users.sf.net>
Remove useless code.

Remove code to set the type entry base container type in
AbstractMetaBuilder::setupInheritance outside of setting up the
container meta class. We do it anyway when the meta class is found, and
fail if we can't find the meta class, so having just the type entry set
is not really useful. (And this will allow us to simplify the code going
forward.)

Change-Id: I90389efc574d516703df0d6a26ba130769adfea7
Reviewed-by: John Cummings <jcummings2@users.sf.net>
Refactor and improve added function resolving

Add a public function to create an AddedFunction::TypeInfo from a
signature string. Change translateType to use this to do full recursive
resolution on template arguments. Create a new helper function to do
more intelligent parsing of template type name signatures, and use this
in translateType.

Taken together, this means that we now recognize both multiple arguments
to template types of added functions, as well as template arguments that
are themselves template types. We couldn't do this before due to the use
of a regular expression to attempt to separate the template type name
from its arguments. The test cases are updated to test these new
features.

Note, however, that it is now a fatal error if the template argument
type cannot be determined. (Before we would just drop it and treat the
type as a non-container.) However, 1) this should not be happening in a
well formed type system, and 2) it's questionable if things wouldn't
have fallen apart anyway from treating the presumed container as
something else.

Change-Id: I23c3a7f7e311e046642d951d6ad2236571fda6b8
Reviewed-by: John Cummings <jcummings2@users.sf.net>
Revert "Remove useless code."

This reverts commit 02c6e63ac8dbb8acde3bc19abd36fff0db65fd11. Apparently
types derived from containers can have a container base class without
the container class having a metaclass.

This fixes the sample_strlist unit test crashing. (There may be another
bug here, in Shiboken's don't-write-generated-source-if-not-changed
logic, as the failure doesn't seem to reliably appear/disappear after an
incremental build.)

Change-Id: I5f60bfb784dca02d9766a32e7b7b8a8a529df5af
Reviewed-by: John Ehresman <jpe@wingware.com>
Fix finding container base classes

Move logic to find template classes to its own helper method, and newly
use the helper in AbstractMetaBuilder::getBaseClasses. This fixes the
latter not finding template base classes, which fixes class topological
sorting in some cases.

Unfortunately I have not figured out a reliable unit test for this,
although printing a debug warning when finding the parent fails (or when
a template lookup succeeds) is able to verify that this change is doing
something useful.

Change-Id: I2a5e0df4035393288b6f69ebc41dc0e64866a182
Reviewed-by: John Cummings <jcummings2@users.sf.net>
Don't warn when inheriting from container

Change AbstractMetaBuilder::setupInheritance to not warn about classes
that inherit from known container types, even if the container type does
not have a corresponding wrapper class (which in many or most cases it
won't). Remove now-unneeded suppression for the same in 'sample'.

Change-Id: I0a45636791eba36cf070ea082eb6ead6cb5947ef
Reviewed-by: John Cummings <jcummings2@users.sf.net>
Fix 'special' include handling

Fix handling of includes like '#include BOOST_USER_CONFIG'. This was
failing due to an obvious logic error in how the preprocessor tests if
the expanded symbol looks like an include file location.

Change-Id: Ia085e5c081078d328d6fc84ff2a99681913a30b9
Reviewed-by: John Cummings <jcummings2@users.sf.net>
Fix buffer overrun processing macro definitions

Fix potential buffer overrun (__first iterator becomes > __last and
starts processing garbage) when parsing macro definitions that would
occur if a macro definition ends in a comment. This would cause the
macro definition to contain incorrect content or even outright garbage
(i.e. random memory) if the trailing comment is at the end of the file,
as in boost/type_traits/detail/type_trait_def.hpp. In this worst case,
the macro expansion could contain a NUL byte which would cause parsing
to prematurely halt at the point of expansion.

Change-Id: I94ded39d9a20dc9510d827bc18adb2dc1bad17f0
Reviewed-by: John Cummings <jcummings2@users.sf.net>
Only use fields in PyTypeObject when defining types

Allocate and use separate structures for as_* fields in the PyTypeObject
rather than using fields in the PyHeapTypeObject.  This is a step
away from using the PyHeapTypeObject, which is unnecessary and will
make supporting stackless python easier.

Change-Id: I6e5c514ab6db5b8bee9bee3107b97d6fbd582641
Reviewed-by: Christian Tismer <tismer@stackless.com>
Reviewed-by: John Cummings <jcummings2@users.sf.net>
Fix compilation issue on OS X 10.9

Starting with OS X 10.9 the system toolchain defaults to libc++.
This is a problem with the current sparse hash config as it defaults
to using  c++11 functionality under the std::tr1 namespace instead
of std, which fails for libc++ since it does not implement the tr1
namespace. This change allows libc++ based systems to use the correct
namespace.

Change-Id: Ia8dd49fb5fad2915f41e44240e45a7af9d6453a8
Reviewed-by: John Ehresman <jpe@wingware.com>
Fix for containers with 'const' values

Fix omission of 'const' specifier when generating binding code for
containers whose value type is 'const', which would lead to binding code
that does not compile due to 'const' mismatch. Includes test case.

Change-Id: Iff99a16ee071bb255f78e86e2456e5206cc00cfb
Reviewed-by: John Cummings <jcummings2@users.sf.net>
doc: Stop requiring sphinx.ext.refcounting.

Sphinx 1.2 made a backwards-incompatible change and removed its
`refcounting' extension module because it "is very specific to CPython
and has no place in the main distribution".

Fix the build with Sphinx 1.2+ by not requiring it in conf.py.in; we were
not using it before anyway (the `refcount_file' variable was not set) and it
was likely added by default when the configuration file was generated.

Change-Id: I6c775fb4c1c2daae25aade68079efc2e77225a0f
Reviewed-by: John Ehresman <jpe@wingware.com>
Fix building with python 3.3 and 3.4.

FindPython3Libs.cmake lists hardcoded versions of python3 to look for,
which include up to python 3.2.

Added python 3.3 and 3.4 to this list so that building on these versions
works.

A better solution would be ideal in future, so as to avoid having to
add python versions to this list as time passes. However, this fixes
the issue for now.

Change-Id: I9c113f70164c30dc3a94a5c946facbc38901f68e
Reviewed-by: John Ehresman <jpe@wingware.com>
Fix function rejections (i.e. support overloads)

Add an additional check to AbstractMetaBuilder::traverseFunction to also
perform a quick-and-dirty construction of the function signature, and to
check that against the rejections. Add a unit test for matching full
signatures.

Before, we were only testing the function name; as a result, a rejection
like 'foo()' would never match (because the name does not have ()'s).
This is especially helpful for rejecting specific overloads of functions
while allowing others to be wrapped normally. (The unit test shows a
not-so-far-fetched example why one might want to do this.)

The signature building logic isn't very sophisticated and likely
requires a very exacting match to the signature as it appears in the
wrapped sources, but that's likely not a serious issue, and at any rate
this is much better than not being able to match overloads at all.

Change-Id: Ic686377477aacf54f79c7bd2013e9aea8521a4ea
Reviewed-by: John Ehresman <jpe@wingware.com>
Add parsing of 'noexcept' keyword

Teach Shiboken to parse the 'noexcept' keyword. This doesn't add any
features (and we only support unconditional 'noexcept' for now), but
addresses an internal error that causes shiboken to SEGV trying to parse
modern versions of boost::intrusive_ptr. A test case to replicate the
crash (without the other changes) is also added.

Change-Id: I4713593dfd189c02ef4a2d7447d785b6d378019c
Reviewed-by: John Ehresman <jpe@wingware.com>
Remove protected from samblebinding test

The protected sections triggered a generation bug when avoiding
the protected hack

Change-Id: I6346cdb74a25f1ddf49263d9f74670a3b105b07a
Reviewed-by: Matthew Woehlke <mw_triad@users.sourceforge.net>
Reviewed-by: Roman Lacko <backup.rlacko@gmail.com>
Remove rejection lines that cause the sample_list test to fail

These functions (except createComplexList) are are needed by the test.
Prior to 5b39f7fd9e21, the rejections were not being recognized; removing
them returns the wrappings to their previous state and allows the test to
pass again.

Change-Id: I3efb08383b2d59f9917a4e4a0200e0516db9c83e
Reviewed-by: Matthew Woehlke <mw_triad@users.sourceforge.net>
Reviewed-by: John Ehresman <jpe@wingware.com>
Version bump

Change-Id: I4da6558dfa2dd2aaae6343d2363b7fcfc7786f45
Reviewed-by: John Cummings <jcummings2@users.sf.net>