When you define a class, is inheriting a logger such as log4cxx a good design?
Approach for comprehensive data/activity logging
I would like to be able to build up a log of user activities, capturing data such as who they were, where they logged in from, what activity did they take, and what data did they change (both before and after).
Should I use a global logging variable?
Over and over again we’re told, “globals are bad” and with good reason. However, I’m working with a logger that needs to be accessible everywhere in the program. Why shouldn’t I create a global logging object? The alternative seems to be to pass the logger object into every object I instantiate and that seems very repetitive and non-productive.
What is the C++ equivalent of a logging facade in Java?
I’m currently writing a library in C++ and was wondering if I should log from within it. Googling the issue I came across this question but it makes reference to a logging facade. Is there anything equivalent for C++?