RE: [boost] Re: Logging Library -- Formal Review Request

From: Bennett, Patrick (Patrick.Bennett_at_[hidden])
Date: 2005-04-26 10:53:29

> -----Original Message-----
> From: boost-bounces_at_[hidden]
[mailto:boost-bounces_at_[hidden]]
> On Behalf Of Peter Simons
> Sent: Tuesday, April 26, 2005 5:55 AM
> To: boost_at_[hidden]
> Subject: [boost] Re: Logging Library -- Formal Review Request
> 
> Patrick Bennett writes:
> 
>  > Having worked on quite a few large-scale commercial
>  > software products using an extensive logging framework
>  > for quite a few years now, I can attest that, short of
>  > embedded deployment, there is almost never a reason to
>  > compile out tracing code.
> 
> Except for, when the tracing code comes with serious
> performance penalties. Then you really want to be able to
> compile a version with all the debugging and tracing
> statements removed.

Nope, in the system we use, the tracing code isn't even called unless
tracing is actually enabled (which can be done in realtime from other
processes).  The only overhead incurred for any logging statement
currently not active is little more than a lookup, compare, and jump.
>From the discussion I've seen, the proposed library should work the same
way.

Patrick Bennett