pygccxml-development

[pygccxml-development] Status:

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

Plan for next week or two
1. adding code creators to decl wrappers

Done.

2. resolving function overload issues

Matthias, I would like to see your solution before I make any decision. Tha=
nks.

3. fixing finalize concept.

I will do it this evening

4. add few function/properties to module builder class:
   parser configuration
   code creators ( factory ) configuration

I hope I will be able to add this tomorrow

5. Documentation. Here I really need your help. If you can write small
tutorial, I will be
    glad. I think this will be the only stopper for making release.

Also take a look on pyplusplus boost.date_time example. It looks much,
much, much better.

Thank you very much.

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

Re: [pygccxml-development] Status:

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

Roman Yakovenko wrote:
> 2. resolving function overload issues
> 
> Matthias, I would like to see your solution before I make any decision. Thanks.

So far, I would simply suggest that a set of overloaded functions is 
actually treated like one single function.

- Matthias -

Re: [pygccxml-development] Status:

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

On 3/19/06, Matthias Baas <ba...@ir...> wrote:
> Roman Yakovenko wrote:
> > 2. resolving function overload issues
> >
> > Matthias, I would like to see your solution before I make any decision.=
 Thanks.
>
> So far, I would simply suggest that a set of overloaded functions is
> actually treated like one single function.

Can you explain me? Or can you write small code that show how woould
you like to use that
feature?

Thanks

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

Re: [pygccxml-development] Status:

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

Roman Yakovenko wrote:
>>> 2. resolving function overload issues
>>>
>>> Matthias, I would like to see your solution before I make any decision. Thanks.
>> So far, I would simply suggest that a set of overloaded functions is
>> actually treated like one single function.
> 
> Can you explain me? Or can you write small code that show how woould
> you like to use that feature?

For example, if I write

rotateBy = mb.class_("MVector").member_function("rotateBy")

and rotateBy is actually implemented as a set of overloaded methods (as 
it is the case in the Maya SDK), then this call could be made so that it 
does not create an error even though the result references more than one 
declaration (note that I was using "member_function" and not 
"member_functions").
Then I could just treat these collection of overloaded functions as if 
it was only one single function:

rotateBy.include()          # includes all overloaded functions
rotateBy.rename("rotate")   # renames all overloaded functions


- Matthias -