Warning. That
eval solution needs error checks. Else
you could get very confused working out why you are getting
no result, when the problem is that $routine expects to
be sharing some variables with its environment, the
environment doesn't have them, and
strict finds this to
be a situation worth complaining about.
(Just to list one non-obvious way that a non-trivial error
in $routine may need to be handled.)
UPDATE
Re the reply, I understand fully. I just like pointing
these things out because you have to expect people to just
lift code from here directly without understanding the
issues. So if you are posting it as a suggestion, it
should look like production code.
That said, I find the eval solution painful on the
face of it. I would prefer to solve that with just
using Filter::Simple and a few well-chosen
macros. If I was going to solve things that way. Which
I would probably avoid for reasons listed above...
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.