I have to agree with Ovid. As with everything else, why reinvent the wheel? Not only does the build-in debbuger work very well, its already there.

I'm on Win32, so I decided to give ActiveState's debugger a shot, and I have found it not only to be a solid app, but a very very useful tool while trying to figure where things went sour in my apps.

The idea of printing line by line does sound like a cool challenge though, but only as one of those I-wonder-if-this-can-be-done? things...

#!/home/bbq/bin/perl
# Trust no1!

In reply to (bbq) RE: (Ovid) RE: (Debugging, Tracing, Trace, Instrumenting) by BBQ
in thread (Debugging, Tracing, Trace, Instrumenting) Automatic tracing of my Perl code? by princepawn

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.