A note nearly identical to this was posted to the DBI mailing list yesterday. Was that you?

In any event, the response from those who even benchmarked it is a clear and resounding "BS" call on the "eval slows things down".

Perhaps it's a bad bit of cargo-cult programming. eval-string certainly slows things down. Using $& (not $@) once in a program slows the whole thing down, and once you pay the price once, you don't have to pay it again. Maybe this is a mutated gene from some weird mutant merge of those two statements.

In any event, eval-block subtracts nothing from the execution speed over the price of a normal block (now don't freak out about that either!).

-- Randal L. Schwartz, Perl hacker

In reply to Re: DBI and Eval by merlyn
in thread DBI and Eval by Sifmole

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.