-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of John Torjo Sent: Tuesday, April 26, 2005 3:12 PM To: boost@lists.boost.org Subject: Re: [boost] Re: Logging Library -- Formal Review Request

...

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.

Yup, it does work the same way -- except that for my lib there's not even a lookup. Every log internally is a reference to a variable of boost::log::logger type, which contains a pointer to a boost::log::logger_impl, which contains a boolean variable.

[Bennett, Patrick] By lookup, I was referring (very) loosely to a pointer indirection. The handles in this system are actually statically defined raw ('opaque' handles) pointers to shared memory structures, so comparisons are *extremely* cheap [as you well know]. Patrick Bennett