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

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

On 7/28/06, Allen Bierbaum <al...@vr...> wrote:
> This sounds like a great idea.  I like the idea of the interface and how
> you specify that arguments should be used in what way.  Please let me
> know if you need help testing or migrating this to Roman's interface in
> pyplusplus.

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
4. custom user policies[ precall, call, postcall ]
4.1 what are performace penalties?
5. what should be done for [pure]virtual functions
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.

Lack of time is the main reason I didn't implement it until now. I
don't have time
to answer all those questions and analize the usecases.

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