> I'm not concerned about / being mistaken for division, since that > ambiguity already exists with bare /pat/ matches. Yes, but the current ambiguity is resolved from context in a rather complicated way. Nevertheless it turns out that Perl does the right thing in most cases. You are proposing to change the context, and it's not clear that the result will be the right thing as often as in the past. It may turn out that the new notation really does have exactly the same ambiguities, but that's not clear to me now. All I said was that I would like to see some discussion of it.
- Re: RFC 138 (v1) Eliminate =~ operator. Damian Conway
- Re: RFC 138 (v1) Eliminate =~ operator. Nathan Wiger
- Re: RFC 138 (v1) Eliminate =~ operator. Steve Fink
- Re: RFC 138 (v1) Eliminate =~ operator. Nathan Wiger
- Re: RFC 138 (v1) Eliminate =~ operator. Nathan Torkington
- Re: RFC 138 (v1) Eliminate =~ operator. Nathan Wiger
- Re: RFC 138 (v1) Eliminate =~ operator... Nathan Torkington
- Re: RFC 138 (v1) Eliminate =~ operator... Tom Christiansen
- Re: RFC 138 (v1) Eliminate =~ operator... Nathan Torkington
- Re: RFC 138 (v1) Eliminate =~ operator... Nathan Wiger
- Re: RFC 138 (v1) Eliminate =~ operator. Mark-Jason Dominus
- Re: RFC 138 (v1) Eliminate =~ operator. Larry Wall
- Re: RFC 138 (v1) Eliminate =~ operator. Piers Cawley
- Re: RFC 138 (v1) Eliminate =~ operator. Tom Christiansen
- working mnemonic for =~ David L. Nicol