Hello.

We are using Try::Tiny module in our project. I'm always using "try" instead of "eval" whenever I can, but eval can do some things, that "try" cannot: it's evaluation code from strings.

So, when I use eval() with string I should do something like this:

eval "require $module" or $self->error("...");

instead of nice and pretty

try "require $module" # It's not going to work catch { $self->error("..."); }

I can try something like this:

try { eval "require $module" or die $@; } catch { $self->error("..."); }

but it still looks ugly, because it's actually eval{eval""}.

Should I worry about this? Should I suggest improving Try::Tiny so it can "try" strings, not only blocks?

P. S. I believe the root of the problem is perl "eval" itself. It does two things for me (evaluate strings AND catch "exceptions") that are not really connected.


In reply to Try string, not block by pushtaev

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.