> The problem I have with calling it a Logger is that it hides the concept of
> Categories from the developer.
Isn't that what documentation is for?
I personally think that Logger is better than Category. Logger shows that
the object is used for logging messages, where Category could be an object
for a game show application, something to used classify animals or part of a
generalized catalog application.
Most developers I work with don't really care too much about the internals,
they simply need an API to inject log messages, though those folks probably
don't care too much if you called it Hamburger I would bet.
my $0.02, go with Logger, create deprecated sub-classes called Category for
backwards compatibility. If Logger turned into an interface then a dynamic
proxy could be used to make this compatiblity translation, but that is a
different matter all together.
--jason
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
