Re: [boost] A meta-proposal for logging

From: JD (jean.daniel.michaud_at_[hidden])
Date: 2007-04-03 14:30:19

> 
> Since I'm interested in having such a library in Boost, I'd be happy
> to participate.
> 

It's what you did and you did well! Thank you!

- Nonetheless, I see a very interesting contribution from Michael 
Lacher. I'm not sure the mailing list is the right place to discuss 
them, but  I don't see any discussion page on the wiki.

Concerning req id 3: Michael, I don't really get this statement. I think 
it's really to the library user (programmer) to decide which log shall 
be present or not. He's in charge of filtering the logs following the 
compilation configuration (debug or release). I don't think the library 
shall manage this by itself. Or maybe I did not get your point at all!

General Thoughts, third bullet:
You say:
        "Logging: print log messages useful for the program user. They are 
needed to understand unexpected conditions during usage like: "file xyz 
not found", "directory baz is not readable".

   I can't disagree more with this. IMO, logging is not at all a way to 
give information to the program user. In my mind, a logging library is 
intended only for debugging, journaling, auditing and performance 
measuring. Not a way to display error message or waiting message to the 
user. In my mind, these are totally different things. Please someone, 
give his POV on this, I think this is a major disagreement.

- Besides, Caleb Epstein propose the definition of channel as:
Multiple named channels each with configurable "threshold" (e.g. error, 
warning, debug, etc)

Caleb, would you mind add a definition of channel on the wiki 
(http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?Boost.Logging) 
and maybe add some requirements on this?

JD