Using glog's design for Phobos?

[sybrandy]

> Ok, I'm going to get flamed for this, but,
>
> I don't get it
>
> I do logging all the time. It's usually customized to the particular
> problem I'm trying to solve, so it involves uncommenting the right
> printf's and then running it. Voila. Done.
>
> The logging libraries I've seen usually required more time spent
> installing the package, getting it to compile, reading the
> documentation, finding out it doesn't work, rereading the documentation,
> etc., etc., than just putting in a #@$%^ printf, and Bang, it works, cut
> & print.
>
> Even worse, the logging libraries are loaded with a grab bag of trivial
> features to try and puff it up into looking impressive. They always
> seemed to me to be a solution in search of a problem.
>
> Shields up! what am I missing about this?

No, you're not.  That's why for the one I've been working on, I've been 
aiming for simplicity.  Basically, you can add as much logging as you 
like, but when you don't need it, you just recompile with a version 
switch to turn it off and it's like it was never there.

Mine is also one file to import and a two-line config file.  The main 
reason for the config file is just so you can change the logging level 
without stopping the program.

Casey