I share your opinion about reinventing, and reuse of existing code. And that was, why I did look at several Template Modules, including the Template-Toolkit. The latter looked for my problem as if
shooting at sparrows with canons (literal translation of a german saying).
I preferred the 30 line solution over the installation of a new, some hundred kByte Moduleset at the customer's site. All constraints are known from our former OS/2 Rexx implementation.
... and at least it is not meant as a CPAN module, just a code-snippet. (Should I have posted it in discussions?)
Nevertheless, I did not know your article before, it is a good example. Other projects require different solutions.
Thank You for Your comment
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.