Re: [pygccxml-development] Indexing suite exception

[Lakin W. <lak...@gm...>]

On 6/21/06, Lakin Wecker <lak...@gm...> wrote:
> On 6/21/06, Matthias Baas <ba...@ir...> wrote:
> >  but it's more serious that I
> > missed the warnings about that (if I had seen them I wouldn't have tried
> > compiling the code in the first place).
> > The problem is that a command line tool basically only has one single
> > channel (stdout) to communicate with the user (having stderr as well is
> > only a slight improvement as they both refer to the same "channel" by
> > default, namely the console window). My suggestion would be to write the
> > really important messages (like the max arity thing) into a separate log
> > file in addition to writing to stdout (or actually it should be stderr).
> > In my opinion this should already be the default behavior. So a user can
> > check any time after the tool has run if there have been important
> > issues. Before quitting, pyplusplus could even check if anything has
> > been written into that log file and print a final message that there
> > have been critical errors and the user should refer to that log file.
>
> I don't mind the current behavior as it would be easy for the user to
> hook into the logging module and write out messages above a certain
> importance to a separate log file.

As a reference, http://docs.python.org/lib/multiple-destinations.html

If pyplusplus is reporting this as a warning, then I think it's
appropriate and that pyplusplus has done it's job.

On a side-note, It would be nice to have a small wiki somewhere to
aggregate all of these best practices for pyplusplus.  Such as setting
up multiple loggers in order to capture _all_ output somewhere for
debugging purposes, and capturing only important pyplusplus messages
to the console or another file for general success feedback purposes.


Lakin