Nathan Wiger writes:
> I argue we should fundamentally shift this thinking in Perl 6. Let's
> truly have "lexical variables made default".

Ugh.  Baby, bathwater.

If I'm writing a big program, then I want to have to declare all
variables so that Perl can catch errors for me.  That's the big
benefit of strict.  Otherwise you're still going to make typos and
have a bugger of a time tracking them down, because the compiler won't
be helping you do it.

You've taken the wrong approach.  If you're writing a big program then
there should be *no* default scope.  Any variable access is an error
unless that variable was my()ed or our()ed.  That's basically what
'strict' gives us.

The only thing I think we should argue is whether strict should be
default or not.  I could fall both ways.  If there was a command-line
switch to turn it off, then I'd be happy with strict as the default.

Nat

Reply via email to