Tom Christiansen wrote: > > There are thirteen years of precedent, not to mention the millions of users, > who are completely accustomed to writing expressions like > > next if /\s+/ || /\w+/; > > It's nearly part of Perl's language signature. I wouldn't count > on this going away if you still think to call this "Perl". It is > of course much more likely in the renamed "Frob" language, however. First off, this argument is just a little too grandiose, because if we can't change anything because of precedent, then we're stuck and Perl 6 should just be Perl 5.9 instead. That being said, I don't see why this wouldn't work still. As I noted in an email to Scott, at the very least this will work: next if m/\s+/ || m/\w+/; And if we want to special case // still that's fine with me. -Nate
- RFC 164 (v1) Replace =~, !~, m//, and s/// with match(... Perl6 RFC Librarian
- Re: RFC 164 (v1) Replace =~, !~, m//, and s/// wi... Nathan Wiger
- Re: RFC 164 (v1) Replace =~, !~, m//, and s/// wi... Nathan Torkington
- Re: RFC 164 (v1) Replace =~, !~, m//, and s//... Nathan Wiger
- Re: RFC 164 (v1) Replace =~, !~, m//, and... Nathan Torkington
- Re: RFC 164 (v1) Replace =~, !~, m//,... Nathan Wiger
- Re: RFC 164 (v1) Replace =~, !~, m//, and s/// wi... Jonathan Scott Duff
- Re: RFC 164 (v1) Replace =~, !~, m//, and s//... Nathan Wiger
- Re: RFC 164 (v1) Replace =~, !~, m//, and... Jonathan Scott Duff
- Re: RFC 164 (v1) Replace =~, !~, m//, and... Tom Christiansen
- Re: RFC 164 (v1) Replace =~, !~, m//,... Nathan Wiger
- Re: RFC 164 (v1) Replace =~, !~,... Tom Christiansen
- Re: RFC 164 (v1) Replace =~,... Richard Proctor
- Re: RFC 164 (v1) Replace... Michael Maraist
- Re: RFC 164 (v1) Replace... Tom Christiansen
- Re: RFC 164 (v1) Replace... Michael Maraist
- Re: RFC 164 (v1) Replace... Nathan Torkington
- Re: RFC 164 (v1) Replace... Tom Christiansen
- Re: RFC 164 (v1) Replace... Nathan Torkington
- Creating Perl 6, not Per... Nathan Wiger
- Re: RFC 164 (v1) Replace... Tom Christiansen