Dear fellow monks,

Please consider the following:

$code = 'while (<>) {'; $code .= 'if (/'; $code .= join ('/ && /', @regexen); $code .= '/) {' $code .= ' print $_;' $code .= '}} '; eval $code; die "Error: $@\n Code:\n$code\n" if ($@);

I would like to ask a specific and a general question:

Specifically, I am interested in performance: if matching many patterns, how does qr// + while-loop perform, compared with an eval of a built string containing while-loop + same patterns 'hard-coded' (as in the above example).

And more generally: how do people use eval string? Are there cases that really need it? (but I would also like to invite the more strange uses.)

I do understand that it should only be used on trusted strings.
My experience with eval string is limited, and I hope to learn from the way others are using this clearly powerful technique.

Thanks


In reply to eval string possibilities by erix

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.