pygccxml-development

[pygccxml-development] Warning output about members and member names

[Allen B. <al...@vr...>]

Roman:

The new warning support is very nice.  I like it a lot and I think it 
will help me quite a bit.  One suggestion though, when there is a 
warning related to a method or attribute of a class, could you output 
the name of that relevant declaration.  For example when I get a warning 
about exposing a non-public member function it would be very helpful to 
know the name of the member that I exposed that was not public.

What do you think about adding the member.name to all the warnings 
output by decl-wrappers.class_wrapper.class_t.is_wrapper_needed?  Is 
there any reason not to support this type of thing?

Thanks,
Allen

Re: [pygccxml-development] Warning output about members and member names

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

On 2/16/07, Allen Bierbaum <al...@vr...> wrote:
> Roman:
>
> The new warning support is very nice.  I like it a lot and I think it
> will help me quite a bit.  One suggestion though, when there is a
> warning related to a method or attribute of a class, could you output
> the name of that relevant declaration.  For example when I get a warning
> about exposing a non-public member function it would be very helpful to
> know the name of the member that I exposed that was not public.
>
> What do you think about adding the member.name to all the warnings
> output by decl-wrappers.class_wrapper.class_t.is_wrapper_needed?  Is
> there any reason not to support this type of thing?

There is no reason, I will add this information. Can you devote few minutes
of your time and to fix the messages? There were few users who didn't get right
what the message tried to say them.

( http://pygccxml.svn.sourceforge.net/viewvc/pygccxml/pyplusplus_dev/pyplusplus/messages/warnings_.py?view=markup
)

Thank you

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

Re: [pygccxml-development] Warning output about members and member names

[Allen B. <al...@vr...>]

Roman Yakovenko wrote:
> On 2/16/07, Allen Bierbaum <al...@vr...> wrote:
>   
>> Roman:
>>
>> The new warning support is very nice.  I like it a lot and I think it
>> will help me quite a bit.  One suggestion though, when there is a
>> warning related to a method or attribute of a class, could you output
>> the name of that relevant declaration.  For example when I get a warning
>> about exposing a non-public member function it would be very helpful to
>> know the name of the member that I exposed that was not public.
>>
>> What do you think about adding the member.name to all the warnings
>> output by decl-wrappers.class_wrapper.class_t.is_wrapper_needed?  Is
>> there any reason not to support this type of thing?
>>     
>
> There is no reason, I will add this information. Can you devote few minutes
> of your time and to fix the messages? There were few users who didn't get right
> what the message tried to say them.
>
> ( http://pygccxml.svn.sourceforge.net/viewvc/pygccxml/pyplusplus_dev/pyplusplus/messages/warnings_.py?view=markup
> )
>
>   
I may be one of those users. :)

As I encounter the messages, if I find one that is confusing or unclear 
I will do my best to change it to make it better.

Thanks,
Allen

> Thank you
>
>   

Re: [pygccxml-development] Warning output about members and member names

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

Hi Allen, I added additional information to the warnings.

Enjoy.

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