Mark-Jason Dominus wrote: > > RFC135: Require explicit m on matches, even with ?? and // as delimiters. This one is along a different line from these two: > RFC138: Eliminate =~ operator. > RFC164: Replace =~, !~, m//, and s/// with match() and subst() Which I could see unifying. I'd ask people to wait until v2 of RFC 164 comes up. It may well include everything from RFC 138 already. -Nate
- Overlapping RFCs 135 138 164 Mark-Jason Dominus
- Re: Overlapping RFCs 135 138 164 Stephen P. Potter
- Re: Overlapping RFCs 135 138 164 Nathan Wiger
- Re: Overlapping RFCs 135 138 164 Steve Fink
- Re: Overlapping RFCs 135 138 164 Tom Christiansen
- Re: Overlapping RFCs 135 138 164 Tom Christiansen
- Re: Overlapping RFCs 135 138 164 Uri Guttman
- Re: Overlapping RFCs 135 138 164 Tom Christiansen
- copying and s/// (was Re: Ove... Uri Guttman
- Re: copying and s/// (was... Nathan Wiger
- Re: copying and s/// (was... Brad Hughes
- Re: copying and s/// (was... Mike Lambert
- Re: copying and s/// (was... Nathan Wiger