The block form of eval (like your example) can be
parsed at compile time along with everything else.
I think where the optimizer is going to have to be
careful is if you use the string form of eval. In
that case, some stuff just won't get optimized that
otherwise could be. So the performance-is-vital
people will be telling us not to use string eval,
and I can safely ignore them if I don't care
about optimization :-)
split//,".rekcah lreP rehtona tsuJ";$\=$;[-1]->();print
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||