That looks like a good use for a solution with Module::Compile. The original source would be manipulated (via PPI or whatever) and a compiled version with DEBUG() calls replaced by print @_ if 1 would be written as a .pmc files.

The obvious drawback is that once enabled in a program run, the macros won't see runtime changes. But that's coherent with the desire to eliminate the overhead of function calls, since we suppose that the mechanism for recompiling macros at runtime would be as heavy or even worse.

That would make feasible to build constructs that worked for instance like use which is kind of a macro for 

BEGIN {
    require $foo;
    $foo->import(@args); # if any args
}

[download]

Hum. May be a good idea or not.

In reply to Re: Debug Macro by ferreira
in thread Debug Macro by Outaspace

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.