From: Karl Williamson <khw@khw-desktop.(none)>
Date: Fri, 26 Feb 2010 02:17:57 +0000 (-0700)
Subject: Revise wording about /x caveats
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=f9e949fde3ede2344392f8b4159fabb7744bbffb;p=p5sagit%2Fp5-mst-13.2.git

Revise wording about /x caveats
---

diff --git a/pod/perlre.pod b/pod/perlre.pod
index 7417b35..c675186 100644
--- a/pod/perlre.pod
+++ b/pod/perlre.pod
@@ -99,11 +99,13 @@ a C<\Q...\E> stays unaffected by C</x>.  And note that C</x> doesn't affect
 whether space interpretation within a single multi-character construct.  For
 example in C<\x{...}>, regardless of the C</x> modifier, there can be no
 spaces.  Same for a L<quantifier|Quantifiers> such as C<{3}> or
-C<{5,}>.  Similarly, C<(?:...)> can't have a space between the C<?> and C<:>.
-Within any delimiters for such a construct, allowed spaces are not affected by
-C</x>, and depend on the construct.  For example, C<\x{...}> can't have spaces
-because hexadecimal numbers don't have spaces in them.  But, in C<\p{...}>  the
-C<...> can have spaces that follow the Unicode properties rules.
+C<{5,}>.  Similarly, C<(?:...)> can't have a space between the C<?> and C<:>,
+but can between the C<(> and C<?>.  Within any delimiters for such a
+construct, allowed spaces are not affected by C</x>, and depend on the
+construct.  For example, C<\x{...}> can't have spaces because hexadecimal
+numbers don't have spaces in them.  But, Unicode properties can have spaces, so
+in C<\p{...}>  there can be spaces that follow the Unicode rules, for which see
+L<perluniprops.pod/Properties accessible through \p{} and \P{}>.
 X</x>
 
 =head2 Regular Expressions