From f9e949fde3ede2344392f8b4159fabb7744bbffb Mon Sep 17 00:00:00 2001 From: Karl Williamson Date: Thu, 25 Feb 2010 19:17:57 -0700 Subject: [PATCH] Revise wording about /x caveats --- pod/perlre.pod | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) 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. And note that C doesn't affect whether space interpretation within a single multi-character construct. For example in C<\x{...}>, regardless of the C modifier, there can be no spaces. Same for a L 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, 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, 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. X =head2 Regular Expressions -- 2.7.4