Paul Seamons wrote:
For more discussion about CGI::Ex::Template, please refer to the warnocked
"Can there be two?" thread that started on the 5th of May.
Hah! I just un-warnocked it! Twice!
The optree-based approach certainly has the benefit of avoiding the need
to generate any Perl/Python/Javascript code.
I've always thought/considered/dreamed of writing a C library for the
template runtime evaluation along with the parser backend to compile
templates to C. Although you would lose all the immediate convenience
of being able to access Perl plugins, etc., it would be very nice to be
able to compile all the templates for your web site down to a C library
which could then be loaded direct into your web server.
But the first job has always been to fix all the broken bits in TT2 and
come up with a clean spec for TT3 that's doesn't rely too heavily on
Perlisms. That should make it easier to port to other languages. I'd
certainly love to see a Ruby TT. Python can keep it's silly whitespace
indenting!
A
_______________________________________________
templates mailing list
[email protected]
http://lists.template-toolkit.org/mailman/listinfo/templates
