Hello monks and nuns,

tired of coding print-statements for debugging purposes again and again while being too lazy to use the debugger I recently wrote a module Debug::Filter::PrintExpr that - acting as a Perl filter - transforms some special comments into debugging print statements. As an example, this piece of code 

use Debug::Filter::PrintExpr;
...
my $some_var = 'some content';
my @array = qw(this is an array);
my %hash = (key1 => 'value1', key2 => 'value2');

#${$some_var}
#@{@array}
#${$array[3]}
#%{custom_label: %hash}

[download]
would generate code that produces an output like: 
line 28: $some_var = 'some content'
line 29: @array = ('this', 'is', 'an', 'array')
line 30: $array[3] = 'array'
custom_label: %hash = ('key2' => 'value2', 'key1' => 'value1')

[download]
I'd provide the module here if someone is interested. But maybe this is just weird stuff.

In reply to Debugging preprocessor by jo37

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.