in reply to Re: RFC - Template::Empty
in thread RFC - Template::Empty

Thanks for the essay link, it has been a while since I have read it so it sounds like I am due for a review.

The code is tied tightly to the presentation with this approach, but the problem I have seen with template code becoming too programmatic gets you to the same place, just a different route (and language).

Replies are listed 'Best First'.
the rhandom-perrin attack rears its head again
by metaperl (Curate) on Feb 26, 2008 at 15:37 UTC
    The code is tied tightly to the presentation with this approach,
    redhotpenguin, what do you mean? Is what you state above a problem? Can you document a case where this leads to issues? Give me one web link or code sample showing this to be a problem. If you know Perl OO, you can decouple, slice, dice, flip, saute your Perl code to the presentation... Perl is liquid my man. Drink every drop. It will never fail you. It has a user base well into the hundreds of thousands. It has been around for more than a decade. And has solved IT problems in every domain under huge time pressure.

    Put your faith in the real solid rock and be happy.

    I have beheld the tarball of 22.1 on ftp.gnu.org with my own eyes. How can you say that there is no God in the Church of Emacs? -- David Kastrup 
    [tag://fanatic,perl,propaganda]

    [download]
    Enforce strict model-view separation in template engines via HTML::Seamstress The car is in the cdr, not the cdr in the car
[reply]
[d/l]

In Section Meditations