> I do *NOT* think in any way that default Perl 6 should ever require a my().
I should probably add here that if this is what you think, you are
certainly doomed to be disappointed, becapse Perl 5 requires my() in
many cases, and this is not going to go away.
For example, there is no way to write this without my():
$x = 2;
if (...) {
my $x = 1;
...
}
print "$x\n";
So I think it might be prudent for you to moderate your demands a little.
Re: Clarification on Default Scoping (was Re: C as default (was Re: RFC 16 (v1)))
mjd-perl-list-language-strict Sat, 05 Aug 2000 12:11:48 -0700
- Re: C<strict> as default (was Re: RFC ... J. David Blackstone
- Re: C<strict> as default (was Re: RFC ... mjd-perl-list-language-strict
- Re: C<strict> as default (was Re:... Nathan Wiger
- Re: C<strict> as default (was... mjd-perl-list-lang-strict
- Re: C<strict> as default ... Nathan Wiger
- Re: C<strict> as defa... mjd-perl-list-language-strict
- Re: C<strict> as default ... Nathan Wiger
- Clarification on Default Scopin... Nathan Wiger
- Re: Clarification on Defaul... Mark-Jason Dominus
- Re: Clarification on Defaul... Peter Scott
- Re: Clarification on Defaul... mjd-perl-list-language-strict
- Re: Clarification on Defaul... Ted Ashton
- Re: Clarification on Defaul... Bart Lateur
- Re: Clarification on Defaul... Ted Ashton
- Re: Clarification on Defaul... Bart Lateur
- Re: Clarification on Defaul... Monty Taylor
- Re: C<strict> as default (was Re:... Nathan Wiger
- Re: C<strict> as default (was... Michael Stevens
- Re: C<strict> as default ... mjd-perl-list-lang-strict
- Re: C<strict> as defa... Michael Stevens
- Re: C<strict> as defa... Peter Scott
