On Sep 10, 2007, at 11:53 AM, A. Pagaltzis wrote:
So Log::Any makes some amount of sense for people who don’t want to lock their users into either choice.
Yes, it's sort of a DBI for logging stuff, if I understand correctly; does little work of its own, but allows multiple backends for the real lifting.
I think it fits well with this whole "aspect-oriented" idea, which locks people into a particular implementation of each aspect unless there's an abstraction layer on top.
OTOH maybe two adapter modules would work as well, one to let Log4perl-based code run under Log::Dispatch and one vice versa. (Do such already exist possibly? Or is there a fundamental problem with that idea?)
It precludes a third logging backend from joining in the fun, because for N backends you'd need N*(N-1) adapters.
-Ken
