pygccxml-development

[pygccxml-development] [new feature]add_properties

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

Hi. I added new future - add_properties.
The idea behind this functionality is to automatically recognize and
add properties to the class.
The "add_properties" functionality aware of few coding conventions:
    UpperCamel
    lowCamel
    words_separated_with_underscore
And also it is aware of common prefixes: get, is, has, <<empty prefix>>, set.
It is possible to configure to exclude functions that has been used
for properties.

Usage example:
mb = module_builder_t( ... )
my_class = mb.class_( ... )
my_class.add_properties()
or
my_class.add_properties( exclude_accessors=True )

The implementation of algorithm could be found here:
http://svn.sourceforge.net/viewvc/pygccxml/pyplusplus_dev/pyplusplus/decl_wrappers/properties.py?view=markup

Your comments, suggestions, bugs are welcome.

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

Re: [pygccxml-development] [new feature]add_properties

[Kevin B. <kev...@gm...>]

Roman Yakovenko wrote:
> Hi. I added new future - add_properties.
> The idea behind this functionality is to automatically recognize and
> add properties to the class.
>   
Excellent idea. I was just thinking about how to script something like this.

> my_class.add_properties()
> or
> my_class.add_properties( exclude_accessors=True )
>   

I have a class with both getValue() and setValue(). setValue() is 
explicitly excluded (it happens to be a protected member and I don't 
want protected members.)

I noticed that in this case add_properties() does not automatically add 
a read-only property Value for the still-visible getValue(). You have to 
specify param exclude_accessors=True.

If I do not explicitly exclude member function setValue(), it binds a 
setValue() function as expected, but it still generates a read-only 
property Value regardless of exclude_accessors True or False.

--- Kevin

Re: [pygccxml-development] [new feature]add_properties

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

On 10/4/06, Kevin Bluck <kev...@gm...> wrote:
> Roman Yakovenko wrote:
> > Hi. I added new future - add_properties.
> > The idea behind this functionality is to automatically recognize and
> > add properties to the class.
> >
> Excellent idea. I was just thinking about how to script something like this.
>
> > my_class.add_properties()
> > or
> > my_class.add_properties( exclude_accessors=True )
> >
>
> I have a class with both getValue() and setValue(). setValue() is
> explicitly excluded (it happens to be a protected member and I don't
> want protected members.)
>
> I noticed that in this case add_properties() does not automatically add
> a read-only property Value for the still-visible getValue(). You have to
> specify param exclude_accessors=True.
>
> If I do not explicitly exclude member function setValue(), it binds a
> setValue() function as expected, but it still generates a read-only
> property Value regardless of exclude_accessors True or False.

This is your use case, as I understand it:

struct data_t{
    int getValue() const { return 1;}
protected:
    void setValue(int){}
};

where setValue is excluded, right?

If I am right, than I can not reproduce the bug ( behaviour ) you
describe, sorry.
Can you create small example that reproduce the problem?

Thank you

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

Re: [pygccxml-development] [new feature]add_properties

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

On 10/5/06, Kevin Bluck <kev...@gm...> wrote:
>
> > If I am right, than I can not reproduce the bug ( behaviour ) you
> > describe, sorry.
> > Can you create small example that reproduce the problem?
> Hmm... now I can't reproduce it either. It might have been another one
> of my famous incompatibilities.
>
> Sorry. I'll let you know if I figure it out.

This is okey.

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