Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Prepping for Production (staging) 5 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • And next we go over the code and isolate all debugging and verbose logging so it can be controlled using flags from a single point.

    Did you mean: Log::Log4perl [cpan.org]

    • Nah, more in the line of:


      print STDERR "We are now in func2\n";
      print STDERR "we got params:\n", Dumper \@params;


      We have a lot of such code. I attempt only to inject
      when really desperately debugging or atleast isolating it behind


      if (DEBUG) { ... }

      • That’s the point: with Log4perl, you can leave it in. You configure at runtime precisely which logging messages you’re interested in (yes, while the program runs – not just at startup).

        Furthermore, if you worry about expensive computations in your logging statements, you can pass a closure instead of a string, which will be invoked only if that statement is enabled. The logger call still happens, so this is not as efficient as if (DEBUG) { ... } (which is completely optimised away at com

        • I utilize log4perl with the Workflow distribution, but not for work currently. I will investigate if we can make use of log4perl in this setup.

          Thanks,

          • Ah, didn’t know you knew it already. A lot of people don’t, and logging is one of those things where it’s really really easy to understand and solve 30% of the problem, but it’s hard to imagine the whole problem and a lot of work to solve it well, so it’s common to get stuck at the 30% threshold.

            I was stuck there too before I read an article about Log4perl. It really opened my eyes – I had been doing things in a pretty crappy way but it never occurred to me I could have better. So now whenever I see someone wringing their hands about log/debug statements, I tell them to look at Log4perl.

            (After that article, I looked at other logging modules, because I wasn’t sure whether Log4perl is really that great or I just hadn’t seen any better before. Turns out it really is that great; only Log::Dispatch is close.)

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.