RFC135: Require explicit m on matches, even with ?? and // as delimiters.
C<?...?> and C</.../> are what makes Perl hard to tokenize.
Requiring them to be written C<m?...?> and C<m/.../> would
solve this.
(Nathan Torkington)
RFC138: Eliminate =~ operator.
Replace EXPR =~ m/.../ with m/.../ EXPR, and similarly for
s/// and tr///. Force an explicit dereference when using
qr/.../. Disallow the implicit treatment of a string as a
regular expression to match against.
(Steve Fink)
RFC164: Replace =~, !~, m//, and s/// with match() and subst()
Several people (including Larry) have expressed a desire to
get rid of C<=~> and C<!~>. This RFC proposes a way to replace
C<m//> and C<s///> with two new builtins, C<match()> and
C<subst()>.
(Nathan Widger)
I would like to see these three RFCs merged into one if this is
appropriate. I am calling on the three authors to discuss in private
email how this may be done. I hope that the discussion will result in
the withdrawal at least two of the three RFCs, and that this private
discussion produces a new RFC. The new RFC should discuss the points
raised by all three existing RFCs, should investigate several
solutions in parallel, and should compare them with one another and
contrast the benefits and drawbacks of each one.
Mark-Jason Dominus [EMAIL PROTECTED]
I am boycotting Amazon. See http://www.plover.com/~mjd/amazon.html for details.
