This proposal applies more to TT3. Template::Alloy and
Template::Parser::CET allow for you to choose the SYNTAX of the
template to be parsed.
The SYNTAX can be any of the following:
tt1 - Template::Toolkit v1
tt2 - Template::Toolkit v2
tt3 - Template::Toolkit v3
alloy - same as tt3
ht - HTML::Template
hte - HTML::Template::Expr
tmpl - Text::Tmpl
velocity - Velocity (VTL)
Template::Parser::CET allows you to pass SYNTAX to the
Template->new method.
Template::Alloy allows you to pass SYNTAX to the
Template::Alloy->new method, or set it via the CONFIG directive,
or set it via arguments to the eval filter or EVALUATE directive.
[% foo='bar'; "<TMPL_VAR foo>" | eval(syntax => 'ht') %]
[% CONFIG SYNTAX => 'tmpl'; PROCESS foo.tmpl %]
These features are available now in Template::Alloy - and partially
in Template::Parser::CET. Similar features would be welcomed in
TT3.
Paul Seamons
Additional possiblity - Template::Alloy has a define_syntax
method that allows for specifying an additional syntax type that
will be recognized.
_______________________________________________
templates mailing list
[email protected]
http://lists.template-toolkit.org/mailman/listinfo/templates
