RE: [Log4cpp-devel] Logging Architecture

[Steve O. <Steve.Ostlind@NetIQ.com>]

From a performance perspective, having a hierarchy in your log4cpp
categories is a problem, Ex: "root.cat1.cat2". The performance hit is not
significant for GUI code, but for a tight loop where performance matters, it
can be a problem.

Calls it isDebugEnabled(), which have to jump up a category hierarchy, begin
to add up.

SteveO

-----Original Message-----
From: Colin Law [mailto:c....@el...]
Sent: Wednesday, August 13, 2003 3:51 AM
To: log...@li...
Subject: [Log4cpp-devel] Logging Architecture


Hi,

I have been using log4cpp for a while now, but I have never been sure on
the 'best' way to organise log categories within my classes. Should I
define a log category within each class, and get one category per class,
or get a global instance per implementation file, or possibly create a
shared instance to be shared amongst a group of classes?

I guess there are probably different techniques for different scenarios,
but I would be interested to hear how other people are doing this.

~Colin.



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Log4cpp-devel mailing list
Log...@li...
https://lists.sourceforge.net/lists/listinfo/log4cpp-devel