Re: [pygccxml-development] Auto-wrapping methods taking non-const reference

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

Roman Yakovenko wrote:
> I don't see any problems to add such functionality to py++. But I'd
> like to see the
> whole picture first:
> 1. Immutable arguments could be in, out, inout.
> 2. pointers to fundamental types:
>        could be arrays with different size policy
> 3. status as exception

All of the above is entirely dealt with in the policy object.

> 4. custom user policies[ precall, call, postcall ]
> 4.1 what are performace penalties?

The inserted code is C++ code, so I don't expect any severe performance 
penalties (it's probably the same code that a user would write when 
creating the bindings manually).

> 5. what should be done for [pure]virtual functions

I haven't dealt with this question in pypp_api..... what problems do we 
have to expect in this case?

> 6. Another valid question: why do you to insert such functionality into 
> core of
>   py++? I am not sure that big monolitic core is a good idea. Making py++
>   better support plug-ins could be a better idea.

I don't understand this point. In what way is the current implementation 
of pyplusplus less monolithic? Isn't it rather the opposite? Currently, 
the code generated by the calldef code creators is more or less fixed, a 
user cannot add his own code. Instead, he has to replace the entire code 
creator object. But if there's a mechanism like the one used for the arg 
policies in pypp_api you could add your own C++ code (that may be 
located outside pyplusplus) to the generated function without having to 
replace the entire function body.

- Matthias -