summaryrefslogtreecommitdiff
path: root/Master/tlpkg/tlperl/lib/pods/perlreapi.pod
diff options
context:
space:
mode:
Diffstat (limited to 'Master/tlpkg/tlperl/lib/pods/perlreapi.pod')
-rw-r--r--Master/tlpkg/tlperl/lib/pods/perlreapi.pod35
1 files changed, 20 insertions, 15 deletions
diff --git a/Master/tlpkg/tlperl/lib/pods/perlreapi.pod b/Master/tlpkg/tlperl/lib/pods/perlreapi.pod
index d1d947b8a74..1c694a72318 100644
--- a/Master/tlpkg/tlperl/lib/pods/perlreapi.pod
+++ b/Master/tlpkg/tlperl/lib/pods/perlreapi.pod
@@ -120,21 +120,26 @@ TODO: Document those cases.
=item C</p> - RXf_PMf_KEEPCOPY
+=item Character set
+
+The character set semantics are determined by an enum that is contained
+in this field. This is still experimental and subject to change, but
+the current interface returns the rules by use of the in-line function
+C<get_regex_charset(const U32 flags)>. The only currently documented
+value returned from it is REGEX_LOCALE_CHARSET, which is set if
+C<use locale> is in effect. If present in C<< rx->extflags >>
+C<split> will use the locale dependent definition of whitespace under
+when RXf_SKIPWHITE or RXf_WHITE are in effect. Under ASCII whitespace
+is defined as per L<isSPACE|perlapi/isSPACE>, and by the internal
+macros C<is_utf8_space> under UTF-8 and C<isSPACE_LC> under C<use
+locale>.
+
=back
Additional flags:
=over 4
-=item RXf_PMf_LOCALE
-
-Set if C<use locale> is in effect. If present in C<< rx->extflags >>
-C<split> will use the locale dependent definition of whitespace under
-when RXf_SKIPWHITE or RXf_WHITE are in effect. Under ASCII whitespace
-is defined as per L<isSPACE|perlapi/ISSPACE>, and by the internal
-macros C<is_utf8_space> under UTF-8 and C<isSPACE_LC> under C<use
-locale>.
-
=item RXf_UTF8
Set if the pattern is L<SvUTF8()|perlapi/SvUTF8>, set by Perl_pmruntime.
@@ -243,7 +248,7 @@ perl will handle releasing anything else contained in the regexp structure.
Called to get/set the value of C<$`>, C<$'>, C<$&> and their named
equivalents, ${^PREMATCH}, ${^POSTMATCH} and $^{MATCH}, as well as the
-numbered capture buffers (C<$1>, C<$2>, ...).
+numbered capture groups (C<$1>, C<$2>, ...).
The C<paren> parameter will be C<-2> for C<$`>, C<-1> for C<$'>, C<0>
for C<$&>, C<1> for C<$1> and so forth.
@@ -317,7 +322,7 @@ behave in the same situation:
package main;
- tie my $sv => "CatptureVar";
+ tie my $sv => "CaptureVar";
$sv =~ y/a/b/;
Because C<$sv> is C<undef> when the C<y///> operator is applied to it
@@ -492,7 +497,7 @@ values.
in the final match, used for optimisations */
struct reg_substr_data *substrs;
- U32 nparens; /* number of capture buffers */
+ U32 nparens; /* number of capture groups */
/* private engine specific data */
U32 intflags; /* Engine Specific Internal flags */
@@ -612,7 +617,7 @@ C<regexp_paren_pair> struct is defined as follows:
} regexp_paren_pair;
If C<< ->offs[num].start >> or C<< ->offs[num].end >> is C<-1> then that
-capture buffer did not match. C<< ->offs[0].start/end >> represents C<$&> (or
+capture group did not match. C<< ->offs[0].start/end >> represents C<$&> (or
C<${^MATCH> under C<//p>) and C<< ->offs[paren].end >> matches C<$$paren> where
C<$paren >= 1>.
@@ -633,7 +638,7 @@ The relevant snippet from C<Perl_pp_regcomp>:
=head2 C<paren_names>
-This is a hash used internally to track named capture buffers and their
+This is a hash used internally to track named capture groups and their
offsets. The keys are the names of the buffers the values are dualvars,
with the IV slot holding the number of buffers with the given name and the
pv being an embedded array of I32. The values may also be contained
@@ -655,7 +660,7 @@ Used during execution phase for managing search and replace patterns.
=head2 C<wrapped> C<wraplen>
Stores the string C<qr//> stringifies to. The perl engine for example
-stores C<(?-xism:eek)> in the case of C<qr/eek/>.
+stores C<(?^:eek)> in the case of C<qr/eek/>.
When using a custom engine that doesn't support the C<(?:)> construct
for inline modifiers, it's probably best to have C<qr//> stringify to