On 12/8/05, Jesse Erlbaum <[EMAIL PROTECTED]> wrote:
- die_on_bad_params has been removed (yay!)
Does this mean that you can pass any bad param into the template
and it
doesn't die? For me, this is the template equivalent of "use
strict".
Sometimes, a "bad" param isn't bad so much as unused. For example, you
might have a standard set of params that gets passed to everything.
One of those values might be used in all templates but one. What
should be done there?
I always turn off die_on_bad_param too, since it "breaks" the
separation between code and template that I want to achieve. What if
the design of the page changes in such a way that a parameter is no
longer needed? The designer shouldn't have to ask the programmer to
remove a parameter just to keep the program working.
I always figure that the program should be able to throw any
parameter at the template that it wants, and the designer can choose
what should be displayed.
Oh well, TMTOWTDI, as always....
Jaclyn
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[email protected]/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
