Hello,
I would like to use eval { } (i.e. the block version not the expression) quite often in one of my modules to protect for errors in function calls to other modules, i.e. exception handling.

I was just wondering how expensive the use of eval { } is. The code is compiled at compile time with all other code and eval can use the return statement, so it might be similar overhead like using a sub function.

Is eval {} much more expensive in terms of runtime (or other terms) then with e.g. using a sub call? Not that both would have the same function - just as a reference point.

Would it be ok, e.g. reasonable fast, to have eval {} inside a for loop, to test for exceptions for every element, or is it recommended to use eval {} outside the loop to speed things up?

Thanks for your wisdom.
Martin


In reply to How expensive is eval { }? by mscharrer

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.