Re: [pygccxml-development] Two problems

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

I'll look into adding the same functions to Matrix4.  I'm sure Ogre
will accept the patch.  However, in the mean time I can avoid those
functions ...

In the end I'd like to have a more pythonic way of accessing
Matrix{4|3}, Vector{4|3|2}, Quaternion, and ColourValue ....
basically by interchanging python lists/tuples etc.

Thanks

Lakin

On 5/31/06, Roman Yakovenko <rom...@gm...> wrote:
> On 5/31/06, Lakin Wecker <lak...@gm...> wrote:
> > In finishing the Ogre bindings, I have run into two problems (one is
> > caused by the other).
> >
> > 1. First, I get an error when compiling Matrix4.cpp ..
>
> I think, that the error caused by exported operator[].
>
> By the way in this case call policies could be
> return_inernal_reference, but ....
> There is another problem here:  those functions have next return type:
> [const] float *. The expression float* could not be translated to
> Python and manual
> wrapper is required. I took a look on Matrix3 class, it defines [S|G]etColumn.
> functions that returns Vector3 class. May be it will be possible to
> add such functions
> to Matrix4 class [G|S]Column and [G|S]Row?
>
> ( By the way I commeted the fix right now )
>
> --
> Roman Yakovenko
> C++ Python language binding
> http://www.language-binding.net/
>