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

[Roman Y. <rom...@gm...>]

On 7/29/06, Matthias Baas <ba...@ir...> wrote:
> I haven't dealt with this question in pypp_api..... what problems do we
> have to expect in this case?

We change the signature of the method, it could no be overridden from Python.

> > 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.

This is just a thought.

> In what way is the current implementation
> of pyplusplus less monolithic? Isn't it rather the opposite?

You are right. The question is whether it should stay to be like this or not.
But this question was a theoretical one.

> 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.

:-). Before I will start to implement(== to port from pypp_api ) this
feature I will
write some paper. So anyone( especially you ) can comment it. Wiki
could be a good platform to discuss these things, right?

-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/