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
| [reply] |
Ahh, Yet Another Templating Solution.
Speaking of which, one possibility to take into account could be our fellow Rhandom's "new" Template::Alloy about which there's been some talk recently: what seems nice about it is that it supports several different templating schemes... and if I understand correctly, it should do so in a very efficient manner too. Thus it would allow one to pick the "best" from each...
| [reply] |