> And I'd certainly be miffed if I wanted to pick up a module and > found it forced me to use Log::Dispatch when the rest of my app > is already using Log4perl.
Right. It isn't so much about convincing module owners, as Leon suggested; it's dealing with all the existing applications out there that have already made a choice of one logging package or another (including, I'm sure, a fair number of home-grown loggers that people could hook up to Log::Any manually). > > 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?) > Log4perl can output to any of the Log::Dispatch dispatchers, so there is a certain amount of equivalence between them in that way. However, the complexity of initialization and configuration differ. There is also Log::Dispatch::Config, which seems to go halfway between the two.
