I see that the logger implementation has multiple variations, but they're compile time options and not run-time. Given that I imagine changing that to a run-time option would be non-trivial, has anyone investigated simply compiling all of the logger libraries variations? One could then choose which variation you want at link-time - I think an improvement.

This is an issue with automated unit test cases, in which we don't want the logger output going to console but would instead like to either make it disappear, or sink it to a stream that we can rifle through when verifying the test output.

Thoughts?
Stephen