Re: [ALACPP] log4cplus (was Singleton clarification)

["Jon Stewart" <stew1@xxxxxxxxxxx>]

> > Also, it has wrapper macros for logging -- which is nice because that's 
> > what you'd end up doing anyway.
> 
> You mean to make the logging syntax easier, or do you mean in order to
> make it possible to compile out the logging code? Normally I don't need
> the latter, as I prefer to have logging code in production environment
> (although it can be problematic doing so with general consumer
> software). Of course with log4cpp I do frequently use macros to remove
> logging.... so that I can make sure my bug isn't in log4cpp. ;-)


Compiling out the logging. I would personally prefer that logging always
shipped, 'cuz, damn, it'd be useful for customer support/debugging. But
who wants to take the performance hit of well-placed if-statements? I
mean, that can be huge, especially if you're running on an old processor,
like a 286, that doesn't have branch prediction; not everyone's a rich
kid, y'know, with a 386sx and 8megs of RAM.

<sigh>


Jon
-- 
Jon Stewart
stew1@xxxxxxxxxxx
_______________________________________________
alacpp mailing list
alacpp@xxxxxxxxxxx
http://lists.ellipsis.cx/mailman/listinfo/alacpp