Skip to content
Browse files

s// -> s/// from jlaire++

  • Loading branch information...
1 parent 6faacb9 commit e8bea71b6d8799febb5070dd4b36afa842695699 @TimToady TimToady committed Jun 29, 2011
Showing with 3 additions and 3 deletions.
  1. +3 −3 S05-regex.pod
View
6 S05-regex.pod
@@ -630,7 +630,7 @@ These principle result in the following rules:
The C<:ignorecase>, C<:ignoremark>, C<:sigspace>, C<:ratchet> and C<:Perl5>
modifiers and their short forms are allowed everywhere: inside a regex,
-and on C<m//>, C<rx//> and C<s//> constructs. An implementation may require
+and on C<m//>, C<rx//> and C<s///> constructs. An implementation may require
that their value is known at compile time, and give a compile-time error
message if that is not the case.
@@ -652,7 +652,7 @@ allowed on matches (ie C<m//>), not on substitutions or regex quotes.
=item *
The C<:pos>, C<:continue>, C<:x> and C<:nth> modifiers and their aliases are
-only allowed on constructs that involve immediate calls, eg. C<m//> and C<s//>
+only allowed on constructs that involve immediate calls, eg. C<m//> and C<s///>
(but not on C<rx//>).
=item *
@@ -2420,7 +2420,7 @@ and these are equivalent to
$string ~~ m/^ <.ws> \d+: <.ws> $/;
The basic rule of thumb is that the keyword-defined methods never
-do implicit C<.*?>-like scanning, while the C<m//> and C<s//>
+do implicit C<.*?>-like scanning, while the C<m//> and C<s///>
quotelike forms do such scanning in the absence of explicit anchoring.
The C<rx//> and C<//> forms can go either way: they scan when used

0 comments on commit e8bea71

Please sign in to comment.
Something went wrong with that request. Please try again.