in reply to Best way to share logging object among multiple objects?

A singleton is the first thing that comes to mind - a class that always returns the same object each time its new() is called. So if you want a logger, you call Logger->new(), and always get the same object. Class::Singleton wraps the logic up for you.

I am not familiar enough with this to point you at good documentation as to how to do it, but I can hear Ovid saying "create a logging role and give that to anything that needs to log". I really need to read his articles about this...basically you're using the extends ... with feature of Moose. See http://use.perl.org/~Ovid/journal/38586 for a solid intro to the concept.

  • Comment on Re: Best way to share logging object among multiple objects?

Replies are listed 'Best First'.
Re^2: Best way to share logging object among multiple objects?
by pileofrogs (Priest) on Aug 10, 2010 at 23:45 UTC

    ++

    If I understand this correctly, I'd want to use a singleton and a role. Making my logger a singleton makes it so each object uses the same Log::Dispatch object. Making it a role makes it so I don't lose my logging capability down a rabbit hole of multiple inheritance in the event my code gets really complex.

    Can I even do that?

    Does that sound right? Did I totally miss the point?

    Thanks!

    --Pileofrogs

[reply]
      Taking my advice with a chunk or rock salt the size of your head because I (at this late date) have still not learned Moose: I'd say yes, that's probably the simplest. If you use (say) Log::Log4perl, I think that the singleton issue's already taken care of, and all you need at that point is a role that provides the logging features of your choice. Having the role lets you (if you want to) abstract the logging so that you can say "please log this object" to the CanLog role, and the role takes care of the details (e.g., does this object have a detailed_description method I can call, or do I just Data::Dumper it?).
[reply]

In Section Seekers of Perl Wisdom