Re: [pygccxml-development] More questions on the Ogre Binding

[Lakin W. <lak...@gm...>]

Gah!  I really need to remember to reply-all ....

Sorry roman, and the list.

Lakin

---------- Forwarded message ----------
From: Lakin Wecker <lak...@gm...>
Date: May 29, 2006 11:34 AM
Subject: Re: [pygccxml-development] More questions on the Ogre Binding
To: Roman Yakovenko <rom...@gm...>


On 5/28/06, Roman Yakovenko <rom...@gm...> wrote:
> On 5/29/06, Lakin Wecker <lak...@gm...> wrote:
> For the time being, those variables will not be exported to Python. Solut=
ion:
>
> mb =3D module_builder_t(...)
> Vector3 =3D mb.class_( "Vector3" )
> Vector3.add_code( 'add_property( "x", &Ogre::Vector3::x)' )

Yeah, something like that will work, but it would be better if py++
would export these variables automatically.  Are you planning on
fixing this?  (If so, then the rest of this letter is not necessary.)

I looked at the code causing the problem, and it's all code similar to:

class Foo{
       union {
            struct {
                    float r,g,b,a;
            };
            float val[4];
        };
};

So (if my understanding is correct), the union is unnamed, but the
union's members can be access through Foo::r, Foo::g, Foo::b, Foo::a,
and Foo::val.

It would be awesome if py++ exported these appropriately.

Lakin