On Fri, 2006-11-03 at 15:29 +0100, A. Pagaltzis wrote:
I know I wouldn’t miss plugins. If expressions were Perl, I’d
simply be using modules. Plugins are just an artifact of having
an extensive mini language.
When I say plugins, I mean it in the broadest sense. I usually just
use modules.
On Wed, 2006-11-01 at 17:17 +0100, A. Pagaltzis wrote:
* Perrin Harkins [EMAIL PROTECTED] [2006-10-28 06:05]:
You're only supposed to use the TT language for simple things.
Hairy things are supposed to be encapsulated in plugins,
written in Perl.
That makes a certain amount of sense; I
Hi,
On Oct 27, 2006, at 11:01 PM, A. Pagaltzis wrote:
None of these engines provides a separate concise syntax to cover
the 18% AND the power of a *real* language to cover the 2%.
I wonder if using PHP as a template language for Catalyst would fly...
Has anybody tested or use
* Jonathan Rockway [EMAIL PROTECTED] [2006-10-27 20:10]:
Mostly because mason becomes an unreadable mess, just like PHP.
Take a look at the RT source code, or my clever example here:
Mason:
table% my $sth = $dbh-prepare('SELECT columns FROM table WHERE
something=1'); for($row =
A. Pagaltzis wrote:
TT2 provides a single minilanguage for both, which is
unnecessarily powerful and verbose for the 18% and way
underpowered for the 2%.
You're only supposed to use the TT language for simple things. Hairy
things are supposed to be encapsulated in plugins, written in Perl.
