>Simple solution. >If you want to require formats such as m/.../ (which I actually think is a >good idea), then make it part of -w, -W, -ww, or -WW, which would be a perl6 >enhancement of strictness. That's like having "use strict" enable mandatory perlstyle compliance checks, and rejecting the program otherwise. Doesn't seem sensible. --tom
- Re: RFC 164 (v1) Replace =~, !~, m//, and s//... Nathan Torkington
- Re: RFC 164 (v1) Replace =~, !~, m//, and... Nathan Wiger
- Re: RFC 164 (v1) Replace =~, !~, m//, and s/// with ma... Jonathan Scott Duff
- Re: RFC 164 (v1) Replace =~, !~, m//, and s/// wi... Nathan Wiger
- Re: RFC 164 (v1) Replace =~, !~, m//, and s//... Jonathan Scott Duff
- Re: RFC 164 (v1) Replace =~, !~, m//, and s//... Tom Christiansen
- Re: RFC 164 (v1) Replace =~, !~, m//, and... Nathan Wiger
- Re: RFC 164 (v1) Replace =~, !~, m//,... 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 Perl++ ... Nathan Wiger
- Re: RFC 164 (v1) Replace =~,... Tom Christiansen
- Re: RFC 164 (v1) Replace =~,... Chaim Frenkel
- Re: RFC 164 (v1) Replace =~,... Mark-Jason Dominus
- Re: RFC 164 (v1) Replace =~, !~,... Nathan Wiger