Well, if we want to be really careful about checking what
$code is going to do, why not do some more analysis of its content:
my $codeBegin = "";
if ( $code =~ /BEGIN\s*\{/ ) {
# tricky part here: try to locate the matching close brace
# (this would require parsing character-by-character, to
# handle various quote operators and escapes -- a worthwhile
# project for a module developer, not something I can do here).
# check that part separately, assign it to $codeBegin and
# delete it from $code;
}
# now check whatever's left in $code, and if everything's
# okay, then:
eval "$codeBegin $code";
But would we also have to check separately for an END{}
block?
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.