From: M.J.T. Guy Date: Fri, 5 Sep 1997 00:00:00 +0000 (+0000) Subject: perlop pod inconsistent in presentation of regexp options X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=b7e30b65e77616e7336a6cda54d9c3d5935d0cfc;p=p5sagit%2Fp5-mst-13.2.git perlop pod inconsistent in presentation of regexp options ts 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 etc, I submit the following micropatch. Credited: Hans Mulder Credited: John Redford p5p-msgid: E0wwnqc-00057s-00@ursa.cus.cam.ac.uk --- diff --git a/pod/perlop.pod b/pod/perlop.pod index 2709a9e..5685902 100644 --- 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.) 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 modifier (e.g. C). Modifying the target string also resets the search position.