I see: it uses Try::Tiny itself, and just makes the exception into its own return value.

It doesn't hide itself from the call stack, so it will make my Carp report show itself rather than my test function. Ah, but knowing that, I can just test for that instead, since the real test is that Carp reports on the caller, not some other intermediate function that was between the user-facing function and the one that died. It might be more helpful since the file/lineno will always be the same: that of the exception function itself. Perhaps a similar function can include a test of the exception string for mention of the correct location, as well.

Thanks.

—John

In reply to Re^2: testing the exception throwing by John M. Dlugosz
in thread testing the exception throwing by John M. Dlugosz

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.