summaryrefslogtreecommitdiff
path: root/pod/perlfilter.pod
diff options
context:
space:
mode:
authorKarl Williamson <khw@cpan.org>2017-02-16 19:30:08 -0700
committerKarl Williamson <khw@cpan.org>2017-02-20 09:08:54 -0700
commitf1dc5bb2995ecccb5fa0346ca80f01f09aaa3e9d (patch)
treeafd9d8fdb26794366402e77cf9ac8a2dc2b74f4b /pod/perlfilter.pod
parent52b4b0e0361aa3b508faa5976f08af4626cd49ae (diff)
downloadperl-f1dc5bb2995ecccb5fa0346ca80f01f09aaa3e9d.tar.gz
Pods: Standardize on one pattern mod style
There were about 40 cases in pods where //m is used to represent the pattern modifier 'm', but nearly 400 where /m is used. Convert to the most common representation.
Diffstat (limited to 'pod/perlfilter.pod')
-rw-r--r--pod/perlfilter.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlfilter.pod b/pod/perlfilter.pod
index 60d086401c..b61b6f97b0 100644
--- a/pod/perlfilter.pod
+++ b/pod/perlfilter.pod
@@ -562,7 +562,7 @@ or the byteloader, to translate binary code back to source code.
See for example the limitations in L<Switch>, which uses source filters,
and thus is does not work inside a string eval, the presence of
regexes with embedded newlines that are specified with raw C</.../>
-delimiters and don't have a modifier C<//x> are indistinguishable from
+delimiters and don't have a modifier C</x> are indistinguishable from
code chunks beginning with the division operator C</>. As a workaround
you must use C<m/.../> or C<m?...?> for such patterns. Also, the presence of
regexes specified with raw C<?...?> delimiters may cause mysterious