Here are other logging and testing frameworks that have served as inspiration (negative and/or positive) for logog.

Panetheios

http://www.pantheios.org

Pantheios claims to compile to nothing in the final release case. However, the Pantheios library depends on STLSoft, xTests, b64, and shwild.

Petru Margenian's library in Dr. Dobb's Journal

http://drdobbs.com/cpp/201804215

Another interesting effort at a portable logging implementation. This library depends on an atomic_ops library from HP, and it won't mention this fact until you try to compile it. Logging can be enabled or disabled based on a single dimension ("level") and all logging output ends up at stderr (there is no support for alternative outputs).

glog, the Google logging library

http://code.google.com/p/google-glog/

Provides logging to stderr, a file or syslog. Their ostream-style logging methodology creates two sets of macros: one for macros that compile away in release mode, one for macros that don't. Interesting (if non portable) support for stack walking.

rlog

http://code.google.com/p/rlog/

Uses a publisher-subscriber model for all objects, and demonstrated that this basic architecture was highly appropriate for logging. Does not play nicely with custom allocators.

Loki

http://loki-lib.sourceforge.net/

The loki library demonstrates how to abstract platform-specific features like mutexes and threads in remarkably few lines of code.