From: Stuart Dootson (stuart.dootson_at_[hidden])
Date: 2005-08-03 01:57:16
On 8/1/05, John Torjo <john.lists_at_[hidden]> wrote:
> Hi all,
>
> Just updated the Logging library. Find it here:
> http://torjo.com/code/logging.zip
> Also, I've updated the docs. Feedback is welcome.
>
>
> Highlights:
> **** Multiple levels.
> **** Easier manipulation of logs
> **** Modifiers/Appenders can now be deleted.
> **** Shortcut for BOOST_IS_LOG_ENABLED
> **** Exception guards
> **** Shared Memory Appender
>
>
>
>
> **** Multiple levels.
> You can specify levels, very much like log4j.
>
>
> Best,
> John
>
> --
> John Torjo, Contributing editor, C/C++ Users Journal
John - this is the first time I've looked at your logging library -
looks pretty good (especially now you've got multiple levels - thats
something I've used before, which I found very handy). I like the
modifiers and appenders as well.
A couple of questions -
1. Is it possible to associate different levels with different
destinations (e.g. err, fatal and warn with std::cerr, others with
std::cout)?
2. Is it possible to query for the current logging level? If logging
activities take a significant amount of time, but they won't be
output, you don't want to do them. As an example - I've written
libraries to decode debug information (Dwarf, Stabs etc). These would
at a high logging level, construct and output a textual equivalent of
a debug record (which took significant time). The text construction
wouldn't be done unless log output was going to be done.