Add x-references in pods to new /a, etc.

2 files changed, 13 insertions, 1 deletions

diff --git a/pod/perlop.pod b/pod/perlop.pod
index 709f6a89f5..eb71b89a83 100644
--- a/pod/perlop.pod
+++ b/pod/perlop.pod
@@ -1332,6 +1332,13 @@ of 'msixp' will be propagated appropriately.  The effect of the 'o'
 modifier has is not propagated, being restricted to those patterns
 explicitly using it.
 
+Several other modifiers to control the character set semantics were
+added for 5.14 that, unlike the ones listed above,  may not be used
+after the final pattern delimiter, but only following a C<"(?"> inside
+the regular expression.  (It is planned in 5.16 to make them usable in
+the suffix position.)  These are B<C<"a">>, B<C<"d">>, B<C<"l">>, and
+B<C<"u">>.  They are documented in L<perlre/Extended Patterns>.
+
 See L<perlre> for additional information on valid syntax for STRING, and
 for a detailed look at the semantics of regular expressions.
 
diff --git a/pod/perlre.pod b/pod/perlre.pod
index 4b058a2e4c..06388fdc94 100644
--- a/pod/perlre.pod
+++ b/pod/perlre.pod
@@ -79,7 +79,12 @@ of the g and c modifiers.
 These are usually written as "the C</x> modifier", even though the delimiter
 in question might not really be a slash.  Any of these
 modifiers may also be embedded within the regular expression itself using
-the C<(?...)> construct.  See below.
+the C<(?...)> construct.  Also are new (in 5.14) character set semantics
+modifiers B<C<<"a">>, B<C<"d">>, B<C<"l">> and B<C<"u">>, which, in 5.14
+only, must be used embedded in the regular expression, and not after the
+trailing delimiter.  All this is discussed below in
+L</Extended Patterns>.
+X</a> X</d> X</l> X</u>
 
 The C</x> modifier itself needs a little more explanation.  It tells
 the regular expression parser to ignore most whitespace that is neither