Re: [pygccxml-development] Code freeze

[Matthias B. <ba...@ir...>]

Roman Yakovenko wrote:
>> that, I have only tested a fraction of the bindings so far (I'm still
>> expecting to encounter methods that have been wrapped without errors but
>> that actually cannot be called in Python (like image.getSize()).
> 
> I can help you a little. If you define the functions that could not be
> called from
> Python I will write some code, on decl_wrappers, that will identify
> such functions.
> So it will be easy to search them.

Well, any function that has a non-const reference or pointer as argument 
is a potential problematic case that has to be reviewed by the user.
Maybe it would be useful if pyplusplus could already give an estimate on 
whether a case is really problematic or not. One thing that could 
influence this is whether the type of the argument refers to a basic C++ 
type or a compound type. I think if an argument of type "int&" is 
encountered then it is quite likely that this variable is really used as 
an output variable whereas I'd not be so sure anymore if the type is 
"MyClass&".

>> If I find some time, I'll update my "alternative" driver script that
>> uses the official module_builder_t class and see if I can get it to
>> generate the bindings as well.
> 
> If I can have Maya sdk I would like to do it. Please contact me
> privately if you want.

Well, Maya is a commercial application so I cannot pass around the SDK. 
But I could send you the current version of my driver script that 
generates the extension module if you want. You won't be able to 
actually run it, but you can see how the bindings are created and check 
how these things would have to be rewritten using module_builder_t.

- Matthias -