pygccxml-development

[pygccxml-development] Code freeze

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

Hi.

Matthias do you agree/ready/have time to do code freeze and join our effort=
s?

Do you have some time for online conversation at the end of this week?

I will try to study your code in order to prepare list of essential
differences.
Can you do the same with my code?

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

Re: [pygccxml-development] Code freeze

[Matthias B. <ba...@ir...>]

Roman Yakovenko wrote:
> Matthias do you agree/ready/have time to do code freeze and join our efforts?
> 
> Do you have some time for online conversation at the end of this week?
> 
> I will try to study your code in order to prepare list of essential
> differences.
> Can you do the same with my code?

I'm still busy getting the Maya bindings into their final shape. The 
status object to exception conversion is still missing, there are still 
some entire classes missing and some individual classes require manual 
customizations, so there's still a lot of work to do. And apart from 
that, I have only tested a fraction of the bindings so far (I'm still 
expecting to encounter methods that have been wrapped without errors but 
that actually cannot be called in Python (like image.getSize()).

At the moment, I'm fine with the current status of pyplusplus. There are 
currently no things that prevent me from going on with the Maya bindings 
(there are still a number of smaller things I'd like to see fixed for a 
1.0 version, but at this point these are only of second priority).

If I find some time, I'll update my "alternative" driver script that 
uses the official module_builder_t class and see if I can get it to 
generate the bindings as well.

What are the things you want to discuss before doing a release? As I 
said above, everything works fine for me at the moment, so you can just 
go ahead and do the release. Feel free to take anything from the 
experimental module that you would also like to see in the official version.

- Matthias -

Re: [pygccxml-development] Code freeze

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

On 3/30/06, Matthias Baas <ba...@ir...> wrote:
> Roman Yakovenko wrote:
> > Matthias do you agree/ready/have time to do code freeze and join our ef=
forts?
> >
> > Do you have some time for online conversation at the end of this week?
> >
> > I will try to study your code in order to prepare list of essential
> > differences.
> > Can you do the same with my code?
>
> I'm still busy getting the Maya bindings into their final shape. The
> status object to exception conversion is still missing, there are still
> some entire classes missing and some individual classes require manual
> customizations, so there's still a lot of work to do. And apart from
> that, I have only tested a fraction of the bindings so far (I'm still
> expecting to encounter methods that have been wrapped without errors but
> that actually cannot be called in Python (like image.getSize()).

I can help you a little. If you define the functions that could not be
called from
Python I will write some code, on decl_wrappers, that will identify
such functions.
So it will be easy to search them.

> At the moment, I'm fine with the current status of pyplusplus. There are
> currently no things that prevent me from going on with the Maya bindings
> (there are still a number of smaller things I'd like to see fixed for a
> 1.0 version, but at this point these are only of second priority).

I am glad to read this.

> If I find some time, I'll update my "alternative" driver script that
> uses the official module_builder_t class and see if I can get it to
> generate the bindings as well.

If I can have Maya sdk I would like to do it. Please contact me
privately if you want.

> What are the things you want to discuss before doing a release? As I
> said above, everything works fine for me at the moment, so you can just
> go ahead and do the release.

Nothing special, I just wanted to close the gaps.

>Feel free to take anything from the
> experimental module that you would also like to see in the official versi=
on.

Thank you. I will do that.

I hope next week I will release technology preview version.

> - Matthias -


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

Re: [pygccxml-development] Code freeze

[Matthias B. <ba...@ir...>]

Roman Yakovenko wrote:
>> that, I have only tested a fraction of the bindings so far (I'm still
>> expecting to encounter methods that have been wrapped without errors but
>> that actually cannot be called in Python (like image.getSize()).
> 
> I can help you a little. If you define the functions that could not be
> called from
> Python I will write some code, on decl_wrappers, that will identify
> such functions.
> So it will be easy to search them.

Well, any function that has a non-const reference or pointer as argument 
is a potential problematic case that has to be reviewed by the user.
Maybe it would be useful if pyplusplus could already give an estimate on 
whether a case is really problematic or not. One thing that could 
influence this is whether the type of the argument refers to a basic C++ 
type or a compound type. I think if an argument of type "int&" is 
encountered then it is quite likely that this variable is really used as 
an output variable whereas I'd not be so sure anymore if the type is 
"MyClass&".

>> If I find some time, I'll update my "alternative" driver script that
>> uses the official module_builder_t class and see if I can get it to
>> generate the bindings as well.
> 
> If I can have Maya sdk I would like to do it. Please contact me
> privately if you want.

Well, Maya is a commercial application so I cannot pass around the SDK. 
But I could send you the current version of my driver script that 
generates the extension module if you want. You won't be able to 
actually run it, but you can see how the bindings are created and check 
how these things would have to be rewritten using module_builder_t.

- Matthias -

Re: [pygccxml-development] Code freeze

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

On 3/30/06, Matthias Baas <ba...@ir...> wrote:
> Well, any function that has a non-const reference or pointer as argument
> is a potential problematic case that has to be reviewed by the user.
> Maybe it would be useful if pyplusplus could already give an estimate on
> whether a case is really problematic or not. One thing that could
> influence this is whether the type of the argument refers to a basic C++
> type or a compound type. I think if an argument of type "int&" is
> encountered then it is quite likely that this variable is really used as
> an output variable whereas I'd not be so sure anymore if the type is
> "MyClass&".

I think that next rule is applied:
function that returns/takes as argument non const reference/pointer to
fundamental type.

Lets start with this and will add the rules.


> >> If I find some time, I'll update my "alternative" driver script that
> >> uses the official module_builder_t class and see if I can get it to
> >> generate the bindings as well.
> >
> > If I can have Maya sdk I would like to do it. Please contact me
> > privately if you want.
>
> Well, Maya is a commercial application so I cannot pass around the SDK.
> But I could send you the current version of my driver script that
> generates the extension module if you want. You won't be able to
> actually run it, but you can see how the bindings are created and check
> how these things would have to be rewritten using module_builder_t.

Good enough.

> - Matthias -


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