Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions pod/perlrecharclass.pod
Original file line number Diff line number Diff line change
Expand Up @@ -1040,7 +1040,7 @@ This will match all the digit characters that are in the Thai script.
This feature became available in Perl 5.18, as experimental; accepted in
5.36.

The rules used by L<C<use re 'strict>|re/'strict' mode> apply to this
The rules used by L<C<use re 'strict'>|re/'strict' mode> apply to this
construct.

We can extend the example above:
Expand Down Expand Up @@ -1069,7 +1069,7 @@ There is one unary operator:

! complement

All the binary operators left associate; C<"&"> is higher precedence
All the binary operators left associate; C<&> is higher precedence
than the others, which all have equal precedence. The unary operator
right associates, and has highest precedence. Thus this follows the
normal Perl precedence rules for logical operators. Use parentheses to
Expand Down Expand Up @@ -1102,7 +1102,7 @@ All the other escapes accepted by normal bracketed character classes are
accepted here as well.

Because this construct compiles under
L<C<use re 'strict>|re/'strict' mode>, unrecognized escapes that
L<C<use re 'strict'>|re/'strict' mode>, unrecognized escapes that
generate warnings in normal classes are fatal errors here, as well as
all other warnings from these class elements, as well as some
practices that don't currently warn outside C<re 'strict'>. For example
Expand All @@ -1120,7 +1120,7 @@ raised, as the result is not Unicode-defined. No such warning will come
when using this extended form.

The final difference between regular bracketed character classes and
these, is that it is not possible to get these to match a
these is that it is not possible to get these to match a
multi-character fold. Thus,

/(?[ [\xDF] ])/iu
Expand All @@ -1133,7 +1133,7 @@ hence both of the following work:
/(?[ [:word:] - [:lower:] ])/
/(?[ [[:word:]] - [[:lower:]] ])/

Any contained POSIX character classes, including things like C<\w> and C<\D>
Any contained POSIX character classes, including things like C<\w> and C<\D>,
respect the C<E<sol>a> (and C<E<sol>aa>) modifiers.

Note that C<< (?[ ]) >> is a regex-compile-time construct. Any attempt
Expand All @@ -1145,7 +1145,7 @@ just three limitations:

=item 1

When compiled within the scope of C<use locale> (or the C<E<sol>l> regex
When compiled within the scope of L<C<use locale>|locale> (or the C<E<sol>l> regex
modifier), this construct assumes that the execution-time locale will be
a UTF-8 one, and the generated pattern always uses Unicode rules. What
gets matched or not thus isn't dependent on the actual runtime locale, so
Expand All @@ -1163,15 +1163,15 @@ properties).
=item 3

A regular expression that otherwise would compile
using C<E<sol>d> rules, and which uses this construct will instead
using C<E<sol>d> rules and which uses this construct will instead
use C<E<sol>u>. Thus this construct tells Perl that you don't want
C<E<sol>d> rules for the entire regular expression containing it.

=back

Note that skipping white space applies only to the interior of this
construct. There must not be any space between any of the characters
that form the initial C<(?[>. Nor may there be space between the
that form the initial C<(?[>, nor may there be space between the
closing C<])> characters.

Just as in all regular expressions, the pattern can be built up by
Expand Down
Loading