3 perlreapi - perl regular expression plugin interface
7 As of Perl 5.9.5 there is a new interface for using other regexp engines than
8 the default one. Each engine is supposed to provide access to a constant
9 structure of the following format:
11 typedef struct regexp_engine {
12 REGEXP* (*comp) (pTHX_ const SV * const pattern, const U32 flags);
13 I32 (*exec) (pTHX_ REGEXP * const rx, char* stringarg, char* strend,
14 char* strbeg, I32 minend, SV* screamer,
15 void* data, U32 flags);
16 char* (*intuit) (pTHX_ REGEXP * const rx, SV *sv, char *strpos,
17 char *strend, U32 flags,
18 struct re_scream_pos_data_s *data);
19 SV* (*checkstr) (pTHX_ REGEXP * const rx);
20 void (*free) (pTHX_ REGEXP * const rx);
21 void (*numbered_buff_FETCH) (pTHX_ REGEXP * const rx, const I32 paren,
23 void (*numbered_buff_STORE) (pTHX_ REGEXP * const rx, const I32 paren,
24 SV const * const value);
25 I32 (*numbered_buff_LENGTH) (pTHX_ REGEXP * const rx, const SV * const sv,
27 SV* (*named_buff_FETCH) (pTHX_ REGEXP * const rx, SV * const sv,
29 SV* (*qr_package)(pTHX_ REGEXP * const rx);
31 void* (*dupe) (pTHX_ REGEXP * const rx, CLONE_PARAMS *param);
34 When a regexp is compiled, its C<engine> field is then set to point at
35 the appropriate structure so that when it needs to be used Perl can find
36 the right routines to do so.
38 In order to install a new regexp handler, C<$^H{regcomp}> is set
39 to an integer which (when casted appropriately) resolves to one of these
40 structures. When compiling, the C<comp> method is executed, and the
41 resulting regexp structure's engine field is expected to point back at
44 The pTHX_ symbol in the definition is a macro used by perl under threading
45 to provide an extra argument to the routine holding a pointer back to
46 the interpreter that is executing the regexp. So under threading all
47 routines get an extra argument.
53 REGEXP* comp(pTHX_ const SV * const pattern, const U32 flags);
55 Compile the pattern stored in C<pattern> using the given C<flags> and
56 return a pointer to a prepared C<REGEXP> structure that can perform
57 the match. See L</The REGEXP structure> below for an explanation of
58 the individual fields in the REGEXP struct.
60 The C<pattern> parameter is the scalar that was used as the
61 pattern. previous versions of perl would pass two C<char*> indicating
62 the start and end of the stringifed pattern, the following snippet can
63 be used to get the old parameters:
66 char* exp = SvPV(pattern, plen);
67 char* xend = exp + plen;
69 Since any scalar can be passed as a pattern it's possible to implement
70 an engine that does something with an array (C<< "ook" =~ [ qw/ eek
71 hlagh / ] >>) or with the non-stringified form of a compiled regular
72 expression (C<< "ook" =~ qr/eek/ >>). perl's own engine will always
73 stringify everything using the snippet above but that doesn't mean
74 other engines have to.
76 The C<flags> paramater is a bitfield which indicates which of the
77 C<msixk> flags the regex was compiled with. In addition it contains
78 info about whether C<use locale> is in effect and optimization info
79 for C<split>. A regex engine might want to use the same split
80 optimizations with a different syntax, for instance a Perl6 engine
81 would treat C<split /^^/> equivalently to perl's C<split /^/>, see
82 L<split documentation|perlfunc> and the relevant code in C<pp_split>
83 in F<pp.c> to find out whether your engine should be setting these.
85 The C<eogc> flags are stripped out before being passed to the comp
86 routine. The regex engine does not need to know whether any of these
87 are set as those flags should only affect what perl does with the
88 pattern and its match variables, not how it gets compiled & executed.
94 C<split ' '> or C<split> with no arguments (which really means
95 C<split(' ', $_> see L<split|perlfunc>).
99 Set if the pattern is C</^/> (C<<r->prelen == 1 && r->precomp[0] ==
100 '^'>>). Will be used by the C<split> operator to split the given
101 string on C<\n> (even under C</^/s>, see L<split|perlfunc>).
105 Set if the pattern is exactly C</\s+/> and used by C<split>, the
106 definition of whitespace varies depending on whether RXf_UTF8 or
107 RXf_PMf_LOCALE is set.
111 Makes C<split> use the locale dependant definition of whitespace under C<use
112 locale> when RXf_SKIPWHITE or RXf_WHITE is in effect. Under ASCII whitespace is
113 defined as per L<isSPACE|perlapi/ISSPACE>, and by the internal macros
114 C<is_utf8_space> under UTF-8 and C<isSPACE_LC> under C<use locale>.
116 =item RXf_PMf_MULTILINE
118 The C</m> flag, this ends up being passed to C<Perl_fbm_instr> by
119 C<pp_split> regardless of the engine.
121 =item RXf_PMf_SINGLELINE
123 The C</s> flag. Guaranteed not to be used outside the regex engine.
127 The C</i> flag. Guaranteed not to be used outside the regex engine.
129 =item RXf_PMf_EXTENDED
131 The C</x> flag. Guaranteed not to be used outside the regex
132 engine. However if present on a regex C<#> comments will be stripped
133 by the tokenizer regardless of the engine currently in use.
135 =item RXf_PMf_KEEPCOPY
141 Set if the pattern is L<SvUTF8()|perlapi/SvUTF8>, set by Perl_pmruntime.
145 In general these flags should be preserved in C<< rx->extflags >>
146 after compilation, although it is possible the regex includes
147 constructs that changes them. The perl engine for instance may upgrade
148 non-utf8 strings to utf8 if the pattern includes constructs such as
149 C<\x{...}> that can only match unicode values. RXf_SKIPWHITE should
150 always be preserved verbatim in C<< regex->extflags >>.
154 I32 exec(pTHX_ REGEXP * const rx,
155 char *stringarg, char* strend, char* strbeg,
156 I32 minend, SV* screamer,
157 void* data, U32 flags);
163 char* intuit(pTHX_ REGEXP * const rx,
164 SV *sv, char *strpos, char *strend,
165 const U32 flags, struct re_scream_pos_data_s *data);
167 Find the start position where a regex match should be attempted,
168 or possibly whether the regex engine should not be run because the
169 pattern can't match. This is called as appropriate by the core
170 depending on the values of the extflags member of the regexp
175 SV* checkstr(pTHX_ REGEXP * const rx);
177 Return a SV containing a string that must appear in the pattern. Used
178 by C<split> for optimising matches.
182 void free(pTHX_ REGEXP * const rx);
184 Called by perl when it is freeing a regexp pattern so that the engine
185 can release any resources pointed to by the C<pprivate> member of the
186 regexp structure. This is only responsible for freeing private data;
187 perl will handle releasing anything else contained in the regexp structure.
189 =head2 numbered_buff_FETCH
191 void numbered_buff_FETCH(pTHX_ REGEXP * const rx, const I32 paren,
194 Called to get the value of C<$`>, C<$'>, C<$&> (and their named
195 equivalents, see L<perlvar>) and the numbered capture buffers (C<$1>,
198 The C<paren> paramater will be C<-2> for C<$`>, C<-1> for C<$'>, C<0>
199 for C<$&>, C<1> for C<$1> and so forth.
201 C<sv> should be set to the scalar to return, the scalar is passed as
202 an argument rather than being returned from the function because when
203 it's called perl already has a scalar to store the value, creating
204 another one would be redundant. The scalar can be set with
205 C<sv_setsv>, C<sv_setpvn> and friends, see L<perlapi>.
207 This callback is where perl untaints its own capture variables under
208 taint mode (see L<perlsec>). See the C<Perl_reg_numbered_buff_get>
209 function in F<regcomp.c> for how to untaint capture variables if
210 that's something you'd like your engine to do as well.
212 =head2 numbered_buff_STORE
214 void (*numbered_buff_STORE) (pTHX_ REGEXP * const rx, const I32 paren,
215 SV const * const value);
217 Called to set the value of a numbered capture variable. C<paren> is
218 the paren number (see the L<mapping|/numbered_buff_FETCH> above) and
219 C<value> is the scalar that is to be used as the new value. It's up to
220 the engine to make sure this is used as the new value (or reject it).
224 if ("ook" =~ /(o*)/) {
225 # `paren' will be `1' and `value' will be `ee'
229 Perl's own engine will croak on any attempt to modify the capture
230 variables, to do this in another engine use the following callack
231 (copied from C<Perl_reg_numbered_buff_store>):
234 Example_reg_numbered_buff_store(pTHX_ REGEXP * const rx, const I32 paren,
235 SV const * const value)
238 PERL_UNUSED_ARG(paren);
239 PERL_UNUSED_ARG(value);
242 Perl_croak(aTHX_ PL_no_modify);
245 Actually perl 5.10 will not I<always> croak in a statement that looks
246 like it would modify a numbered capture variable. This is because the
247 STORE callback will not be called if perl can determine that it
248 doesn't have to modify the value. This is exactly how tied variables
249 behave in the same situation:
252 use base 'Tie::Scalar';
254 sub TIESCALAR { bless [] }
256 sub STORE { die "This doesn't get called" }
260 tie my $sv => "CatptureVar";
263 Because C<$sv> is C<undef> when the C<y///> operator is applied to it
264 the transliteration won't actually execute and the program won't
265 C<die>. This is different to how 5.8 behaved since the capture
266 variables were READONLY variables then, now they'll just die on
267 assignment in the default engine.
269 =head2 numbered_buff_LENGTH
271 I32 numbered_buff_LENGTH (pTHX_ REGEXP * const rx, const SV * const sv,
274 Get the C<length> of a capture variable. There's a special callback
275 for this so that perl doesn't have to do a FETCH and run C<length> on
276 the result, since the length is (in perl's case) known from a memory
277 offset this is much more efficient:
279 I32 s1 = rx->offs[paren].start;
280 I32 s2 = rx->offs[paren].end;
283 This is a little bit more complex in the case of UTF-8, see what
284 C<Perl_reg_numbered_buff_length> does with
285 L<is_utf8_string_loclen|perlapi/is_utf8_string_loclen>.
287 =head2 named_buff_FETCH
289 SV* named_buff_FETCH(pTHX_ REGEXP * const rx, SV * const key,
292 Called to get the value of key in the C<%+> and C<%-> hashes, C<key>
293 is the hash key being requested and if C<flags & 1> is true C<%-> is
294 being requested (and C<%+> if it's not).
298 SV* qr_package(pTHX_ REGEXP * const rx);
300 The package the qr// magic object is blessed into (as seen by C<ref
301 qr//>). It is recommended that engines change this to their package
302 name for identification regardless of whether they implement methods
305 A callback implementation might be:
308 Example_reg_qr_package(pTHX_ REGEXP * const rx)
311 return newSVpvs("re::engine::Example");
314 Any method calls on an object created with C<qr//> will be dispatched to the
315 package as a normal object.
317 use re::engine::Example;
319 $re->meth; # dispatched to re::engine::Example::meth()
321 To retrieve the C<REGEXP> object from the scalar in an XS function use the
332 (sv = (SV*)SvRV(sv)) && /* assignment deliberate */
333 SvTYPE(sv) == SVt_PVMG &&
334 (mg = mg_find(sv, PERL_MAGIC_qr))) /* assignment deliberate */
336 re = (REGEXP *)mg->mg_obj;
339 Or use the (CURRENTLY UNDOCUMENETED!) C<Perl_get_re_arg> function:
343 const REGEXP * const re = (REGEXP *)Perl_get_re_arg( aTHX_ rv, 0, NULL );
347 void* dupe(pTHX_ REGEXP * const rx, CLONE_PARAMS *param);
349 On threaded builds a regexp may need to be duplicated so that the pattern
350 can be used by mutiple threads. This routine is expected to handle the
351 duplication of any private data pointed to by the C<pprivate> member of
352 the regexp structure. It will be called with the preconstructed new
353 regexp structure as an argument, the C<pprivate> member will point at
354 the B<old> private structue, and it is this routine's responsibility to
355 construct a copy and return a pointer to it (which perl will then use to
356 overwrite the field as passed to this routine.)
358 This allows the engine to dupe its private data but also if necessary
359 modify the final structure if it really must.
361 On unthreaded builds this field doesn't exist.
363 =head1 The REGEXP structure
365 The REGEXP struct is defined in F<regexp.h>. All regex engines must be able to
366 correctly build such a structure in their L</comp> routine.
368 The REGEXP structure contains all the data that perl needs to be aware of
369 to properly work with the regular expression. It includes data about
370 optimisations that perl can use to determine if the regex engine should
371 really be used, and various other control info that is needed to properly
372 execute patterns in various contexts such as is the pattern anchored in
373 some way, or what flags were used during the compile, or whether the
374 program contains special constructs that perl needs to be aware of.
376 In addition it contains two fields that are intended for the private
377 use of the regex engine that compiled the pattern. These are the
378 C<intflags> and C<pprivate> members. C<pprivate> is a void pointer to
379 an arbitrary structure whose use and management is the responsibility
380 of the compiling engine. perl will never modify either of these
383 typedef struct regexp {
384 /* what engine created this regexp? */
385 const struct regexp_engine* engine;
387 /* what re is this a lightweight copy of? */
388 struct regexp* mother_re;
390 /* Information about the match that the perl core uses to manage things */
391 U32 extflags; /* Flags used both externally and internally */
392 I32 minlen; /* mininum possible length of string to match */
393 I32 minlenret; /* mininum possible length of $& */
394 U32 gofs; /* chars left of pos that we search from */
396 /* substring data about strings that must appear
397 in the final match, used for optimisations */
398 struct reg_substr_data *substrs;
400 U32 nparens; /* number of capture buffers */
402 /* private engine specific data */
403 U32 intflags; /* Engine Specific Internal flags */
404 void *pprivate; /* Data private to the regex engine which
405 created this object. */
407 /* Data about the last/current match. These are modified during matching*/
408 U32 lastparen; /* last open paren matched */
409 U32 lastcloseparen; /* last close paren matched */
410 regexp_paren_pair *swap; /* Swap copy of *offs */
411 regexp_paren_pair *offs; /* Array of offsets for (@-) and (@+) */
413 char *subbeg; /* saved or original string so \digit works forever. */
414 SV_SAVED_COPY /* If non-NULL, SV which is COW from original */
415 I32 sublen; /* Length of string pointed by subbeg */
417 /* Information about the match that isn't often used */
418 I32 prelen; /* length of precomp */
419 const char *precomp; /* pre-compilation regular expression */
421 /* wrapped can't be const char*, as it is returned by sv_2pv_flags */
422 char *wrapped; /* wrapped version of the pattern */
423 I32 wraplen; /* length of wrapped */
425 I32 seen_evals; /* number of eval groups in the pattern - for security checks */
426 HV *paren_names; /* Optional hash of paren names */
428 /* Refcount of this regexp */
429 I32 refcnt; /* Refcount of this regexp */
432 The fields are discussed in more detail below:
436 This field points at a regexp_engine structure which contains pointers
437 to the subroutines that are to be used for performing a match. It
438 is the compiling routine's responsibility to populate this field before
439 returning the regexp object.
441 Internally this is set to C<NULL> unless a custom engine is specified in
442 C<$^H{regcomp}>, perl's own set of callbacks can be accessed in the struct
443 pointed to by C<RE_ENGINE_PTR>.
447 TODO, see L<http://www.mail-archive.com/perl5-changes@perl.org/msg17328.html>
451 This will be used by perl to see what flags the regexp was compiled with, this
452 will normally be set to the value of the flags parameter on L</comp>.
454 =head2 C<minlen> C<minlenret>
456 The minimum string length required for the pattern to match. This is used to
457 prune the search space by not bothering to match any closer to the end of a
458 string than would allow a match. For instance there is no point in even
459 starting the regex engine if the minlen is 10 but the string is only 5
460 characters long. There is no way that the pattern can match.
462 C<minlenret> is the minimum length of the string that would be found
465 The difference between C<minlen> and C<minlenret> can be seen in the
470 where the C<minlen> would be 3 but C<minlenret> would only be 2 as the \d is
471 required to match but is not actually included in the matched content. This
472 distinction is particularly important as the substitution logic uses the
473 C<minlenret> to tell whether it can do in-place substition which can result in
474 considerable speedup.
478 Left offset from pos() to start match at.
484 =head2 C<nparens>, C<lasparen>, and C<lastcloseparen>
486 These fields are used to keep track of how many paren groups could be matched
487 in the pattern, which was the last open paren to be entered, and which was
488 the last close paren to be entered.
492 The engine's private copy of the flags the pattern was compiled with. Usually
493 this is the same as C<extflags> unless the engine chose to modify one of them
497 A void* pointing to an engine-defined data structure. The perl engine uses the
498 C<regexp_internal> structure (see L<perlreguts/Base Structures>) but a custom
499 engine should use something else.
507 A C<regexp_paren_pair> structure which defines offsets into the string being
508 matched which correspond to the C<$&> and C<$1>, C<$2> etc. captures, the
509 C<regexp_paren_pair> struct is defined as follows:
511 typedef struct regexp_paren_pair {
516 If C<< ->offs[num].start >> or C<< ->offs[num].end >> is C<-1> then that
517 capture buffer did not match. C<< ->offs[0].start/end >> represents C<$&> (or
518 C<${^MATCH> under C<//p>) and C<< ->offs[paren].end >> matches C<$$paren> where
521 =head2 C<precomp> C<prelen>
523 Used for debugging purposes. C<precomp> holds a copy of the pattern
524 that was compiled and C<prelen> its length.
526 =head2 C<paren_names>
528 This is a hash used internally to track named capture buffers and their
529 offsets. The keys are the names of the buffers the values are dualvars,
530 with the IV slot holding the number of buffers with the given name and the
531 pv being an embedded array of I32. The values may also be contained
532 independently in the data array in cases where named backreferences are
535 =head2 C<reg_substr_data>
537 Holds information on the longest string that must occur at a fixed
538 offset from the start of the pattern, and the longest string that must
539 occur at a floating offset from the start of the pattern. Used to do
540 Fast-Boyer-Moore searches on the string to find out if its worth using
541 the regex engine at all, and if so where in the string to search.
543 =head2 C<subbeg> C<sublen> C<saved_copy>
545 #define SAVEPVN(p,n) ((p) ? savepvn(p,n) : NULL)
546 if (RX_MATCH_COPIED(ret))
547 ret->subbeg = SAVEPVN(ret->subbeg, ret->sublen);
551 C<PL_sawampersand || rx->extflags & RXf_PMf_KEEPCOPY>
553 These are used during execution phase for managing search and replace
556 =head2 C<wrapped> C<wraplen>
558 Stores the string C<qr//> stringifies to, for example C<(?-xism:eek)>
559 in the case of C<qr/eek/>.
561 When using a custom engine that doesn't support the C<(?:)> construct for
562 inline modifiers it's best to have C<qr//> stringify to the supplied pattern,
563 note that this will create invalid patterns in cases such as:
565 my $x = qr/a|b/; # "a|b"
567 my $z = qr/$x$y/; # "a|bc"
569 There's no solution for such problems other than making the custom engine
570 understand some for of inline modifiers.
572 The C<Perl_reg_stringify> in F<regcomp.c> does the stringification work.
576 This stores the number of eval groups in the pattern. This is used for security
577 purposes when embedding compiled regexes into larger patterns with C<qr//>.
581 The number of times the structure is referenced. When this falls to 0 the
582 regexp is automatically freed by a call to pregfree. This should be set to 1 in
583 each engine's L</comp> routine.
587 Originally part of L<perlreguts>.
591 Originally written by Yves Orton, expanded by E<AElig>var ArnfjE<ouml>rE<eth>
596 Copyright 2006 Yves Orton and 2007 E<AElig>var ArnfjE<ouml>rE<eth> Bjarmason.
598 This program is free software; you can redistribute it and/or modify it under
599 the same terms as Perl itself.