Hi!
Mostly the same here. I like it for testing and the only reason I can think
of why it should be disabled is that you want to avoid setting params
specific for your template.
I kind of like the strict behavior on a second way: it remind me of use
strict with scopes 'n stuff, but that may be
On Tue, 2009-11-10 at 20:56 -0500, Mark Stosberg wrote:
To proceed, I'd like to hear at least a small chorus of voices claiming that
the they use
the die_on_bad_params feature.
I use it all the time as an alternative to an if-then-else: if a piece
of content is not to be displayed, I
..
I don't know how many people use die_on_bad_params, so I don't
know how worth it it is to modify the core.
..
I use it exclusively, under the assumption that, like 'use strict', it
is just best practice, may make my code faster and less error-ridden,
and may endow me with good looks and
On 11/11/2009 10:46 AM, P Kishor wrote:
I use it exclusively, under the assumption that, like 'use strict', it
is just best practice,
But a real question I have is, should designers (who are the ones
creating these, or at least that's one of it's benefits is that they
can) be burdened with
On Wed, 11 Nov 2009 02:30:21 +
r...@savage.net.au wrote:
Hi Mark
Quoting Mark Stosberg m...@summersault.com:
To proceed, I'd like to hear at least a small chorus of voices
claiming that the they use
the die_on_bad_params feature.
I always use it, since in testing I want to
Hi Michael
Quoting Michael Peters mpet...@plusthree.com:
On 11/11/2009 10:46 AM, P Kishor wrote:
I use it exclusively, under the assumption that, like 'use strict', it
is just best practice,
But a real question I have is, should designers (who are the ones
creating these, or at least
Hi Michael
Looking back at all of my projects that use HTML::Template I can
honestly say that die_on_bad_params has caused more problems then it's
fixed for me. It's not an argument against reliability but rather for
it. If a valid template change causes an ISE (rather than just an
invalid
This is a pathetic argument!
If die_on_bad_params makes it harder for designers to use and less like
the tools they are used to using, how can that be a pathetic argument.
Just because X is non-strict does not justify refusing to use strict
in Y, when the whole point of strictness is to
