perlop pod inconsistent in presentation of regexp options

ts <decoux@moulon.inra.fr> wrote
> man perlop :
>
>            entry in the perlfunc manpage.)  A failed match
>            normally resets the search position to the beginning
>            of the string, but you can avoid that by adding the
>            "c" modifier (e.g. m//gc).  Modifying the target
>            string also resets the search position.

Doh!   Didn't see that.  My excuse is that a search for "/c" doesn't find
it.    And since all other modifiers are referred to as C</g> etc, I
submit the following micropatch.

Credited: Hans Mulder <hansm@icgned.nl>
Credited: John Redford <jmr@whirlwind.fmr.com>

p5p-msgid: E0wwnqc-00057s-00@ursa.cus.cam.ac.uk

diff --git a/pod/perlop.pod b/pod/perlop.pod
index 2709a9e..5685902 100644 (file)
--- a/pod/perlop.pod
+++ b/pod/perlop.pod
@@ -702,7 +702,7 @@ each time it matches, and FALSE when it eventually runs out of matches.
 the search at that point.  You can actually find the current match
 position of a string or set it using the pos() function; see
 L<perlfunc/pos>.)  A failed match normally resets the search position to
-the beginning of the string, but you can avoid that by adding the "c"
+the beginning of the string, but you can avoid that by adding the C</c>
 modifier (e.g. C<m//gc>).  Modifying the target string also resets the
 search position.