Re: [pygccxml-development] problem with an array of pointers

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

On Tue, Jul 8, 2008 at 4:31 AM, Gordon Wrigley <gor...@gm...> wrote:
> OK, that seems to make some sense, but leads to a few lil feature requests.
>
> First the py++ code on that page is overly verbose, it would be nice if this
> could be handled in one line. So for this C++ code:
>
> class tom
> {
> public:
>   double *data;
>   double dataLen;
>
> you might have something like:
>
> mb.class_( "tom" ).variable( "data" ).size("tom.dataLen")
>
> I realise it's probably not going to be quite that simple, I'm just trying
> to convey the direction of the idea.

Interesting idea. I will try it.

> Also if you had a standard policy of
> always having a xLen variable for every x pointer variable (or xLen function
> for every function returning a pointer) then it'd be nice to be able to
> capture that in a single line.
>
> And of course this would all have to be extended somehow to work with my
> array of pointers example and the documentations width*heigh example.

:-). Adding support for 2 dimensions array is on my todo list.

> Also that warning that py++ should give when it runs into one of these
> should include an example of the sort of line required to fix it.

I will fix it before next release

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