Re: Parsing Templates

Reinvention of a good wheel is generally not a good idea. I have installed Template Toolkit on several systems without a hitch (*nix and M$ systems). Having to install outside modules, really does not make the system less portable (unless the modules will not install on various systems, but as I have said at least one very good templating system does). Yeah there's a little more over head to getting the system installed, but I would rather take more time in the front end than not have a product or even worse have a poorly functioning product.

So to make a long answer short: I would recommend reevaluating the specification of no outside modules.

grep

grep> cd pub
grep> more beer
[download]

Comment on Re: Parsing Templates Download Code

Replies are listed 'Best First'.
(jeffa) 2Re: Parsing Templates by jeffa (Bishop) on Jan 13, 2002 at 21:04 UTC
And i will 'third' this motion. I really think that the question itself is a testimony to USE avaible modules instead of trying to roll your own. Now, i can really appreciate wanting to avoid external modules to make your program more portable - but there is nothing stopping someone from packaging up those modules with the application... jeffa L-LL-L--L-LL-L--L-LL-L-- -R--R-RR-R--R-RR-R--R-RR F--F--F--F--F--F--F--F-- (the triplet paradiddle)	[reply]
Re: Re: Parsing Templates by IlyaM (Parson) on Jan 13, 2002 at 20:48 UTC
I second it. Popular modules often are much more portable than homegrown solutions for very simple reason: there is much more people who use them on very different platforms and on different versions of Perl. -- Ilya Martynov (http://martynov.org/)	[reply]