I tend to prefer command-line switches (I use --DEBUG). You can then conditionally load modules as appropriate using require or eval (you could of course, build your conditional using your $I_AM_DEV, but I personally find command line switches far more elegant and less annoying than modifying code to enable/disable such things). Example:

use Getopt::Long;
my %OPT;
GetOptions \%OPT, qw/ help|h DEBUG / or ($OPT{help} = 1);
if ($OPT{DEBUG}) {
    # whatever you like:
    require Data::Dump;
    eval "use Carp::Always";
}

...

say "Got some data:\n", Data::Dump::pp(\%my_data) if $OPT{DEBUG};

[download]

Good Day,
    Dean

In reply to Re: How to turn a "developer code" into a "user code" by duelafn
in thread How to turn a "developer code" into a "user code" by mascip

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.