Re: Re: Sharing a log file across classes...

I'm not sure it needs to even be that complex. If you are using all three classes in the same script, why not simply pass the log object in the constructor?

my $log = Log::Common->new;
my $foo = Foo::Foo->new('log' => $log);
my $bar = Foo::Bar->new('log' => $log);
my $baz = Foo::Baz->new('log' => $log);
[download]

I have used a similar method for sharing database handles amongst several different classes.

Comment on Re: Re: Sharing a log file across classes... Download Code

Replies are listed 'Best First'.
Re3: Sharing a log file across classes... by dragonchild (Archbishop) on Feb 27, 2002 at 21:04 UTC
That is definitely a perfectly good way of doing things. However, I like to encapsulate things. The client of that class hierarchy doesn't need to know what logger is being used, so allow for some default behavior. If the client wishes to override that behavior, then allow for a logger to be set, both in the constructor and by some 'setter'. ------ We are the carpenters and bricklayers of the Information Age. Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.	[reply]
Re: Re3: Sharing a log file across classes... by Anonymous Monk on Feb 27, 2002 at 22:51 UTC
In that case, I think the singleton is definately the best approach. That allows you to create a class which will return the same instance to everything that calls its constructor.	[reply]