Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Every perl module whose author wants strict mode (and they all should)
> has to carry such a declaration, so in a sense we'd just be doing what
> perl itself does, and by trying to provide a global switch we're being
> unperlish.
You missed my point. I wasn't objecting to having the global switch,
only to the fact that turning it on and off doesn't do what a rational
person would expect. If it's going to advertise itself as USERSET then
it darn well ought to be settable.
The idea of loading the strict module unconditionally seems ok to me,
if we can work out a way of making it apply or not apply to individual
function compilations. From what you were saying, perhaps it would
work to implicitly add "strict->import();" when use_strict is enabled?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
