Fix the type resolver algorithm.

The new algorithm do the following:

- Try to use type_info on the object the get the object real name.
- Try to find a type resolver with the name returned by type_info.
- If a type resolver was found, get the python type.
- Else, ask binding manager to resolve the type walking on all possible
  subclasses found in the inheritance tree.

The binding manager has a graph representing the class inheritance tree.

Note: This commit break the libshiboken ABI, but not the API.

Reviewer: Luciano Wolf <luciano.wolf@openbossa.org>
          Renato Araújo <renato.araujo@openbossa.org>

1 files changed, 3 insertions, 0 deletions

diff --git a/libshiboken/bindingmanager.h b/libshiboken/bindingmanager.h
index 150baa90a..dd18dcdc1 100644
--- a/libshiboken/bindingmanager.h
+++ b/libshiboken/bindingmanager.h
@@ -42,6 +42,7 @@ namespace Shiboken
 {
 
 struct SbkBaseWrapper;
+struct SbkBaseWrapperType;
 
 class LIBSHIBOKEN_API BindingManager
 {
@@ -73,6 +74,8 @@ public:
         transferOwnershipToCpp(reinterpret_cast<SbkBaseWrapper*>(wrapper));
     }
 
+    void addClassInheritance(SbkBaseWrapperType* parent, SbkBaseWrapperType* child);
+    SbkBaseWrapperType* resolveType(void* cptr, SbkBaseWrapperType* type);
 private:
     ~BindingManager();
     // disable copy