Boost Logging Library v2 Namespace List

Here is a list of all documented namespaces with brief descriptions:
boost::loggingRoot namespace. All the logging lib is contained in this namespace, or sub-namespaces of this one
boost::logging::destinationDestination is a manipulator. It contains a place where the message, after being formatted, is to be written to
boost::logging::destination::convertAllows writing messages to destinations
boost::logging::filterContains filter implementations. A filter tells the logger if it's enabled or not
boost::logging::format_and_writeThe format_and_write classes know how to call the formatter and destination objects
boost::logging::formatterFormatter is a manipulator. It allows you to format the message before writing it to the destination(s)
boost::logging::formatter::convertAllows format convertions - In case you're using a formatter that does not match your string type
boost::logging::formatter::tagClasses that process the tags coming with the library
boost::logging::gatherClasses that implement gathering the message
boost::logging::gather::ostream_likeGathering the message: Allows you to write to a log using the cool "<<" operator
boost::logging::levelHandling levels - classes that can hold and/or deal with levels - filters and level holders
boost::logging::lock_resource_finderPossible ways to lock resource for read/write
boost::logging::lockerContains implementations of locker objects. Such a locker can lock data for read or write
boost::logging::manipulatorManipulators = Formatters and/or destinations
boost::logging::msg_routeSpecifies the route : how formatting and writing to destinations take place
boost::logging::op_equalImplements operator== for manipulators
boost::logging::optimizeGathering the message: contains optimizers for formatting and/or destinations: for example, caching techniques
boost::logging::profileAllows profiling your application
boost::logging::scenarioUse this when you have a specific scenario, and want the best logger/filter classes that fit that scenario. Check out scenario::usage and scenario::ts
boost::logging::scenario::tsFind out the right logger/filter, based on thread-safety of logger(s)/filter(s)
boost::logging::scenario::usageIf you want the library to choose the best logger/filter classes based on how your application will use the loggers and filters, use this namespace
boost::logging::scenario::usage::filter_Filter usage settings : filter_::change and filter_::level
boost::logging::scenario::usage::filter_::changeWhen does the filter change?
boost::logging::scenario::usage::filter_::levelWhat's our "level" policy?
boost::logging::scenario::usage::logger_Logger usage settings : logger_::change and logger_::favor
boost::logging::scenario::usage::logger_::changeWhen does the logger change, that is, how often do you manipulate it?
boost::logging::scenario::usage::logger_::favorWhen logging, what should we favor?
boost::logging::scenario::usage::logger_::gatherHow do you gather the message?
boost::logging::tagAllows you to use tags (extra information about the context of the logged message: file/line, function name, thread id, etc.), and log this information as well
boost::logging::writerClasses that write the message, once it's been gathered
boost::logging::writer::threadingSpecify thread-safety of your logger_format_write class

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