On 2005-12-08, 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".
The documentation says:
die_on_bad_params - if set to 0 the module will let you call
$template->param(param_name => 'value') even if 'param_name' doesn't exist
in
the template body. Defaults to 1.
I always pass configuration variables to the template, although they are rarely
used. This can only be done by turning off die_on_bad_params.
Another "use case" is that the HTDot and TT plugins do-- they both provide a
"c" parameter which corresponds to the the CGI::App object, so you can directly
access anything in the object without extra code. Very handy.
I haven't turned on die_on_bad_params in the past five years of web
application development. I don't recall experiencing any noticeable pain
or suffering as a result, just added convenience.
The problem is that name sound like "use strict", which makes it seem
good and worth doing. It's more like "use paranoid".
Mark
---------------------------------------------------------------------
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]
