| boost::logging | Root namespace. All the logging lib is contained in this namespace, or sub-namespaces of this one |
| boost::logging::destination | Destination is a manipulator. It contains a place where the message, after being formatted, is to be written to |
| boost::logging::destination::convert | Allows writing messages to destinations |
| boost::logging::filter | Contains filter implementations. A filter tells the logger if it's enabled or not |
| boost::logging::format_and_write | The format_and_write classes know how to call the formatter and destination objects |
| boost::logging::formatter | Formatter is a manipulator. It allows you to format the message before writing it to the destination(s) |
| boost::logging::formatter::convert | Allows format convertions - In case you're using a formatter that does not match your string type |
| boost::logging::formatter::convert::prepend | |
| boost::logging::formatter::tag | Classes that process the tags coming with the library |
| boost::logging::gather | Classes that implement gathering the message |
| boost::logging::gather::ostream_like | Gathering the message: Allows you to write to a log using the cool "<<" operator |
| boost::logging::level | Handling levels - classes that can hold and/or deal with levels - filters and level holders |
| boost::logging::lock_resource_finder | Possible ways to lock resource for read/write |
| boost::logging::locker | Contains implementations of locker objects. Such a locker can lock data for read or write |
| boost::logging::manipulator | Manipulators = Formatters and/or destinations |
| boost::logging::msg_route | Specifies the route : how formatting and writing to destinations take place |
| boost::logging::op_equal | Implements operator== for manipulators |
| boost::logging::optimize | Gathering the message: contains optimizers for formatting and/or destinations: for example, caching techniques |
| boost::logging::profile | Allows profiling your application |
| boost::logging::scenario | Use 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::ts | Find out the right logger/filter, based on thread-safety of logger(s)/filter(s) |
| boost::logging::scenario::usage | If 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_::change | When does the filter change? |
| boost::logging::scenario::usage::filter_::level | What's our "level" policy? |
| boost::logging::scenario::usage::logger_ | Logger usage settings : logger_::change and logger_::favor |
| boost::logging::scenario::usage::logger_::change | When does the logger change, that is, how often do you manipulate it? |
| boost::logging::scenario::usage::logger_::favor | When logging, what should we favor? |
| boost::logging::scenario::usage::logger_::gather | How do you gather the message? |
| boost::logging::tag | Allows 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::writer | Classes that write the message, once it's been gathered |
| boost::logging::writer::threading | Specify thread-safety of your logger_format_write class |