[Box Backup-dev] Logging

[Chris Wilson]

Hi Ben,

On Sat, 24 Dec 2005, Ben Summers wrote:

> TRACEn() is a bit messy. The number of arguments is required to make sure 
> it's easy to exclude them in release builds, even with annoying compilers, 
> and not fill the executables with debugging strings, so that really should 
> stay. But it is a bit of a mess with flags and attempting to do the 
> appropriate thing. Simply feeding it into the new log system would sort 
> things out nicely.

I'd like to be able to turn tracing on without recompiling. Is the space 
saving, and tiny performance gain of excluding these messages, really 
worth the debugging hassle?

> I wonder whether all the object orientation and subclassing is 
> necessary, and if it could be done with a couple of functions and a few 
> static variables? Simplicity is good.

I like simplicity too, but I also like object orientation and 
polymorphism. I'd like to create a framework that could in principle 
support other kinds of logging, such as writing a log file or sending 
messages over the network (to the backup server administrator or system 
support staff).

Cheers, Chris.
-- 
_ ___ __     _
  / __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
\ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |