Re: Want to create a common Perl module

in reply to Want to create a common Perl module

Toolkit by TheDamian does that

The mantra of every experienced web application developer is the same: thou shalt separate business logic from display. Ironically, almost all template engines allow violation of this separation principle, which is the very impetus for HTML template engine development.

-- Terence Parr, "Enforcing Strict Model View Separation in Template Engines"

Comment on Re: Want to create a common Perl module

Replies are listed 'Best First'.
Re^2: Want to create a common Perl module by almut (Canon) on Jun 28, 2010 at 16:35 UTC
It's maybe worth noting that this module uses source filtering, i.e. it on-the-fly edits the respective `use` statements into your source before it's being compiled. While this is kind of the easy way out for all potential namespace related issues with importing/exporting, it might cause other unexpected behavior on rare occasions (like any source filter).	[reply] [d/l]
Re^3: Want to create a common Perl module by toolic (Bishop) on Jun 28, 2010 at 16:50 UTC
Also may be of interest: in Categorized Damian Modules, TheDamian classifies Toolkit as: Damian modules that are specifically debugging and coding aids and which Damian uses himself during code development:	[reply]
Re^2: Want to create a common Perl module by Anonymous Monk on Jun 28, 2010 at 22:37 UTC
In this case a simpler, and more atomic, solution than Toolkit might be Filter::Macro.	[reply]

In Section Seekers of Perl Wisdom