Re: [pygccxml-development] improving user experience

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

On 7/23/06, Matthias Baas <ba...@ir...> wrote:
> Personally, I'm against splitting lines. Actually, I'd even prefer to
> have the entire warning message in one single line so that I see the
> entire message when I 'grep' for a particular declaration.
> This would also make it easier to write scripts that further process a
> log file (e.g. a filter that transforms the single-line log into an
> easier to read log or even a set of html pages).

Yes, but in this case line is toooooo long. Personally, I can not read it.
I have an idea, but I will need your help( =time ). All messages written by py++
will be written in single line. py++ will create custom formatter,
that will divide
message to few lines and will use it by default. You will be able to
use the formatter
provided by logging package.It could be nice, if you can find time and
implement it.

> 1) The second message complains about the first argument being a
> non-const reference to a C++ fundamental type. But the first argument is
> just an ordinary integer (no reference at all). So what's the problem here?

Bug. I will try to fix it this evening.

> 2) Why does the second warning appear at all? The first warning already
> told me that the operator cannot be exported anyway. (If it is
> intentional that pyplusplus reports all potential problems then that's
> fine with me and I'm not arguing that this should be changed.

Yes, it is intentional. py++ will provide user with all information it has.

Thanks for feedback.

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