boost::logging::scenario::usage::logger_::change Namespace Reference

When does the logger change, that is, how often do you manipulate it? More...


Classes

struct  often
 Optimize for often change. Does per-thread caching. At a given period, it re-synchronizes. This is the default, for multi-threaded applications. More...
struct  set_once_when_one_thread
 Set only once, when there's only one thread running - thus, you don't need to worry about thread-syncronizing. More...
struct  set_once_when_multiple_threads
 Set only once, when there could be multiple thread running. More...
struct  always_accurate
 This is always accurate. However, it's the slowest too. More...
struct  single_thread
 Single threading. It doesn't matter when/how often the filter/logger changes. This is the default, for single-threaded applications. More...


Detailed Description

When does the logger change, that is, how often do you manipulate it?

Note that using the log does not mean changing it. Manipulation means invoking non-const functions on the logger, like adding/removing formatters/destinations for instance.



Copyright John Torjo © 2007
Have a question/ suggestion/ comment? Send me feedback