Christian Grobmeier wrote:
This is confusing. What should one use? Why two ways? I hardly see a
benefit in having the LoggerManager class. Its just defining the
classloader and references to the LoggerHierarchy.
I've always been confused by this myself. I would prefer to go with one
class: Logger
I would like to remove the LoggerManager class since Log4PHP 2.0 isn't
meant to be backward compatible. Instead, Logger should do the stuff.
Are there any reasons not to do so from your point of view?
I see no reasons (beside the BC break, but that shouldn't be a problem).
I think everyone will accept this and it's even more in line with log4j
which is a good thing :)
However, this is actually an important change that everyone should be
aware of and it should be clear in any examples for log4php 2.0 that
LoggerManager is deprecated/removed in favor of Logger. These are the
lines users will have to change in their code when upgrading to 2.0.
Knut
