On Tuesday 20 February 2001 16:03, John Porter wrote:
> Bryan C. Warnock wrote:
> >
> > And there's a difference between warnings originating because something
has
> > gone wrong and those originating because I'm doing something
particularly
> > perlish. Unfortunately, -w doesn't (and probably can't) tell the
> > difference.
>
> Can you give me an example of the former?
> I can't think of any off the top of my head.
Scalar value @foo[$bar] better written as $foo[$bar], for one.
(But you probably would have thought of that if I had said something better
than "something has gone wrong" which doesn't describe the above at all.
I'm sorry, a completely horrible phrasing of what I was trying to say -
I'll take me out back and shoot me now.)
I'll try this again - the difference between a perceived user error, and a
misused perl construct. The above error reflects an inability to
distinguish between mulitple typos: either $foo or a list index.
If part of Perl's breeding is autovivication and interpretation of undef as
0 or "" in the appropriate context, why should Perl bitch at me if I use it
as such? Why should I have to ask permission to do so?
I would rather say, and I think it would be more perlish to say, "I'm not
feeling particularly perly today, can you check for anything clever, cause
if there is, chances are it's a mistake."
--
Bryan C. Warnock
[EMAIL PROTECTED]
