Tom Christiansen wrote:
>
> >Tom Christiansen wrote:
> >>
> >> >It happens when I don't bother to declare something. My company has
> >> >several dozen machines with an 'our'-less perl, and 'use vars qw($x)' is
> >> >a pain. As is $My::Package::Name::x.
> >>
> >> Far, far easier to fix behavioral problems than to hack Perl.
> >>
> >> --tom
>
> >Not sure what you mean, since this RFC _adds_ a warning in this case. In
> >fact, with the proposed change, my trick to avoid punishment for my
> >misbehavior would no longer work.
>
> >The point is that if
>
> >$x = 3;
>
> >elicits a warning...
>
> ....that you should declare the variable properly, of course.
I want a similar warning for a file containing only
my $x = 3;
And for a file containing only
my $x = 3;
$x = 3;
Do you think this would be useless? Or do you think that it would report
too many spurious warnings? Or do you think it would confuse people? I'm
having trouble figuring out what your position is, other than not
wanting uninitialized values to be any different from undefined values.
In your opinion, is the RFC without merit, or are you objecting only to
parts of it?
