foreach $ext (@ext) {
eval "require $ext"
$args_ref=$ext->process($args_ref)
}
The above is written. It works. And yet, it's difficult to maintain.
Well, that's a pretty simple loop, and it didn't take you
many lines to describe what it does, and why. Yet you claim
it's difficult to maintain, so I expect there's something
else going on as well. Why is it difficult to maintain,
and why do you think it's easier if you put the functionality in different programs, and chain them?
You will still be chaining, and you still need to logic to
determine what to chain, and in which order.
Abigail
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.