A common idiom for eval is
eval { do_something_that_might_die(); 1; } or do { my $error = $@ || 'Zombie error'; deal_w($error) || die; }

Is that because $@ might contain something "false-y" (like 0, '0', "", undef)?
(If so, who cares? Why would I care if the "reason string" is false-y or not?)

Or is it a hold-over from bugs in ancient versions of perl?
If so, how old? if we already require versions greater than $v can we dispense with it?

((Sorry monks, I'm sure this has been asked before, but searches like "perl eval zombie error" and the like are mostly about zombie processes and code that already contains that boilerplate.))

Edit: I Forgot to mention that our local coding standards discourage Try::Tiny apparently because it's edge cases have been tripped over in the past.


In reply to eval: Why use the 'Zombie error' idiom? by DouglasDD

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.