> So I don't think that Python's stupidity is a good argument against > this, unless the stupidity is really unavoidable. Don't get me wrong. I think that the "global variable by default" thing is outdated, especially with how advanced the rest of Perl 6 is. If it can be done right, let's do it. I hate suggesting work, but it sounds like you've got a really good handle on this. The current RFCs (6 and 16) only address whether or not strict should be on or off. Do you have any interest in writing an RFC that fully details how we could fundamentally change the way variables are scoped? If not, I'll put one together. I think we need a 3rd viewpoint to make this discussion worthwhile. -Nate
- Re: RFC 16 (v1) Keep default Perl free of co... Peter Scott
- C<strict> as default (was Re: RFC... Daniel Chetlin
- Re: C<strict> as default (was... J. David Blackstone
- Re: C<strict> as default (was... mjd-perl-list-language-strict
- Re: C<strict> as default ... Nathan Wiger
- Re: C<strict> as defa... mjd-perl-list-lang-strict
- Re: C<strict> as... Nathan Wiger
- Re: C<strict>... mjd-perl-list-language-strict
- Re: C<strict> as... Nathan Wiger
- Clarification on Defau... Nathan Wiger
- Re: Clarification ... Mark-Jason Dominus
- Re: Clarificat... Peter Scott
- Re: Clarification ... mjd-perl-list-language-strict
- Re: Clarificat... Ted Ashton
- Re: Clarificat... Bart Lateur
- Re: Clarificat... Ted Ashton
- Re: Clarificat... Bart Lateur
