Re: [pygccxml-development] Future freeze

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

On 10/10/06, Allen Bierbaum <al...@vr...> wrote:
> Roman Yakovenko wrote:
>
> > On 10/10/06, Allen Bierbaum <al...@vr...> wrote:
> >
> >> Any hints at what other things
> >> will make Py++ create wrappers?
> >
> >
> > http://svn.sourceforge.net/viewvc/pygccxml/pyplusplus_dev/pyplusplus/decl_wrappers/class_wrapper.py?view=markup
> >
> >
> > Take a look on is_wrapper_needed method
> >
> Thanks.  That is a very helpful method. :)
>
> I understand most of the reasons in there, but I don't understand any of
> the member variable reasons.  Why does a bitfield, T*, T&, or array
> member variable require a wrapper to be created?

bitfield - you can not take reference to the bit, get\set functions are needed
T*, & - you should instruct Boost.Python how to manage life time of
the variable - you
    have to suppy call policies
array - boost.python does not supoprt arrays, so there is a need to
construct instance
of the class that exposes array to Python.


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