Re: [ID 20000111.008] use strict 'vars'

[Steve Fink <sfink@digital-integrity.com>]

From the number of cheap shots TomC has been making recently, I'd say
something has him in a bad mood. But that aside, has everyone given up
hope on backwards-compatibly catching $a and $b problems?

<strawman> Warn on uses at the toplevel scope (or scopes without a
subroutine definition ancestor). Queue up the warnings for all other
scopes, and track which things are definitely used as sort subs in the
same compile. Wipe those out, and emit the remaining warnings at the end
of the compile. Don't worry about the cases that slip through the
cracks. </strawman>

Maybe that's totally insane, I don't know.

Given that this "bug" report arises so frequently, why was I unable to
find any mention in the 5.5.62 docs? I didn't try that hard, but no
perlfaq entry, no mention in strict.pm, no perltrap entry. The following
are people's strict.pm patches -- why aren't they in?:

http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/1999-12/msg00009.html
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/1999-12/msg00179.html

There is a mention in perlfunc, but judging from the number of reports,
that's not enough. It strikes me as wartlike enough in behavior to merit
quite a few notices in the documentation.

---

References to:

london@pixelmagic.com

---

[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index][Thread Index][Top&Search][Original]

---