On Mon, 10 Sep 2007, Jonathan Swartz wrote:
> It isn't different, by itself, but it translates naturally into
>
> $log->debug("Current arguments: " . Dumper([EMAIL PROTECTED])) if
> $log->is_debug;
>
> whereas if you start off in easy mode, you don't have any way to get
> at the logger (as f
>> The problem I have with the DEBUG etc keywords is that they promote
>> inefficient behavior. e.g.
>>
>> DEBUG "Current arguments: " . Dumper([EMAIL PROTECTED]);
>>
>> will take the performance hit for Dumper() even when debug logging
>> isn't turned on.
>
> Sure, although I don't see how
>
Mike Schilli wrote:
>
> While you're at it, here's my pipe dream: I want something like Dtrace,
> where the logging framework zeroes out the opcodes that are currently
> inactive, and the interpreter rushes through them at light speed with
> practically no overhead.
>
> -- Mike
>
This sounds l
On Sat, 8 Sep 2007, Jonathan Swartz wrote:
> Did you see this in the posting?
>
> As a convenient shorthand, you can use
>
> package Foo;
> use Log::Abstract qw($log);
>
> to create the logger, which is equivalent to the first example
> except that $log is
>
>
> On Sep 8, 2007, at 1:19 PM, Mike Schilli wrote:
>
> > On Fri, 7 Sep 2007, Jonathan Swartz wrote:
> >
> > I'd be interested in feedback on a proposed module, Log::Abstract,
> > described here:
> >
> > http://use.perl.org/~jonswar/journal/34366
>
> ...
>
> By the way, I don't ag
On Fri, 7 Sep 2007, Jonathan Swartz wrote:
> I'd be interested in feedback on a proposed module, Log::Abstract,
> described here:
>
> http://use.perl.org/~jonswar/journal/34366
>
> This would be a tiny module designed to bridge CPAN modules that wish
> to log (e.g. LWP, DBI, ...) with existin
