Re: your first point here:
http://bit.ly/tl2q14
With this approach not only that an additional method call is added (hardly a big
performance fault, but still..) but for me it makes it harder to compare the logs with the
code, as the class that contains the code might be different than the class that
"runs" the code.
In my case at least, it's important to be able to compare the logs with the code fast
- as this is the way I use the logs.
OTOH I agree that the logs don't tell you straight away the runtime class where the
code was ran - but TBH I don't remember that being an issue for me. I remember though
being annoyed by "overridden" loggers in a previous project - hence my email
:-)
I'd be very curios hear other opinion on this, especially Galder's as I imagine he
did a fare share of log reading back in the days.
Cheers,
Mircea