Sepia has come a long ways since your review. Myself, I've always found the Perl debugger more painful than print statements, and didn't discover gud's perl debugger function until I had become used to using Sepia and print. Besides, what I am aiming for with Sepia is not an improved debugger, but a Lisp-style development model for Perl, where you experiment at the prompt, and errors give you a prompt to play with.

Anyways, the point of my post was that you might as well always run with some debugging enabled, since it costs nothing and lets you diagnose problems without having to come up with test cases to reproduce them.

In reply to Re^2: perl -d: faster and less scary than you think by educated_foo
in thread perl -d: faster and less scary than you think by educated_foo

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.