On 2/27/06, Allen Bierbaum <abi...@gm...> wrote:
> - Currently pyplusplus generates invalid bindings on class with
> virtual methods and static methods. It tries to add the static
> methods to the wrapper and things just don't work out well. IIRC the
> code doesn't even compile.
>
> - Type traits: I noticed when using the pygccxml type traits to test
> a type for const'ness that the current code only tests the most
> external type wrapper and thus doesn't really tell you if the entire
> type is const.
>
> for example a type in pygccxml may end up looking like: ref( const(
> ptr( float))))
>
> This type would only return true when tested for is_reference.
> is_const would fail. This is inconvenient and doesn't reflect the way
> boost.type_traits works on types. I think it could be solved by just
> making the type traits methods process the type recursively.
>
> - finalizing: Are there known issues with finalizing a class? I have
> run into multiple cases where I was able to finalize a class with
> Pyste but pyplusplus returns an error when attempting to finalize it.
> (I don't have a self contained example right now but I may be able to
> come up with one if needed)
Allen, I would like to fix those bugs. Can you create simple
test-cases that reproduce
those problems? Thank you.
Also, I am waiting for your answer about "finalizing". Do you agree with me=
?
Thanks
--
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/
|
