Hello smile4me,

1. does the perl compiler optimize away the debug's when the ENV{DEBUG_LEVEL} is 0?

No.

2. is there a cost to leaving the debug()'s inline?
3. should I remove them to improve performance overall?

Yes, there is a cost, but it’s probably negligible. If performance becomes a problem, you should first profile the code using a module such as Devel::NYTProf to find the bottlenecks. Unless your debug statements are placed inside heavy-duty loops, it’s unlikely they will degrade performance significantly.

4. is there a better way to accomplish the goal of simple on/off for debugging one's code?

If you want the compiler to eliminate debugging code when debugging is not required, you need to code like this:

use constant DEBUG => $ENV{DEBUG_LEVEL} // 0;        # Handle undef gr
+acefully

...

sub helpful {
    my $int = shift;
    debug(1, "called with: ", $int) if DEBUG > 0;    # <-- Add this
    ## do stuff here ...
    my $val = $int * $int;
    debug(3, "output: ", $val)      if DEBUG > 0;    # <-- Add this
    print "$int becomes: $val \n";
}

...

[download]

You can check with perl -MO=Deparse that when DEBUG == 0, the debug statements are removed by the compiler.

Hope that helps,

Athanasius <°(((>< contra mundum Iustus alius egestas vitae, eros Piratica,

In reply to Re: perl compiler optimizer curiosity by Athanasius
in thread perl compiler optimizer curiosity by smile4me

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.