Ah...so I wasn't close at all :)

Well, your explanation makes sense, thanks. Unfortunately, that still leaves me at an impasse. There's little value in adding 'use ifdef;' to all my modules, since the whole point of my using it is so that sections tagged with DEBUGGING will only activate during development, but be ignored in production, without any changes to the code. With 'use ifdef;' at the top of every module, I'd have to take it out when promoting to production (since production will not have ifdef). I could just as easily take out the debug code itself instead.

I suppose I could try 'use if $ENV{DEBUGGING}, ifdef;', but it just feels like what seemed like an elegant debugging solution in ifdef now requires too many workarounds.

In reply to Re^6: ifdef in modules by clee
in thread ifdef in modules by Anonymous Monk

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.