ViewVC logotype

Contents of /code/trunk/doc/pcreapi.3

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1348 - (show annotations)
Fri Jul 5 10:38:37 2013 UTC (7 years, 11 months ago) by ph10
File size: 125448 byte(s)
Error occurred while calculating annotation data.
Implement PCRE_INFO_MATCH_EMPTY and fix 2 bugs concerned with scanning for 
empty string matching.
1 .TH PCREAPI 3 "05 July 2013" "PCRE 8.34"
3 PCRE - Perl-compatible regular expressions
4 .sp
5 .B #include <pcre.h>
6 .
7 .
9 .rs
10 .sp
11 .nf
12 .B pcre *pcre_compile(const char *\fIpattern\fP, int \fIoptions\fP,
13 .B " const char **\fIerrptr\fP, int *\fIerroffset\fP,"
14 .B " const unsigned char *\fItableptr\fP);"
15 .sp
16 .B pcre *pcre_compile2(const char *\fIpattern\fP, int \fIoptions\fP,
17 .B " int *\fIerrorcodeptr\fP,"
18 .B " const char **\fIerrptr\fP, int *\fIerroffset\fP,"
19 .B " const unsigned char *\fItableptr\fP);"
20 .sp
21 .B pcre_extra *pcre_study(const pcre *\fIcode\fP, int \fIoptions\fP,
22 .B " const char **\fIerrptr\fP);"
23 .sp
24 .B void pcre_free_study(pcre_extra *\fIextra\fP);
25 .sp
26 .B int pcre_exec(const pcre *\fIcode\fP, "const pcre_extra *\fIextra\fP,"
27 .B " const char *\fIsubject\fP, int \fIlength\fP, int \fIstartoffset\fP,"
28 .B " int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP);"
29 .sp
30 .B int pcre_dfa_exec(const pcre *\fIcode\fP, "const pcre_extra *\fIextra\fP,"
31 .B " const char *\fIsubject\fP, int \fIlength\fP, int \fIstartoffset\fP,"
32 .B " int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP,"
33 .B " int *\fIworkspace\fP, int \fIwscount\fP);"
34 .fi
35 .
36 .
38 .rs
39 .sp
40 .nf
41 .B int pcre_copy_named_substring(const pcre *\fIcode\fP,
42 .B " const char *\fIsubject\fP, int *\fIovector\fP,"
43 .B " int \fIstringcount\fP, const char *\fIstringname\fP,"
44 .B " char *\fIbuffer\fP, int \fIbuffersize\fP);"
45 .sp
46 .B int pcre_copy_substring(const char *\fIsubject\fP, int *\fIovector\fP,
47 .B " int \fIstringcount\fP, int \fIstringnumber\fP, char *\fIbuffer\fP,"
48 .B " int \fIbuffersize\fP);"
49 .sp
50 .B int pcre_get_named_substring(const pcre *\fIcode\fP,
51 .B " const char *\fIsubject\fP, int *\fIovector\fP,"
52 .B " int \fIstringcount\fP, const char *\fIstringname\fP,"
53 .B " const char **\fIstringptr\fP);"
54 .sp
55 .B int pcre_get_stringnumber(const pcre *\fIcode\fP,
56 .B " const char *\fIname\fP);"
57 .sp
58 .B int pcre_get_stringtable_entries(const pcre *\fIcode\fP,
59 .B " const char *\fIname\fP, char **\fIfirst\fP, char **\fIlast\fP);"
60 .sp
61 .B int pcre_get_substring(const char *\fIsubject\fP, int *\fIovector\fP,
62 .B " int \fIstringcount\fP, int \fIstringnumber\fP,"
63 .B " const char **\fIstringptr\fP);"
64 .sp
65 .B int pcre_get_substring_list(const char *\fIsubject\fP,
66 .B " int *\fIovector\fP, int \fIstringcount\fP, const char ***\fIlistptr\fP);"
67 .sp
68 .B void pcre_free_substring(const char *\fIstringptr\fP);
69 .sp
70 .B void pcre_free_substring_list(const char **\fIstringptr\fP);
71 .fi
72 .
73 .
75 .rs
76 .sp
77 .nf
78 .B int pcre_jit_exec(const pcre *\fIcode\fP, "const pcre_extra *\fIextra\fP,"
79 .B " const char *\fIsubject\fP, int \fIlength\fP, int \fIstartoffset\fP,"
80 .B " int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP,"
81 .B " pcre_jit_stack *\fIjstack\fP);"
82 .sp
83 .B pcre_jit_stack *pcre_jit_stack_alloc(int \fIstartsize\fP, int \fImaxsize\fP);
84 .sp
85 .B void pcre_jit_stack_free(pcre_jit_stack *\fIstack\fP);
86 .sp
87 .B void pcre_assign_jit_stack(pcre_extra *\fIextra\fP,
88 .B " pcre_jit_callback \fIcallback\fP, void *\fIdata\fP);"
89 .sp
90 .B const unsigned char *pcre_maketables(void);
91 .sp
92 .B int pcre_fullinfo(const pcre *\fIcode\fP, "const pcre_extra *\fIextra\fP,"
93 .B " int \fIwhat\fP, void *\fIwhere\fP);"
94 .sp
95 .B int pcre_refcount(pcre *\fIcode\fP, int \fIadjust\fP);
96 .sp
97 .B int pcre_config(int \fIwhat\fP, void *\fIwhere\fP);
98 .sp
99 .B const char *pcre_version(void);
100 .sp
101 .B int pcre_pattern_to_host_byte_order(pcre *\fIcode\fP,
102 .B " pcre_extra *\fIextra\fP, const unsigned char *\fItables\fP);"
103 .fi
104 .
105 .
107 .rs
108 .sp
109 .nf
110 .B void *(*pcre_malloc)(size_t);
111 .sp
112 .B void (*pcre_free)(void *);
113 .sp
114 .B void *(*pcre_stack_malloc)(size_t);
115 .sp
116 .B void (*pcre_stack_free)(void *);
117 .sp
118 .B int (*pcre_callout)(pcre_callout_block *);
119 .fi
120 .
121 .
123 .rs
124 .sp
125 As well as support for 8-bit character strings, PCRE also supports 16-bit
126 strings (from release 8.30) and 32-bit strings (from release 8.32), by means of
127 two additional libraries. They can be built as well as, or instead of, the
128 8-bit library. To avoid too much complication, this document describes the
129 8-bit versions of the functions, with only occasional references to the 16-bit
130 and 32-bit libraries.
131 .P
132 The 16-bit and 32-bit functions operate in the same way as their 8-bit
133 counterparts; they just use different data types for their arguments and
134 results, and their names start with \fBpcre16_\fP or \fBpcre32_\fP instead of
135 \fBpcre_\fP. For every option that has UTF8 in its name (for example,
136 PCRE_UTF8), there are corresponding 16-bit and 32-bit names with UTF8 replaced
137 by UTF16 or UTF32, respectively. This facility is in fact just cosmetic; the
138 16-bit and 32-bit option names define the same bit values.
139 .P
140 References to bytes and UTF-8 in this document should be read as references to
141 16-bit data units and UTF-16 when using the 16-bit library, or 32-bit data
142 units and UTF-32 when using the 32-bit library, unless specified otherwise.
143 More details of the specific differences for the 16-bit and 32-bit libraries
144 are given in the
145 .\" HREF
146 \fBpcre16\fP
147 .\"
148 and
149 .\" HREF
150 \fBpcre32\fP
151 .\"
152 pages.
153 .
154 .
156 .rs
157 .sp
158 PCRE has its own native API, which is described in this document. There are
159 also some wrapper functions (for the 8-bit library only) that correspond to the
160 POSIX regular expression API, but they do not give access to all the
161 functionality. They are described in the
162 .\" HREF
163 \fBpcreposix\fP
164 .\"
165 documentation. Both of these APIs define a set of C function calls. A C++
166 wrapper (again for the 8-bit library only) is also distributed with PCRE. It is
167 documented in the
168 .\" HREF
169 \fBpcrecpp\fP
170 .\"
171 page.
172 .P
173 The native API C function prototypes are defined in the header file
174 \fBpcre.h\fP, and on Unix-like systems the (8-bit) library itself is called
175 \fBlibpcre\fP. It can normally be accessed by adding \fB-lpcre\fP to the
176 command for linking an application that uses PCRE. The header file defines the
177 macros PCRE_MAJOR and PCRE_MINOR to contain the major and minor release numbers
178 for the library. Applications can use these to include support for different
179 releases of PCRE.
180 .P
181 In a Windows environment, if you want to statically link an application program
182 against a non-dll \fBpcre.a\fP file, you must define PCRE_STATIC before
183 including \fBpcre.h\fP or \fBpcrecpp.h\fP, because otherwise the
184 \fBpcre_malloc()\fP and \fBpcre_free()\fP exported functions will be declared
185 \fB__declspec(dllimport)\fP, with unwanted results.
186 .P
187 The functions \fBpcre_compile()\fP, \fBpcre_compile2()\fP, \fBpcre_study()\fP,
188 and \fBpcre_exec()\fP are used for compiling and matching regular expressions
189 in a Perl-compatible manner. A sample program that demonstrates the simplest
190 way of using them is provided in the file called \fIpcredemo.c\fP in the PCRE
191 source distribution. A listing of this program is given in the
192 .\" HREF
193 \fBpcredemo\fP
194 .\"
195 documentation, and the
196 .\" HREF
197 \fBpcresample\fP
198 .\"
199 documentation describes how to compile and run it.
200 .P
201 Just-in-time compiler support is an optional feature of PCRE that can be built
202 in appropriate hardware environments. It greatly speeds up the matching
203 performance of many patterns. Simple programs can easily request that it be
204 used if available, by setting an option that is ignored when it is not
205 relevant. More complicated programs might need to make use of the functions
206 \fBpcre_jit_stack_alloc()\fP, \fBpcre_jit_stack_free()\fP, and
207 \fBpcre_assign_jit_stack()\fP in order to control the JIT code's memory usage.
208 .P
209 From release 8.32 there is also a direct interface for JIT execution, which
210 gives improved performance. The JIT-specific functions are discussed in the
211 .\" HREF
212 \fBpcrejit\fP
213 .\"
214 documentation.
215 .P
216 A second matching function, \fBpcre_dfa_exec()\fP, which is not
217 Perl-compatible, is also provided. This uses a different algorithm for the
218 matching. The alternative algorithm finds all possible matches (at a given
219 point in the subject), and scans the subject just once (unless there are
220 lookbehind assertions). However, this algorithm does not return captured
221 substrings. A description of the two matching algorithms and their advantages
222 and disadvantages is given in the
223 .\" HREF
224 \fBpcrematching\fP
225 .\"
226 documentation.
227 .P
228 In addition to the main compiling and matching functions, there are convenience
229 functions for extracting captured substrings from a subject string that is
230 matched by \fBpcre_exec()\fP. They are:
231 .sp
232 \fBpcre_copy_substring()\fP
233 \fBpcre_copy_named_substring()\fP
234 \fBpcre_get_substring()\fP
235 \fBpcre_get_named_substring()\fP
236 \fBpcre_get_substring_list()\fP
237 \fBpcre_get_stringnumber()\fP
238 \fBpcre_get_stringtable_entries()\fP
239 .sp
240 \fBpcre_free_substring()\fP and \fBpcre_free_substring_list()\fP are also
241 provided, to free the memory used for extracted strings.
242 .P
243 The function \fBpcre_maketables()\fP is used to build a set of character tables
244 in the current locale for passing to \fBpcre_compile()\fP, \fBpcre_exec()\fP,
245 or \fBpcre_dfa_exec()\fP. This is an optional facility that is provided for
246 specialist use. Most commonly, no special tables are passed, in which case
247 internal tables that are generated when PCRE is built are used.
248 .P
249 The function \fBpcre_fullinfo()\fP is used to find out information about a
250 compiled pattern. The function \fBpcre_version()\fP returns a pointer to a
251 string containing the version of PCRE and its date of release.
252 .P
253 The function \fBpcre_refcount()\fP maintains a reference count in a data block
254 containing a compiled pattern. This is provided for the benefit of
255 object-oriented applications.
256 .P
257 The global variables \fBpcre_malloc\fP and \fBpcre_free\fP initially contain
258 the entry points of the standard \fBmalloc()\fP and \fBfree()\fP functions,
259 respectively. PCRE calls the memory management functions via these variables,
260 so a calling program can replace them if it wishes to intercept the calls. This
261 should be done before calling any PCRE functions.
262 .P
263 The global variables \fBpcre_stack_malloc\fP and \fBpcre_stack_free\fP are also
264 indirections to memory management functions. These special functions are used
265 only when PCRE is compiled to use the heap for remembering data, instead of
266 recursive function calls, when running the \fBpcre_exec()\fP function. See the
267 .\" HREF
268 \fBpcrebuild\fP
269 .\"
270 documentation for details of how to do this. It is a non-standard way of
271 building PCRE, for use in environments that have limited stacks. Because of the
272 greater use of memory management, it runs more slowly. Separate functions are
273 provided so that special-purpose external code can be used for this case. When
274 used, these functions are always called in a stack-like manner (last obtained,
275 first freed), and always for memory blocks of the same size. There is a
276 discussion about PCRE's stack usage in the
277 .\" HREF
278 \fBpcrestack\fP
279 .\"
280 documentation.
281 .P
282 The global variable \fBpcre_callout\fP initially contains NULL. It can be set
283 by the caller to a "callout" function, which PCRE will then call at specified
284 points during a matching operation. Details are given in the
285 .\" HREF
286 \fBpcrecallout\fP
287 .\"
288 documentation.
289 .
290 .
291 .\" HTML <a name="newlines"></a>
293 .rs
294 .sp
295 PCRE supports five different conventions for indicating line breaks in
296 strings: a single CR (carriage return) character, a single LF (linefeed)
297 character, the two-character sequence CRLF, any of the three preceding, or any
298 Unicode newline sequence. The Unicode newline sequences are the three just
299 mentioned, plus the single characters VT (vertical tab, U+000B), FF (form feed,
300 U+000C), NEL (next line, U+0085), LS (line separator, U+2028), and PS
301 (paragraph separator, U+2029).
302 .P
303 Each of the first three conventions is used by at least one operating system as
304 its standard newline sequence. When PCRE is built, a default can be specified.
305 The default default is LF, which is the Unix standard. When PCRE is run, the
306 default can be overridden, either when a pattern is compiled, or when it is
307 matched.
308 .P
309 At compile time, the newline convention can be specified by the \fIoptions\fP
310 argument of \fBpcre_compile()\fP, or it can be specified by special text at the
311 start of the pattern itself; this overrides any other settings. See the
312 .\" HREF
313 \fBpcrepattern\fP
314 .\"
315 page for details of the special character sequences.
316 .P
317 In the PCRE documentation the word "newline" is used to mean "the character or
318 pair of characters that indicate a line break". The choice of newline
319 convention affects the handling of the dot, circumflex, and dollar
320 metacharacters, the handling of #-comments in /x mode, and, when CRLF is a
321 recognized line ending sequence, the match position advancement for a
322 non-anchored pattern. There is more detail about this in the
323 .\" HTML <a href="#execoptions">
324 .\" </a>
325 section on \fBpcre_exec()\fP options
326 .\"
327 below.
328 .P
329 The choice of newline convention does not affect the interpretation of
330 the \en or \er escape sequences, nor does it affect what \eR matches, which is
331 controlled in a similar way, but by separate options.
332 .
333 .
335 .rs
336 .sp
337 The PCRE functions can be used in multi-threading applications, with the
338 proviso that the memory management functions pointed to by \fBpcre_malloc\fP,
339 \fBpcre_free\fP, \fBpcre_stack_malloc\fP, and \fBpcre_stack_free\fP, and the
340 callout function pointed to by \fBpcre_callout\fP, are shared by all threads.
341 .P
342 The compiled form of a regular expression is not altered during matching, so
343 the same compiled pattern can safely be used by several threads at once.
344 .P
345 If the just-in-time optimization feature is being used, it needs separate
346 memory stack areas for each thread. See the
347 .\" HREF
348 \fBpcrejit\fP
349 .\"
350 documentation for more details.
351 .
352 .
354 .rs
355 .sp
356 The compiled form of a regular expression can be saved and re-used at a later
357 time, possibly by a different program, and even on a host other than the one on
358 which it was compiled. Details are given in the
359 .\" HREF
360 \fBpcreprecompile\fP
361 .\"
362 documentation, which includes a description of the
363 \fBpcre_pattern_to_host_byte_order()\fP function. However, compiling a regular
364 expression with one version of PCRE for use with a different version is not
365 guaranteed to work and may cause crashes.
366 .
367 .
369 .rs
370 .sp
371 .B int pcre_config(int \fIwhat\fP, void *\fIwhere\fP);
372 .PP
373 The function \fBpcre_config()\fP makes it possible for a PCRE client to
374 discover which optional features have been compiled into the PCRE library. The
375 .\" HREF
376 \fBpcrebuild\fP
377 .\"
378 documentation has more details about these optional features.
379 .P
380 The first argument for \fBpcre_config()\fP is an integer, specifying which
381 information is required; the second argument is a pointer to a variable into
382 which the information is placed. The returned value is zero on success, or the
383 negative error code PCRE_ERROR_BADOPTION if the value in the first argument is
384 not recognized. The following information is available:
385 .sp
387 .sp
388 The output is an integer that is set to one if UTF-8 support is available;
389 otherwise it is set to zero. This value should normally be given to the 8-bit
390 version of this function, \fBpcre_config()\fP. If it is given to the 16-bit
391 or 32-bit version of this function, the result is PCRE_ERROR_BADOPTION.
392 .sp
394 .sp
395 The output is an integer that is set to one if UTF-16 support is available;
396 otherwise it is set to zero. This value should normally be given to the 16-bit
397 version of this function, \fBpcre16_config()\fP. If it is given to the 8-bit
398 or 32-bit version of this function, the result is PCRE_ERROR_BADOPTION.
399 .sp
401 .sp
402 The output is an integer that is set to one if UTF-32 support is available;
403 otherwise it is set to zero. This value should normally be given to the 32-bit
404 version of this function, \fBpcre32_config()\fP. If it is given to the 8-bit
405 or 16-bit version of this function, the result is PCRE_ERROR_BADOPTION.
406 .sp
408 .sp
409 The output is an integer that is set to one if support for Unicode character
410 properties is available; otherwise it is set to zero.
411 .sp
413 .sp
414 The output is an integer that is set to one if support for just-in-time
415 compiling is available; otherwise it is set to zero.
416 .sp
418 .sp
419 The output is a pointer to a zero-terminated "const char *" string. If JIT
420 support is available, the string contains the name of the architecture for
421 which the JIT compiler is configured, for example "x86 32bit (little endian +
422 unaligned)". If JIT support is not available, the result is NULL.
423 .sp
425 .sp
426 The output is an integer whose value specifies the default character sequence
427 that is recognized as meaning "newline". The values that are supported in
428 ASCII/Unicode environments are: 10 for LF, 13 for CR, 3338 for CRLF, -2 for
429 ANYCRLF, and -1 for ANY. In EBCDIC environments, CR, ANYCRLF, and ANY yield the
430 same values. However, the value for LF is normally 21, though some EBCDIC
431 environments use 37. The corresponding values for CRLF are 3349 and 3365. The
432 default should normally correspond to the standard sequence for your operating
433 system.
434 .sp
436 .sp
437 The output is an integer whose value indicates what character sequences the \eR
438 escape sequence matches by default. A value of 0 means that \eR matches any
439 Unicode line ending sequence; a value of 1 means that \eR matches only CR, LF,
440 or CRLF. The default can be overridden when a pattern is compiled or matched.
441 .sp
443 .sp
444 The output is an integer that contains the number of bytes used for internal
445 linkage in compiled regular expressions. For the 8-bit library, the value can
446 be 2, 3, or 4. For the 16-bit library, the value is either 2 or 4 and is still
447 a number of bytes. For the 32-bit library, the value is either 2 or 4 and is
448 still a number of bytes. The default value of 2 is sufficient for all but the
449 most massive patterns, since it allows the compiled pattern to be up to 64K in
450 size. Larger values allow larger regular expressions to be compiled, at the
451 expense of slower matching.
452 .sp
454 .sp
455 The output is an integer that contains the threshold above which the POSIX
456 interface uses \fBmalloc()\fP for output vectors. Further details are given in
457 the
458 .\" HREF
459 \fBpcreposix\fP
460 .\"
461 documentation.
462 .sp
464 .sp
465 The output is a long integer that gives the default limit for the number of
466 internal matching function calls in a \fBpcre_exec()\fP execution. Further
467 details are given with \fBpcre_exec()\fP below.
468 .sp
470 .sp
471 The output is a long integer that gives the default limit for the depth of
472 recursion when calling the internal matching function in a \fBpcre_exec()\fP
473 execution. Further details are given with \fBpcre_exec()\fP below.
474 .sp
476 .sp
477 The output is an integer that is set to one if internal recursion when running
478 \fBpcre_exec()\fP is implemented by recursive function calls that use the stack
479 to remember their state. This is the usual way that PCRE is compiled. The
480 output is zero if PCRE was compiled to use blocks of data on the heap instead
481 of recursive function calls. In this case, \fBpcre_stack_malloc\fP and
482 \fBpcre_stack_free\fP are called to manage memory blocks on the heap, thus
483 avoiding the use of the stack.
484 .
485 .
487 .rs
488 .sp
489 .nf
490 .B pcre *pcre_compile(const char *\fIpattern\fP, int \fIoptions\fP,
491 .B " const char **\fIerrptr\fP, int *\fIerroffset\fP,"
492 .B " const unsigned char *\fItableptr\fP);"
493 .sp
494 .B pcre *pcre_compile2(const char *\fIpattern\fP, int \fIoptions\fP,
495 .B " int *\fIerrorcodeptr\fP,"
496 .B " const char **\fIerrptr\fP, int *\fIerroffset\fP,"
497 .B " const unsigned char *\fItableptr\fP);"
498 .fi
499 .P
500 Either of the functions \fBpcre_compile()\fP or \fBpcre_compile2()\fP can be
501 called to compile a pattern into an internal form. The only difference between
502 the two interfaces is that \fBpcre_compile2()\fP has an additional argument,
503 \fIerrorcodeptr\fP, via which a numerical error code can be returned. To avoid
504 too much repetition, we refer just to \fBpcre_compile()\fP below, but the
505 information applies equally to \fBpcre_compile2()\fP.
506 .P
507 The pattern is a C string terminated by a binary zero, and is passed in the
508 \fIpattern\fP argument. A pointer to a single block of memory that is obtained
509 via \fBpcre_malloc\fP is returned. This contains the compiled code and related
510 data. The \fBpcre\fP type is defined for the returned block; this is a typedef
511 for a structure whose contents are not externally defined. It is up to the
512 caller to free the memory (via \fBpcre_free\fP) when it is no longer required.
513 .P
514 Although the compiled code of a PCRE regex is relocatable, that is, it does not
515 depend on memory location, the complete \fBpcre\fP data block is not
516 fully relocatable, because it may contain a copy of the \fItableptr\fP
517 argument, which is an address (see below).
518 .P
519 The \fIoptions\fP argument contains various bit settings that affect the
520 compilation. It should be zero if no options are required. The available
521 options are described below. Some of them (in particular, those that are
522 compatible with Perl, but some others as well) can also be set and unset from
523 within the pattern (see the detailed description in the
524 .\" HREF
525 \fBpcrepattern\fP
526 .\"
527 documentation). For those options that can be different in different parts of
528 the pattern, the contents of the \fIoptions\fP argument specifies their
529 settings at the start of compilation and execution. The PCRE_ANCHORED,
531 PCRE_NO_START_OPTIMIZE options can be set at the time of matching as well as at
532 compile time.
533 .P
534 If \fIerrptr\fP is NULL, \fBpcre_compile()\fP returns NULL immediately.
535 Otherwise, if compilation of a pattern fails, \fBpcre_compile()\fP returns
536 NULL, and sets the variable pointed to by \fIerrptr\fP to point to a textual
537 error message. This is a static string that is part of the library. You must
538 not try to free it. Normally, the offset from the start of the pattern to the
539 data unit that was being processed when the error was discovered is placed in
540 the variable pointed to by \fIerroffset\fP, which must not be NULL (if it is,
541 an immediate error is given). However, for an invalid UTF-8 or UTF-16 string,
542 the offset is that of the first data unit of the failing character.
543 .P
544 Some errors are not detected until the whole pattern has been scanned; in these
545 cases, the offset passed back is the length of the pattern. Note that the
546 offset is in data units, not characters, even in a UTF mode. It may sometimes
547 point into the middle of a UTF-8 or UTF-16 character.
548 .P
549 If \fBpcre_compile2()\fP is used instead of \fBpcre_compile()\fP, and the
550 \fIerrorcodeptr\fP argument is not NULL, a non-zero error code number is
551 returned via this argument in the event of an error. This is in addition to the
552 textual error message. Error codes and messages are listed below.
553 .P
554 If the final argument, \fItableptr\fP, is NULL, PCRE uses a default set of
555 character tables that are built when PCRE is compiled, using the default C
556 locale. Otherwise, \fItableptr\fP must be an address that is the result of a
557 call to \fBpcre_maketables()\fP. This value is stored with the compiled
558 pattern, and used again by \fBpcre_exec()\fP, unless another table pointer is
559 passed to it. For more discussion, see the section on locale support below.
560 .P
561 This code fragment shows a typical straightforward call to \fBpcre_compile()\fP:
562 .sp
563 pcre *re;
564 const char *error;
565 int erroffset;
566 re = pcre_compile(
567 "^A.*Z", /* the pattern */
568 0, /* default options */
569 &error, /* for error message */
570 &erroffset, /* for error offset */
571 NULL); /* use default character tables */
572 .sp
573 The following names for option bits are defined in the \fBpcre.h\fP header
574 file:
575 .sp
577 .sp
578 If this bit is set, the pattern is forced to be "anchored", that is, it is
579 constrained to match only at the first matching point in the string that is
580 being searched (the "subject string"). This effect can also be achieved by
581 appropriate constructs in the pattern itself, which is the only way to do it in
582 Perl.
583 .sp
585 .sp
586 If this bit is set, \fBpcre_compile()\fP automatically inserts callout items,
587 all with number 255, before each pattern item. For discussion of the callout
588 facility, see the
589 .\" HREF
590 \fBpcrecallout\fP
591 .\"
592 documentation.
593 .sp
596 .sp
597 These options (which are mutually exclusive) control what the \eR escape
598 sequence matches. The choice is either to match only CR, LF, or CRLF, or to
599 match any Unicode newline sequence. The default is specified when PCRE is
600 built. It can be overridden from within the pattern, or by setting an option
601 when a compiled pattern is matched.
602 .sp
604 .sp
605 If this bit is set, letters in the pattern match both upper and lower case
606 letters. It is equivalent to Perl's /i option, and it can be changed within a
607 pattern by a (?i) option setting. In UTF-8 mode, PCRE always understands the
608 concept of case for characters whose values are less than 128, so caseless
609 matching is always possible. For characters with higher values, the concept of
610 case is supported if PCRE is compiled with Unicode property support, but not
611 otherwise. If you want to use caseless matching for characters 128 and above,
612 you must ensure that PCRE is compiled with Unicode property support as well as
613 with UTF-8 support.
614 .sp
616 .sp
617 If this bit is set, a dollar metacharacter in the pattern matches only at the
618 end of the subject string. Without this option, a dollar also matches
619 immediately before a newline at the end of the string (but not before any other
620 newlines). The PCRE_DOLLAR_ENDONLY option is ignored if PCRE_MULTILINE is set.
621 There is no equivalent to this option in Perl, and no way to set it within a
622 pattern.
623 .sp
625 .sp
626 If this bit is set, a dot metacharacter in the pattern matches a character of
627 any value, including one that indicates a newline. However, it only ever
628 matches one character, even if newlines are coded as CRLF. Without this option,
629 a dot does not match when the current position is at a newline. This option is
630 equivalent to Perl's /s option, and it can be changed within a pattern by a
631 (?s) option setting. A negative class such as [^a] always matches newline
632 characters, independent of the setting of this option.
633 .sp
635 .sp
636 If this bit is set, names used to identify capturing subpatterns need not be
637 unique. This can be helpful for certain types of pattern when it is known that
638 only one instance of the named subpattern can ever be matched. There are more
639 details of named subpatterns below; see also the
640 .\" HREF
641 \fBpcrepattern\fP
642 .\"
643 documentation.
644 .sp
646 .sp
647 If this bit is set, white space data characters in the pattern are totally
648 ignored except when escaped or inside a character class. White space does not
649 include the VT character (code 11). In addition, characters between an
650 unescaped # outside a character class and the next newline, inclusive, are also
651 ignored. This is equivalent to Perl's /x option, and it can be changed within a
652 pattern by a (?x) option setting.
653 .P
654 Which characters are interpreted as newlines is controlled by the options
655 passed to \fBpcre_compile()\fP or by a special sequence at the start of the
656 pattern, as described in the section entitled
657 .\" HTML <a href="pcrepattern.html#newlines">
658 .\" </a>
659 "Newline conventions"
660 .\"
661 in the \fBpcrepattern\fP documentation. Note that the end of this type of
662 comment is a literal newline sequence in the pattern; escape sequences that
663 happen to represent a newline do not count.
664 .P
665 This option makes it possible to include comments inside complicated patterns.
666 Note, however, that this applies only to data characters. White space characters
667 may never appear within special character sequences in a pattern, for example
668 within the sequence (?( that introduces a conditional subpattern.
669 .sp
671 .sp
672 This option was invented in order to turn on additional functionality of PCRE
673 that is incompatible with Perl, but it is currently of very little use. When
674 set, any backslash in a pattern that is followed by a letter that has no
675 special meaning causes an error, thus reserving these combinations for future
676 expansion. By default, as in Perl, a backslash followed by a letter with no
677 special meaning is treated as a literal. (Perl can, however, be persuaded to
678 give an error for this, by running it with the -w option.) There are at present
679 no other features controlled by this option. It can also be set by a (?X)
680 option setting within a pattern.
681 .sp
683 .sp
684 If this option is set, an unanchored pattern is required to match before or at
685 the first newline in the subject string, though the matched text may continue
686 over the newline.
687 .sp
689 .sp
690 If this option is set, PCRE's behaviour is changed in some ways so that it is
691 compatible with JavaScript rather than Perl. The changes are as follows:
692 .P
693 (1) A lone closing square bracket in a pattern causes a compile-time error,
694 because this is illegal in JavaScript (by default it is treated as a data
695 character). Thus, the pattern AB]CD becomes illegal when this option is set.
696 .P
697 (2) At run time, a back reference to an unset subpattern group matches an empty
698 string (by default this causes the current matching alternative to fail). A
699 pattern such as (\e1)(a) succeeds when this option is set (assuming it can find
700 an "a" in the subject), whereas it fails by default, for Perl compatibility.
701 .P
702 (3) \eU matches an upper case "U" character; by default \eU causes a compile
703 time error (Perl uses \eU to upper case subsequent characters).
704 .P
705 (4) \eu matches a lower case "u" character unless it is followed by four
706 hexadecimal digits, in which case the hexadecimal number defines the code point
707 to match. By default, \eu causes a compile time error (Perl uses it to upper
708 case the following character).
709 .P
710 (5) \ex matches a lower case "x" character unless it is followed by two
711 hexadecimal digits, in which case the hexadecimal number defines the code point
712 to match. By default, as in Perl, a hexadecimal number is always expected after
713 \ex, but it may have zero, one, or two digits (so, for example, \exz matches a
714 binary zero character followed by z).
715 .sp
717 .sp
718 By default, for the purposes of matching "start of line" and "end of line",
719 PCRE treats the subject string as consisting of a single line of characters,
720 even if it actually contains newlines. The "start of line" metacharacter (^)
721 matches only at the start of the string, and the "end of line" metacharacter
722 ($) matches only at the end of the string, or before a terminating newline
723 (except when PCRE_DOLLAR_ENDONLY is set). Note, however, that unless
724 PCRE_DOTALL is set, the "any character" metacharacter (.) does not match at a
725 newline. This behaviour (for ^, $, and dot) is the same as Perl.
726 .P
727 When PCRE_MULTILINE it is set, the "start of line" and "end of line" constructs
728 match immediately following or immediately before internal newlines in the
729 subject string, respectively, as well as at the very start and end. This is
730 equivalent to Perl's /m option, and it can be changed within a pattern by a
731 (?m) option setting. If there are no newlines in a subject string, or no
732 occurrences of ^ or $ in a pattern, setting PCRE_MULTILINE has no effect.
733 .sp
735 .sp
736 This option locks out interpretation of the pattern as UTF-8 (or UTF-16 or
737 UTF-32 in the 16-bit and 32-bit libraries). In particular, it prevents the
738 creator of the pattern from switching to UTF interpretation by starting the
739 pattern with (*UTF). This may be useful in applications that process patterns
740 from external sources. The combination of PCRE_UTF8 and PCRE_NEVER_UTF also
741 causes an error.
742 .sp
748 .sp
749 These options override the default newline definition that was chosen when PCRE
750 was built. Setting the first or the second specifies that a newline is
751 indicated by a single character (CR or LF, respectively). Setting
752 PCRE_NEWLINE_CRLF specifies that a newline is indicated by the two-character
753 CRLF sequence. Setting PCRE_NEWLINE_ANYCRLF specifies that any of the three
754 preceding sequences should be recognized. Setting PCRE_NEWLINE_ANY specifies
755 that any Unicode newline sequence should be recognized.
756 .P
757 In an ASCII/Unicode environment, the Unicode newline sequences are the three
758 just mentioned, plus the single characters VT (vertical tab, U+000B), FF (form
759 feed, U+000C), NEL (next line, U+0085), LS (line separator, U+2028), and PS
760 (paragraph separator, U+2029). For the 8-bit library, the last two are
761 recognized only in UTF-8 mode.
762 .P
763 When PCRE is compiled to run in an EBCDIC (mainframe) environment, the code for
764 CR is 0x0d, the same as ASCII. However, the character code for LF is normally
765 0x15, though in some EBCDIC environments 0x25 is used. Whichever of these is
766 not LF is made to correspond to Unicode's NEL character. EBCDIC codes are all
767 less than 256. For more details, see the
768 .\" HREF
769 \fBpcrebuild\fP
770 .\"
771 documentation.
772 .P
773 The newline setting in the options word uses three bits that are treated
774 as a number, giving eight possibilities. Currently only six are used (default
775 plus the five values above). This means that if you set more than one newline
776 option, the combination may or may not be sensible. For example,
778 other combinations may yield unused numbers and cause an error.
779 .P
780 The only time that a line break in a pattern is specially recognized when
781 compiling is when PCRE_EXTENDED is set. CR and LF are white space characters,
782 and so are ignored in this mode. Also, an unescaped # outside a character class
783 indicates a comment that lasts until after the next line break sequence. In
784 other circumstances, line break sequences in patterns are treated as literal
785 data.
786 .P
787 The newline option that is set at compile time becomes the default that is used
788 for \fBpcre_exec()\fP and \fBpcre_dfa_exec()\fP, but it can be overridden.
789 .sp
791 .sp
792 If this option is set, it disables the use of numbered capturing parentheses in
793 the pattern. Any opening parenthesis that is not followed by ? behaves as if it
794 were followed by ?: but named parentheses can still be used for capturing (and
795 they acquire numbers in the usual way). There is no equivalent of this option
796 in Perl.
797 .sp
799 .sp
800 This is an option that acts at matching time; that is, it is really an option
801 for \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP. If it is set at compile time,
802 it is remembered with the compiled pattern and assumed at matching time. This
803 is necessary if you want to use JIT execution, because the JIT compiler needs
804 to know whether or not this option is set. For details see the discussion of
806 .\" HTML <a href="#execoptions">
807 .\" </a>
808 below.
809 .\"
810 .sp
812 .sp
813 This option changes the way PCRE processes \eB, \eb, \eD, \ed, \eS, \es, \eW,
814 \ew, and some of the POSIX character classes. By default, only ASCII characters
815 are recognized, but if PCRE_UCP is set, Unicode properties are used instead to
816 classify characters. More details are given in the section on
817 .\" HTML <a href="pcre.html#genericchartypes">
818 .\" </a>
819 generic character types
820 .\"
821 in the
822 .\" HREF
823 \fBpcrepattern\fP
824 .\"
825 page. If you set PCRE_UCP, matching one of the items it affects takes much
826 longer. The option is available only if PCRE has been compiled with Unicode
827 property support.
828 .sp
830 .sp
831 This option inverts the "greediness" of the quantifiers so that they are not
832 greedy by default, but become greedy if followed by "?". It is not compatible
833 with Perl. It can also be set by a (?U) option setting within the pattern.
834 .sp
836 .sp
837 This option causes PCRE to regard both the pattern and the subject as strings
838 of UTF-8 characters instead of single-byte strings. However, it is available
839 only when PCRE is built to include UTF support. If not, the use of this option
840 provokes an error. Details of how this option changes the behaviour of PCRE are
841 given in the
842 .\" HREF
843 \fBpcreunicode\fP
844 .\"
845 page.
846 .sp
848 .sp
849 When PCRE_UTF8 is set, the validity of the pattern as a UTF-8 string is
850 automatically checked. There is a discussion about the
851 .\" HTML <a href="pcreunicode.html#utf8strings">
852 .\" </a>
853 validity of UTF-8 strings
854 .\"
855 in the
856 .\" HREF
857 \fBpcreunicode\fP
858 .\"
859 page. If an invalid UTF-8 sequence is found, \fBpcre_compile()\fP returns an
860 error. If you already know that your pattern is valid, and you want to skip
861 this check for performance reasons, you can set the PCRE_NO_UTF8_CHECK option.
862 When it is set, the effect of passing an invalid UTF-8 string as a pattern is
863 undefined. It may cause your program to crash. Note that this option can also
864 be passed to \fBpcre_exec()\fP and \fBpcre_dfa_exec()\fP, to suppress the
865 validity checking of subject strings only. If the same string is being matched
866 many times, the option can be safely set for the second and subsequent
867 matchings to improve performance.
868 .
869 .
871 .rs
872 .sp
873 The following table lists the error codes than may be returned by
874 \fBpcre_compile2()\fP, along with the error messages that may be returned by
875 both compiling functions. Note that error messages are always 8-bit ASCII
876 strings, even in 16-bit or 32-bit mode. As PCRE has developed, some error codes
877 have fallen out of use. To avoid confusion, they have not been re-used.
878 .sp
879 0 no error
880 1 \e at end of pattern
881 2 \ec at end of pattern
882 3 unrecognized character follows \e
883 4 numbers out of order in {} quantifier
884 5 number too big in {} quantifier
885 6 missing terminating ] for character class
886 7 invalid escape sequence in character class
887 8 range out of order in character class
888 9 nothing to repeat
889 10 [this code is not in use]
890 11 internal error: unexpected repeat
891 12 unrecognized character after (? or (?-
892 13 POSIX named classes are supported only within a class
893 14 missing )
894 15 reference to non-existent subpattern
895 16 erroffset passed as NULL
896 17 unknown option bit(s) set
897 18 missing ) after comment
898 19 [this code is not in use]
899 20 regular expression is too large
900 21 failed to get memory
901 22 unmatched parentheses
902 23 internal error: code overflow
903 24 unrecognized character after (?<
904 25 lookbehind assertion is not fixed length
905 26 malformed number or name after (?(
906 27 conditional group contains more than two branches
907 28 assertion expected after (?(
908 29 (?R or (?[+-]digits must be followed by )
909 30 unknown POSIX class name
910 31 POSIX collating elements are not supported
911 32 this version of PCRE is compiled without UTF support
912 33 [this code is not in use]
913 34 character value in \ex{...} sequence is too large
914 35 invalid condition (?(0)
915 36 \eC not allowed in lookbehind assertion
916 37 PCRE does not support \eL, \el, \eN{name}, \eU, or \eu
917 38 number after (?C is > 255
918 39 closing ) for (?C expected
919 40 recursive call could loop indefinitely
920 41 unrecognized character after (?P
921 42 syntax error in subpattern name (missing terminator)
922 43 two named subpatterns have the same name
923 44 invalid UTF-8 string (specifically UTF-8)
924 45 support for \eP, \ep, and \eX has not been compiled
925 46 malformed \eP or \ep sequence
926 47 unknown property name after \eP or \ep
927 48 subpattern name is too long (maximum 32 characters)
928 49 too many named subpatterns (maximum 10000)
929 50 [this code is not in use]
930 51 octal value is greater than \e377 in 8-bit non-UTF-8 mode
931 52 internal error: overran compiling workspace
932 53 internal error: previously-checked referenced subpattern
933 not found
934 54 DEFINE group contains more than one branch
935 55 repeating a DEFINE group is not allowed
936 56 inconsistent NEWLINE options
937 57 \eg is not followed by a braced, angle-bracketed, or quoted
938 name/number or by a plain number
939 58 a numbered reference must not be zero
940 59 an argument is not allowed for (*ACCEPT), (*FAIL), or (*COMMIT)
941 60 (*VERB) not recognized or malformed
942 61 number is too big
943 62 subpattern name expected
944 63 digit expected after (?+
945 64 ] is an invalid data character in JavaScript compatibility mode
946 65 different names for subpatterns of the same number are
947 not allowed
948 66 (*MARK) must have an argument
949 67 this version of PCRE is not compiled with Unicode property
950 support
951 68 \ec must be followed by an ASCII character
952 69 \ek is not followed by a braced, angle-bracketed, or quoted name
953 70 internal error: unknown opcode in find_fixedlength()
954 71 \eN is not supported in a class
955 72 too many forward references
956 73 disallowed Unicode code point (>= 0xd800 && <= 0xdfff)
957 74 invalid UTF-16 string (specifically UTF-16)
958 75 name is too long in (*MARK), (*PRUNE), (*SKIP), or (*THEN)
959 76 character value in \eu.... sequence is too large
960 77 invalid UTF-32 string (specifically UTF-32)
961 .sp
962 The numbers 32 and 10000 in errors 48 and 49 are defaults; different values may
963 be used if the limits were changed when PCRE was built.
964 .
965 .
966 .\" HTML <a name="studyingapattern"></a>
968 .rs
969 .sp
970 .nf
971 .B pcre_extra *pcre_study(const pcre *\fIcode\fP, int \fIoptions\fP,
972 .B " const char **\fIerrptr\fP);"
973 .fi
974 .PP
975 If a compiled pattern is going to be used several times, it is worth spending
976 more time analyzing it in order to speed up the time taken for matching. The
977 function \fBpcre_study()\fP takes a pointer to a compiled pattern as its first
978 argument. If studying the pattern produces additional information that will
979 help speed up matching, \fBpcre_study()\fP returns a pointer to a
980 \fBpcre_extra\fP block, in which the \fIstudy_data\fP field points to the
981 results of the study.
982 .P
983 The returned value from \fBpcre_study()\fP can be passed directly to
984 \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP. However, a \fBpcre_extra\fP block
985 also contains other fields that can be set by the caller before the block is
986 passed; these are described
987 .\" HTML <a href="#extradata">
988 .\" </a>
989 below
990 .\"
991 in the section on matching a pattern.
992 .P
993 If studying the pattern does not produce any useful information,
994 \fBpcre_study()\fP returns NULL by default. In that circumstance, if the
995 calling program wants to pass any of the other fields to \fBpcre_exec()\fP or
996 \fBpcre_dfa_exec()\fP, it must set up its own \fBpcre_extra\fP block. However,
997 if \fBpcre_study()\fP is called with the PCRE_STUDY_EXTRA_NEEDED option, it
998 returns a \fBpcre_extra\fP block even if studying did not find any additional
999 information. It may still return NULL, however, if an error occurs in
1000 \fBpcre_study()\fP.
1001 .P
1002 The second argument of \fBpcre_study()\fP contains option bits. There are three
1003 further options in addition to PCRE_STUDY_EXTRA_NEEDED:
1004 .sp
1008 .sp
1009 If any of these are set, and the just-in-time compiler is available, the
1010 pattern is further compiled into machine code that executes much faster than
1011 the \fBpcre_exec()\fP interpretive matching function. If the just-in-time
1012 compiler is not available, these options are ignored. All undefined bits in the
1013 \fIoptions\fP argument must be zero.
1014 .P
1015 JIT compilation is a heavyweight optimization. It can take some time for
1016 patterns to be analyzed, and for one-off matches and simple patterns the
1017 benefit of faster execution might be offset by a much slower study time.
1018 Not all patterns can be optimized by the JIT compiler. For those that cannot be
1019 handled, matching automatically falls back to the \fBpcre_exec()\fP
1020 interpreter. For more details, see the
1021 .\" HREF
1022 \fBpcrejit\fP
1023 .\"
1024 documentation.
1025 .P
1026 The third argument for \fBpcre_study()\fP is a pointer for an error message. If
1027 studying succeeds (even if no data is returned), the variable it points to is
1028 set to NULL. Otherwise it is set to point to a textual error message. This is a
1029 static string that is part of the library. You must not try to free it. You
1030 should test the error pointer for NULL after calling \fBpcre_study()\fP, to be
1031 sure that it has run successfully.
1032 .P
1033 When you are finished with a pattern, you can free the memory used for the
1034 study data by calling \fBpcre_free_study()\fP. This function was added to the
1035 API for release 8.20. For earlier versions, the memory could be freed with
1036 \fBpcre_free()\fP, just like the pattern itself. This will still work in cases
1037 where JIT optimization is not used, but it is advisable to change to the new
1038 function when convenient.
1039 .P
1040 This is a typical way in which \fBpcre_study\fP() is used (except that in a
1041 real application there should be tests for errors):
1042 .sp
1043 int rc;
1044 pcre *re;
1045 pcre_extra *sd;
1046 re = pcre_compile("pattern", 0, &error, &erroroffset, NULL);
1047 sd = pcre_study(
1048 re, /* result of pcre_compile() */
1049 0, /* no options */
1050 &error); /* set to NULL or points to a message */
1051 rc = pcre_exec( /* see below for details of pcre_exec() options */
1052 re, sd, "subject", 7, 0, 0, ovector, 30);
1053 ...
1054 pcre_free_study(sd);
1055 pcre_free(re);
1056 .sp
1057 Studying a pattern does two things: first, a lower bound for the length of
1058 subject string that is needed to match the pattern is computed. This does not
1059 mean that there are any strings of that length that match, but it does
1060 guarantee that no shorter strings match. The value is used to avoid wasting
1061 time by trying to match strings that are shorter than the lower bound. You can
1062 find out the value in a calling program via the \fBpcre_fullinfo()\fP function.
1063 .P
1064 Studying a pattern is also useful for non-anchored patterns that do not have a
1065 single fixed starting character. A bitmap of possible starting bytes is
1066 created. This speeds up finding a position in the subject at which to start
1067 matching. (In 16-bit mode, the bitmap is used for 16-bit values less than 256.
1068 In 32-bit mode, the bitmap is used for 32-bit values less than 256.)
1069 .P
1070 These two optimizations apply to both \fBpcre_exec()\fP and
1071 \fBpcre_dfa_exec()\fP, and the information is also used by the JIT compiler.
1072 The optimizations can be disabled by setting the PCRE_NO_START_OPTIMIZE option.
1073 You might want to do this if your pattern contains callouts or (*MARK) and you
1074 want to make use of these facilities in cases where matching fails.
1075 .P
1076 PCRE_NO_START_OPTIMIZE can be specified at either compile time or execution
1077 time. However, if PCRE_NO_START_OPTIMIZE is passed to \fBpcre_exec()\fP, (that
1078 is, after any JIT compilation has happened) JIT execution is disabled. For JIT
1079 execution to work with PCRE_NO_START_OPTIMIZE, the option must be set at
1080 compile time.
1081 .P
1082 There is a longer discussion of PCRE_NO_START_OPTIMIZE
1083 .\" HTML <a href="#execoptions">
1084 .\" </a>
1085 below.
1086 .\"
1087 .
1088 .
1089 .\" HTML <a name="localesupport"></a>
1091 .rs
1092 .sp
1093 PCRE handles caseless matching, and determines whether characters are letters,
1094 digits, or whatever, by reference to a set of tables, indexed by character
1095 value. When running in UTF-8 mode, this applies only to characters
1096 with codes less than 128. By default, higher-valued codes never match escapes
1097 such as \ew or \ed, but they can be tested with \ep if PCRE is built with
1098 Unicode character property support. Alternatively, the PCRE_UCP option can be
1099 set at compile time; this causes \ew and friends to use Unicode property
1100 support instead of built-in tables. The use of locales with Unicode is
1101 discouraged. If you are handling characters with codes greater than 128, you
1102 should either use UTF-8 and Unicode, or use locales, but not try to mix the
1103 two.
1104 .P
1105 PCRE contains an internal set of tables that are used when the final argument
1106 of \fBpcre_compile()\fP is NULL. These are sufficient for many applications.
1107 Normally, the internal tables recognize only ASCII characters. However, when
1108 PCRE is built, it is possible to cause the internal tables to be rebuilt in the
1109 default "C" locale of the local system, which may cause them to be different.
1110 .P
1111 The internal tables can always be overridden by tables supplied by the
1112 application that calls PCRE. These may be created in a different locale from
1113 the default. As more and more applications change to using Unicode, the need
1114 for this locale support is expected to die away.
1115 .P
1116 External tables are built by calling the \fBpcre_maketables()\fP function,
1117 which has no arguments, in the relevant locale. The result can then be passed
1118 to \fBpcre_compile()\fP or \fBpcre_exec()\fP as often as necessary. For
1119 example, to build and use tables that are appropriate for the French locale
1120 (where accented characters with values greater than 128 are treated as letters),
1121 the following code could be used:
1122 .sp
1123 setlocale(LC_CTYPE, "fr_FR");
1124 tables = pcre_maketables();
1125 re = pcre_compile(..., tables);
1126 .sp
1127 The locale name "fr_FR" is used on Linux and other Unix-like systems; if you
1128 are using Windows, the name for the French locale is "french".
1129 .P
1130 When \fBpcre_maketables()\fP runs, the tables are built in memory that is
1131 obtained via \fBpcre_malloc\fP. It is the caller's responsibility to ensure
1132 that the memory containing the tables remains available for as long as it is
1133 needed.
1134 .P
1135 The pointer that is passed to \fBpcre_compile()\fP is saved with the compiled
1136 pattern, and the same tables are used via this pointer by \fBpcre_study()\fP
1137 and normally also by \fBpcre_exec()\fP. Thus, by default, for any single
1138 pattern, compilation, studying and matching all happen in the same locale, but
1139 different patterns can be compiled in different locales.
1140 .P
1141 It is possible to pass a table pointer or NULL (indicating the use of the
1142 internal tables) to \fBpcre_exec()\fP. Although not intended for this purpose,
1143 this facility could be used to match a pattern in a different locale from the
1144 one in which it was compiled. Passing table pointers at run time is discussed
1145 below in the section on matching a pattern.
1146 .
1147 .
1148 .\" HTML <a name="infoaboutpattern"></a>
1150 .rs
1151 .sp
1152 .nf
1153 .B int pcre_fullinfo(const pcre *\fIcode\fP, "const pcre_extra *\fIextra\fP,"
1154 .B " int \fIwhat\fP, void *\fIwhere\fP);"
1155 .fi
1156 .PP
1157 The \fBpcre_fullinfo()\fP function returns information about a compiled
1158 pattern. It replaces the \fBpcre_info()\fP function, which was removed from the
1159 library at version 8.30, after more than 10 years of obsolescence.
1160 .P
1161 The first argument for \fBpcre_fullinfo()\fP is a pointer to the compiled
1162 pattern. The second argument is the result of \fBpcre_study()\fP, or NULL if
1163 the pattern was not studied. The third argument specifies which piece of
1164 information is required, and the fourth argument is a pointer to a variable
1165 to receive the data. The yield of the function is zero for success, or one of
1166 the following negative numbers:
1167 .sp
1168 PCRE_ERROR_NULL the argument \fIcode\fP was NULL
1169 the argument \fIwhere\fP was NULL
1170 PCRE_ERROR_BADMAGIC the "magic number" was not found
1171 PCRE_ERROR_BADENDIANNESS the pattern was compiled with different
1172 endianness
1173 PCRE_ERROR_BADOPTION the value of \fIwhat\fP was invalid
1174 PCRE_ERROR_UNSET the requested field is not set
1175 .sp
1176 The "magic number" is placed at the start of each compiled pattern as an simple
1177 check against passing an arbitrary memory pointer. The endianness error can
1178 occur if a compiled pattern is saved and reloaded on a different host. Here is
1179 a typical call of \fBpcre_fullinfo()\fP, to obtain the length of the compiled
1180 pattern:
1181 .sp
1182 int rc;
1183 size_t length;
1184 rc = pcre_fullinfo(
1185 re, /* result of pcre_compile() */
1186 sd, /* result of pcre_study(), or NULL */
1187 PCRE_INFO_SIZE, /* what is required */
1188 &length); /* where to put the data */
1189 .sp
1190 The possible values for the third argument are defined in \fBpcre.h\fP, and are
1191 as follows:
1192 .sp
1194 .sp
1195 Return the number of the highest back reference in the pattern. The fourth
1196 argument should point to an \fBint\fP variable. Zero is returned if there are
1197 no back references.
1198 .sp
1200 .sp
1201 Return the number of capturing subpatterns in the pattern. The fourth argument
1202 should point to an \fBint\fP variable.
1203 .sp
1205 .sp
1206 Return a pointer to the internal default character tables within PCRE. The
1207 fourth argument should point to an \fBunsigned char *\fP variable. This
1208 information call is provided for internal use by the \fBpcre_study()\fP
1209 function. External callers can cause PCRE to use its internal tables by passing
1210 a NULL table pointer.
1211 .sp
1213 .sp
1214 Return information about the first data unit of any matched string, for a
1215 non-anchored pattern. (The name of this option refers to the 8-bit library,
1216 where data units are bytes.) The fourth argument should point to an \fBint\fP
1217 variable.
1218 .P
1219 If there is a fixed first value, for example, the letter "c" from a pattern
1220 such as (cat|cow|coyote), its value is returned. In the 8-bit library, the
1221 value is always less than 256. In the 16-bit library the value can be up to
1222 0xffff. In the 32-bit library the value can be up to 0x10ffff.
1223 .P
1224 If there is no fixed first value, and if either
1225 .sp
1226 (a) the pattern was compiled with the PCRE_MULTILINE option, and every branch
1227 starts with "^", or
1228 .sp
1229 (b) every branch of the pattern starts with ".*" and PCRE_DOTALL is not set
1230 (if it were set, the pattern would be anchored),
1231 .sp
1232 -1 is returned, indicating that the pattern matches only at the start of a
1233 subject string or after any newline within the string. Otherwise -2 is
1234 returned. For anchored patterns, -2 is returned.
1235 .P
1236 Since for the 32-bit library using the non-UTF-32 mode, this function is unable
1237 to return the full 32-bit range of the character, this value is deprecated;
1239 should be used.
1240 .sp
1242 .sp
1243 If the pattern was studied, and this resulted in the construction of a 256-bit
1244 table indicating a fixed set of values for the first data unit in any matching
1245 string, a pointer to the table is returned. Otherwise NULL is returned. The
1246 fourth argument should point to an \fBunsigned char *\fP variable.
1247 .sp
1249 .sp
1250 Return 1 if the pattern contains any explicit matches for CR or LF characters,
1251 otherwise 0. The fourth argument should point to an \fBint\fP variable. An
1252 explicit match is either a literal CR or LF character, or \er or \en.
1253 .sp
1255 .sp
1256 Return 1 if the (?J) or (?-J) option setting is used in the pattern, otherwise
1257 0. The fourth argument should point to an \fBint\fP variable. (?J) and
1258 (?-J) set and unset the local PCRE_DUPNAMES option, respectively.
1259 .sp
1261 .sp
1262 Return 1 if the pattern was studied with one of the JIT options, and
1263 just-in-time compiling was successful. The fourth argument should point to an
1264 \fBint\fP variable. A return value of 0 means that JIT support is not available
1265 in this version of PCRE, or that the pattern was not studied with a JIT option,
1266 or that the JIT compiler could not handle this particular pattern. See the
1267 .\" HREF
1268 \fBpcrejit\fP
1269 .\"
1270 documentation for details of what can and cannot be handled.
1271 .sp
1273 .sp
1274 If the pattern was successfully studied with a JIT option, return the size of
1275 the JIT compiled code, otherwise return zero. The fourth argument should point
1276 to a \fBsize_t\fP variable.
1277 .sp
1279 .sp
1280 Return the value of the rightmost literal data unit that must exist in any
1281 matched string, other than at its start, if such a value has been recorded. The
1282 fourth argument should point to an \fBint\fP variable. If there is no such
1283 value, -1 is returned. For anchored patterns, a last literal value is recorded
1284 only if it follows something of variable length. For example, for the pattern
1285 /^a\ed+z\ed+/ the returned value is "z", but for /^a\edz\ed/ the returned value
1286 is -1.
1287 .P
1288 Since for the 32-bit library using the non-UTF-32 mode, this function is unable
1289 to return the full 32-bit range of characters, this value is deprecated;
1291 be used.
1292 .sp
1294 .sp
1295 Return 1 if the pattern can match an empty string, otherwise 0. The fourth
1296 argument should point to an \fBint\fP variable.
1297 .sp
1299 .sp
1300 If the pattern set a match limit by including an item of the form
1301 (*LIMIT_MATCH=nnnn) at the start, the value is returned. The fourth argument
1302 should point to an unsigned 32-bit integer. If no such value has been set, the
1303 call to \fBpcre_fullinfo()\fP returns the error PCRE_ERROR_UNSET.
1304 .sp
1306 .sp
1307 Return the number of characters (NB not data units) in the longest lookbehind
1308 assertion in the pattern. This information is useful when doing multi-segment
1309 matching using the partial matching facilities. Note that the simple assertions
1310 \eb and \eB require a one-character lookbehind. \eA also registers a
1311 one-character lookbehind, though it does not actually inspect the previous
1312 character. This is to ensure that at least one character from the old segment
1313 is retained when a new segment is processed. Otherwise, if there are no
1314 lookbehinds in the pattern, \eA might match incorrectly at the start of a new
1315 segment.
1316 .sp
1318 .sp
1319 If the pattern was studied and a minimum length for matching subject strings
1320 was computed, its value is returned. Otherwise the returned value is -1. The
1321 value is a number of characters, which in UTF mode may be different from the
1322 number of data units. The fourth argument should point to an \fBint\fP
1323 variable. A non-negative value is a lower bound to the length of any matching
1324 string. There may not be any strings of that length that do actually match, but
1325 every string that does match is at least that long.
1326 .sp
1330 .sp
1331 PCRE supports the use of named as well as numbered capturing parentheses. The
1332 names are just an additional way of identifying the parentheses, which still
1333 acquire numbers. Several convenience functions such as
1334 \fBpcre_get_named_substring()\fP are provided for extracting captured
1335 substrings by name. It is also possible to extract the data directly, by first
1336 converting the name to a number in order to access the correct pointers in the
1337 output vector (described with \fBpcre_exec()\fP below). To do the conversion,
1338 you need to use the name-to-number map, which is described by these three
1339 values.
1340 .P
1341 The map consists of a number of fixed-size entries. PCRE_INFO_NAMECOUNT gives
1342 the number of entries, and PCRE_INFO_NAMEENTRYSIZE gives the size of each
1343 entry; both of these return an \fBint\fP value. The entry size depends on the
1344 length of the longest name. PCRE_INFO_NAMETABLE returns a pointer to the first
1345 entry of the table. This is a pointer to \fBchar\fP in the 8-bit library, where
1346 the first two bytes of each entry are the number of the capturing parenthesis,
1347 most significant byte first. In the 16-bit library, the pointer points to
1348 16-bit data units, the first of which contains the parenthesis number. In the
1349 32-bit library, the pointer points to 32-bit data units, the first of which
1350 contains the parenthesis number. The rest of the entry is the corresponding
1351 name, zero terminated.
1352 .P
1353 The names are in alphabetical order. Duplicate names may appear if (?| is used
1354 to create multiple groups with the same number, as described in the
1355 .\" HTML <a href="pcrepattern.html#dupsubpatternnumber">
1356 .\" </a>
1357 section on duplicate subpattern numbers
1358 .\"
1359 in the
1360 .\" HREF
1361 \fBpcrepattern\fP
1362 .\"
1363 page. Duplicate names for subpatterns with different numbers are permitted only
1364 if PCRE_DUPNAMES is set. In all cases of duplicate names, they appear in the
1365 table in the order in which they were found in the pattern. In the absence of
1366 (?| this is the order of increasing number; when (?| is used this is not
1367 necessarily the case because later subpatterns may have lower numbers.
1368 .P
1369 As a simple example of the name/number table, consider the following pattern
1370 after compilation by the 8-bit library (assume PCRE_EXTENDED is set, so white
1371 space - including newlines - is ignored):
1372 .sp
1373 .\" JOIN
1374 (?<date> (?<year>(\ed\ed)?\ed\ed) -
1375 (?<month>\ed\ed) - (?<day>\ed\ed) )
1376 .sp
1377 There are four named subpatterns, so the table has four entries, and each entry
1378 in the table is eight bytes long. The table is as follows, with non-printing
1379 bytes shows in hexadecimal, and undefined bytes shown as ??:
1380 .sp
1381 00 01 d a t e 00 ??
1382 00 05 d a y 00 ?? ??
1383 00 04 m o n t h 00
1384 00 02 y e a r 00 ??
1385 .sp
1386 When writing code to extract data from named subpatterns using the
1387 name-to-number map, remember that the length of the entries is likely to be
1388 different for each compiled pattern.
1389 .sp
1391 .sp
1392 Return 1 if the pattern can be used for partial matching with
1393 \fBpcre_exec()\fP, otherwise 0. The fourth argument should point to an
1394 \fBint\fP variable. From release 8.00, this always returns 1, because the
1395 restrictions that previously applied to partial matching have been lifted. The
1396 .\" HREF
1397 \fBpcrepartial\fP
1398 .\"
1399 documentation gives details of partial matching.
1400 .sp
1402 .sp
1403 Return a copy of the options with which the pattern was compiled. The fourth
1404 argument should point to an \fBunsigned long int\fP variable. These option bits
1405 are those specified in the call to \fBpcre_compile()\fP, modified by any
1406 top-level option settings at the start of the pattern itself. In other words,
1407 they are the options that will be in force when matching starts. For example,
1408 if the pattern /(?im)abc(?-i)d/ is compiled with the PCRE_EXTENDED option, the
1410 .P
1411 A pattern is automatically anchored by PCRE if all of its top-level
1412 alternatives begin with one of the following:
1413 .sp
1414 ^ unless PCRE_MULTILINE is set
1415 \eA always
1416 \eG always
1417 .\" JOIN
1418 .* if PCRE_DOTALL is set and there are no back
1419 references to the subpattern in which .* appears
1420 .sp
1421 For such patterns, the PCRE_ANCHORED bit is set in the options returned by
1422 \fBpcre_fullinfo()\fP.
1423 .sp
1425 .sp
1426 If the pattern set a recursion limit by including an item of the form
1427 (*LIMIT_RECURSION=nnnn) at the start, the value is returned. The fourth
1428 argument should point to an unsigned 32-bit integer. If no such value has been
1429 set, the call to \fBpcre_fullinfo()\fP returns the error PCRE_ERROR_UNSET.
1430 .sp
1432 .sp
1433 Return the size of the compiled pattern in bytes (for all three libraries). The
1434 fourth argument should point to a \fBsize_t\fP variable. This value does not
1435 include the size of the \fBpcre\fP structure that is returned by
1436 \fBpcre_compile()\fP. The value that is passed as the argument to
1437 \fBpcre_malloc()\fP when \fBpcre_compile()\fP is getting memory in which to
1438 place the compiled data is the value returned by this option plus the size of
1439 the \fBpcre\fP structure. Studying a compiled pattern, with or without JIT,
1440 does not alter the value returned by this option.
1441 .sp
1443 .sp
1444 Return the size in bytes (for all three libraries) of the data block pointed to
1445 by the \fIstudy_data\fP field in a \fBpcre_extra\fP block. If \fBpcre_extra\fP
1446 is NULL, or there is no study data, zero is returned. The fourth argument
1447 should point to a \fBsize_t\fP variable. The \fIstudy_data\fP field is set by
1448 \fBpcre_study()\fP to record information that will speed up matching (see the
1449 section entitled
1450 .\" HTML <a href="#studyingapattern">
1451 .\" </a>
1452 "Studying a pattern"
1453 .\"
1454 above). The format of the \fIstudy_data\fP block is private, but its length
1455 is made available via this option so that it can be saved and restored (see the
1456 .\" HREF
1457 \fBpcreprecompile\fP
1458 .\"
1459 documentation for details).
1460 .sp
1462 .sp
1463 Return information about the first data unit of any matched string, for a
1464 non-anchored pattern. The fourth argument should point to an \fBint\fP
1465 variable.
1466 .P
1467 If there is a fixed first value, for example, the letter "c" from a pattern
1468 such as (cat|cow|coyote), 1 is returned, and the character value can be
1469 retrieved using PCRE_INFO_FIRSTCHARACTER.
1470 .P
1471 If there is no fixed first value, and if either
1472 .sp
1473 (a) the pattern was compiled with the PCRE_MULTILINE option, and every branch
1474 starts with "^", or
1475 .sp
1476 (b) every branch of the pattern starts with ".*" and PCRE_DOTALL is not set
1477 (if it were set, the pattern would be anchored),
1478 .sp
1479 2 is returned, indicating that the pattern matches only at the start of a
1480 subject string or after any newline within the string. Otherwise 0 is
1481 returned. For anchored patterns, 0 is returned.
1482 .sp
1484 .sp
1485 Return the fixed first character value in the situation where
1486 PCRE_INFO_FIRSTCHARACTERFLAGS returns 1; otherwise return 0. The fourth
1487 argument should point to an \fBuint_t\fP variable.
1488 .P
1489 In the 8-bit library, the value is always less than 256. In the 16-bit library
1490 the value can be up to 0xffff. In the 32-bit library in UTF-32 mode the value
1491 can be up to 0x10ffff, and up to 0xffffffff when not using UTF-32 mode.
1492 .sp
1494 .sp
1495 Returns 1 if there is a rightmost literal data unit that must exist in any
1496 matched string, other than at its start. The fourth argument should point to
1497 an \fBint\fP variable. If there is no such value, 0 is returned. If returning
1498 1, the character value itself can be retrieved using PCRE_INFO_REQUIREDCHAR.
1499 .P
1500 For anchored patterns, a last literal value is recorded only if it follows
1501 something of variable length. For example, for the pattern /^a\ed+z\ed+/ the
1502 returned value 1 (with "z" returned from PCRE_INFO_REQUIREDCHAR), but for
1503 /^a\edz\ed/ the returned value is 0.
1504 .sp
1506 .sp
1507 Return the value of the rightmost literal data unit that must exist in any
1508 matched string, other than at its start, if such a value has been recorded. The
1509 fourth argument should point to an \fBuint32_t\fP variable. If there is no such
1510 value, 0 is returned.
1511 .
1512 .
1514 .rs
1515 .sp
1516 .B int pcre_refcount(pcre *\fIcode\fP, int \fIadjust\fP);
1517 .PP
1518 The \fBpcre_refcount()\fP function is used to maintain a reference count in the
1519 data block that contains a compiled pattern. It is provided for the benefit of
1520 applications that operate in an object-oriented manner, where different parts
1521 of the application may be using the same compiled pattern, but you want to free
1522 the block when they are all done.
1523 .P
1524 When a pattern is compiled, the reference count field is initialized to zero.
1525 It is changed only by calling this function, whose action is to add the
1526 \fIadjust\fP value (which may be positive or negative) to it. The yield of the
1527 function is the new value. However, the value of the count is constrained to
1528 lie between 0 and 65535, inclusive. If the new value is outside these limits,
1529 it is forced to the appropriate limit value.
1530 .P
1531 Except when it is zero, the reference count is not correctly preserved if a
1532 pattern is compiled on one host and then transferred to a host whose byte-order
1533 is different. (This seems a highly unlikely scenario.)
1534 .
1535 .
1537 .rs
1538 .sp
1539 .nf
1540 .B int pcre_exec(const pcre *\fIcode\fP, "const pcre_extra *\fIextra\fP,"
1541 .B " const char *\fIsubject\fP," int \fIlength\fP, int \fIstartoffset\fP,
1542 .B " int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP);"
1543 .fi
1544 .P
1545 The function \fBpcre_exec()\fP is called to match a subject string against a
1546 compiled pattern, which is passed in the \fIcode\fP argument. If the
1547 pattern was studied, the result of the study should be passed in the
1548 \fIextra\fP argument. You can call \fBpcre_exec()\fP with the same \fIcode\fP
1549 and \fIextra\fP arguments as many times as you like, in order to match
1550 different subject strings with the same pattern.
1551 .P
1552 This function is the main matching facility of the library, and it operates in
1553 a Perl-like manner. For specialist use there is also an alternative matching
1554 function, which is described
1555 .\" HTML <a href="#dfamatch">
1556 .\" </a>
1557 below
1558 .\"
1559 in the section about the \fBpcre_dfa_exec()\fP function.
1560 .P
1561 In most applications, the pattern will have been compiled (and optionally
1562 studied) in the same process that calls \fBpcre_exec()\fP. However, it is
1563 possible to save compiled patterns and study data, and then use them later
1564 in different processes, possibly even on different hosts. For a discussion
1565 about this, see the
1566 .\" HREF
1567 \fBpcreprecompile\fP
1568 .\"
1569 documentation.
1570 .P
1571 Here is an example of a simple call to \fBpcre_exec()\fP:
1572 .sp
1573 int rc;
1574 int ovector[30];
1575 rc = pcre_exec(
1576 re, /* result of pcre_compile() */
1577 NULL, /* we didn't study the pattern */
1578 "some string", /* the subject string */
1579 11, /* the length of the subject string */
1580 0, /* start at offset 0 in the subject */
1581 0, /* default options */
1582 ovector, /* vector of integers for substring information */
1583 30); /* number of elements (NOT size in bytes) */
1584 .
1585 .
1586 .\" HTML <a name="extradata"></a>
1587 .SS "Extra data for \fBpcre_exec()\fR"
1588 .rs
1589 .sp
1590 If the \fIextra\fP argument is not NULL, it must point to a \fBpcre_extra\fP
1591 data block. The \fBpcre_study()\fP function returns such a block (when it
1592 doesn't return NULL), but you can also create one for yourself, and pass
1593 additional information in it. The \fBpcre_extra\fP block contains the following
1594 fields (not necessarily in this order):
1595 .sp
1596 unsigned long int \fIflags\fP;
1597 void *\fIstudy_data\fP;
1598 void *\fIexecutable_jit\fP;
1599 unsigned long int \fImatch_limit\fP;
1600 unsigned long int \fImatch_limit_recursion\fP;
1601 void *\fIcallout_data\fP;
1602 const unsigned char *\fItables\fP;
1603 unsigned char **\fImark\fP;
1604 .sp
1605 In the 16-bit version of this structure, the \fImark\fP field has type
1606 "PCRE_UCHAR16 **".
1607 .sp
1608 In the 32-bit version of this structure, the \fImark\fP field has type
1609 "PCRE_UCHAR32 **".
1610 .P
1611 The \fIflags\fP field is used to specify which of the other fields are set. The
1612 flag bits are:
1613 .sp
1621 .sp
1622 Other flag bits should be set to zero. The \fIstudy_data\fP field and sometimes
1623 the \fIexecutable_jit\fP field are set in the \fBpcre_extra\fP block that is
1624 returned by \fBpcre_study()\fP, together with the appropriate flag bits. You
1625 should not set these yourself, but you may add to the block by setting other
1626 fields and their corresponding flag bits.
1627 .P
1628 The \fImatch_limit\fP field provides a means of preventing PCRE from using up a
1629 vast amount of resources when running patterns that are not going to match,
1630 but which have a very large number of possibilities in their search trees. The
1631 classic example is a pattern that uses nested unlimited repeats.
1632 .P
1633 Internally, \fBpcre_exec()\fP uses a function called \fBmatch()\fP, which it
1634 calls repeatedly (sometimes recursively). The limit set by \fImatch_limit\fP is
1635 imposed on the number of times this function is called during a match, which
1636 has the effect of limiting the amount of backtracking that can take place. For
1637 patterns that are not anchored, the count restarts from zero for each position
1638 in the subject string.
1639 .P
1640 When \fBpcre_exec()\fP is called with a pattern that was successfully studied
1641 with a JIT option, the way that the matching is executed is entirely different.
1642 However, there is still the possibility of runaway matching that goes on for a
1643 very long time, and so the \fImatch_limit\fP value is also used in this case
1644 (but in a different way) to limit how long the matching can continue.
1645 .P
1646 The default value for the limit can be set when PCRE is built; the default
1647 default is 10 million, which handles all but the most extreme cases. You can
1648 override the default by suppling \fBpcre_exec()\fP with a \fBpcre_extra\fP
1649 block in which \fImatch_limit\fP is set, and PCRE_EXTRA_MATCH_LIMIT is set in
1650 the \fIflags\fP field. If the limit is exceeded, \fBpcre_exec()\fP returns
1652 .P
1653 A value for the match limit may also be supplied by an item at the start of a
1654 pattern of the form
1655 .sp
1656 (*LIMIT_MATCH=d)
1657 .sp
1658 where d is a decimal number. However, such a setting is ignored unless d is
1659 less than the limit set by the caller of \fBpcre_exec()\fP or, if no such limit
1660 is set, less than the default.
1661 .P
1662 The \fImatch_limit_recursion\fP field is similar to \fImatch_limit\fP, but
1663 instead of limiting the total number of times that \fBmatch()\fP is called, it
1664 limits the depth of recursion. The recursion depth is a smaller number than the
1665 total number of calls, because not all calls to \fBmatch()\fP are recursive.
1666 This limit is of use only if it is set smaller than \fImatch_limit\fP.
1667 .P
1668 Limiting the recursion depth limits the amount of machine stack that can be
1669 used, or, when PCRE has been compiled to use memory on the heap instead of the
1670 stack, the amount of heap memory that can be used. This limit is not relevant,
1671 and is ignored, when matching is done using JIT compiled code.
1672 .P
1673 The default value for \fImatch_limit_recursion\fP can be set when PCRE is
1674 built; the default default is the same value as the default for
1675 \fImatch_limit\fP. You can override the default by suppling \fBpcre_exec()\fP
1676 with a \fBpcre_extra\fP block in which \fImatch_limit_recursion\fP is set, and
1677 PCRE_EXTRA_MATCH_LIMIT_RECURSION is set in the \fIflags\fP field. If the limit
1678 is exceeded, \fBpcre_exec()\fP returns PCRE_ERROR_RECURSIONLIMIT.
1679 .P
1680 A value for the recursion limit may also be supplied by an item at the start of
1681 a pattern of the form
1682 .sp
1684 .sp
1685 where d is a decimal number. However, such a setting is ignored unless d is
1686 less than the limit set by the caller of \fBpcre_exec()\fP or, if no such limit
1687 is set, less than the default.
1688 .P
1689 The \fIcallout_data\fP field is used in conjunction with the "callout" feature,
1690 and is described in the
1691 .\" HREF
1692 \fBpcrecallout\fP
1693 .\"
1694 documentation.
1695 .P
1696 The \fItables\fP field is used to pass a character tables pointer to
1697 \fBpcre_exec()\fP; this overrides the value that is stored with the compiled
1698 pattern. A non-NULL value is stored with the compiled pattern only if custom
1699 tables were supplied to \fBpcre_compile()\fP via its \fItableptr\fP argument.
1700 If NULL is passed to \fBpcre_exec()\fP using this mechanism, it forces PCRE's
1701 internal tables to be used. This facility is helpful when re-using patterns
1702 that have been saved after compiling with an external set of tables, because
1703 the external tables might be at a different address when \fBpcre_exec()\fP is
1704 called. See the
1705 .\" HREF
1706 \fBpcreprecompile\fP
1707 .\"
1708 documentation for a discussion of saving compiled patterns for later use.
1709 .P
1710 If PCRE_EXTRA_MARK is set in the \fIflags\fP field, the \fImark\fP field must
1711 be set to point to a suitable variable. If the pattern contains any
1712 backtracking control verbs such as (*MARK:NAME), and the execution ends up with
1713 a name to pass back, a pointer to the name string (zero terminated) is placed
1714 in the variable pointed to by the \fImark\fP field. The names are within the
1715 compiled pattern; if you wish to retain such a name you must copy it before
1716 freeing the memory of a compiled pattern. If there is no name to pass back, the
1717 variable pointed to by the \fImark\fP field is set to NULL. For details of the
1718 backtracking control verbs, see the section entitled
1719 .\" HTML <a href="pcrepattern#backtrackcontrol">
1720 .\" </a>
1721 "Backtracking control"
1722 .\"
1723 in the
1724 .\" HREF
1725 \fBpcrepattern\fP
1726 .\"
1727 documentation.
1728 .
1729 .
1730 .\" HTML <a name="execoptions"></a>
1731 .SS "Option bits for \fBpcre_exec()\fP"
1732 .rs
1733 .sp
1734 The unused bits of the \fIoptions\fP argument for \fBpcre_exec()\fP must be
1735 zero. The only bits that may be set are PCRE_ANCHORED, PCRE_NEWLINE_\fIxxx\fP,
1739 .P
1740 If the pattern was successfully studied with one of the just-in-time (JIT)
1741 compile options, the only supported options for JIT execution are
1744 unsupported option is used, JIT execution is disabled and the normal
1745 interpretive code in \fBpcre_exec()\fP is run.
1746 .sp
1748 .sp
1749 The PCRE_ANCHORED option limits \fBpcre_exec()\fP to matching at the first
1750 matching position. If a pattern was compiled with PCRE_ANCHORED, or turned out
1751 to be anchored by virtue of its contents, it cannot be made unachored at
1752 matching time.
1753 .sp
1756 .sp
1757 These options (which are mutually exclusive) control what the \eR escape
1758 sequence matches. The choice is either to match only CR, LF, or CRLF, or to
1759 match any Unicode newline sequence. These options override the choice that was
1760 made or defaulted when the pattern was compiled.
1761 .sp
1767 .sp
1768 These options override the newline definition that was chosen or defaulted when
1769 the pattern was compiled. For details, see the description of
1770 \fBpcre_compile()\fP above. During matching, the newline choice affects the
1771 behaviour of the dot, circumflex, and dollar metacharacters. It may also alter
1772 the way the match position is advanced after a match failure for an unanchored
1773 pattern.
1774 .P
1776 match attempt for an unanchored pattern fails when the current position is at a
1777 CRLF sequence, and the pattern contains no explicit matches for CR or LF
1778 characters, the match position is advanced by two characters instead of one, in
1779 other words, to after the CRLF.
1780 .P
1781 The above rule is a compromise that makes the most common cases work as
1782 expected. For example, if the pattern is .+A (and the PCRE_DOTALL option is not
1783 set), it does not match the string "\er\enA" because, after failing at the
1784 start, it skips both the CR and the LF before retrying. However, the pattern
1785 [\er\en]A does match that string, because it contains an explicit CR or LF
1786 reference, and so advances only by one character after the first failure.
1787 .P
1788 An explicit match for CR of LF is either a literal appearance of one of those
1789 characters, or one of the \er or \en escape sequences. Implicit matches such as
1790 [^X] do not count, nor does \es (which includes CR and LF in the characters
1791 that it matches).
1792 .P
1793 Notwithstanding the above, anomalous effects may still occur when CRLF is a
1794 valid newline sequence and explicit \er or \en escapes appear in the pattern.
1795 .sp
1797 .sp
1798 This option specifies that first character of the subject string is not the
1799 beginning of a line, so the circumflex metacharacter should not match before
1800 it. Setting this without PCRE_MULTILINE (at compile time) causes circumflex
1801 never to match. This option affects only the behaviour of the circumflex
1802 metacharacter. It does not affect \eA.
1803 .sp
1805 .sp
1806 This option specifies that the end of the subject string is not the end of a
1807 line, so the dollar metacharacter should not match it nor (except in multiline
1808 mode) a newline immediately before it. Setting this without PCRE_MULTILINE (at
1809 compile time) causes dollar never to match. This option affects only the
1810 behaviour of the dollar metacharacter. It does not affect \eZ or \ez.
1811 .sp
1813 .sp
1814 An empty string is not considered to be a valid match if this option is set. If
1815 there are alternatives in the pattern, they are tried. If all the alternatives
1816 match the empty string, the entire match fails. For example, if the pattern
1817 .sp
1818 a?b?
1819 .sp
1820 is applied to a string not beginning with "a" or "b", it matches an empty
1821 string at the start of the subject. With PCRE_NOTEMPTY set, this match is not
1822 valid, so PCRE searches further into the string for occurrences of "a" or "b".
1823 .sp
1825 .sp
1826 This is like PCRE_NOTEMPTY, except that an empty string match that is not at
1827 the start of the subject is permitted. If the pattern is anchored, such a match
1828 can occur only if the pattern contains \eK.
1829 .P
1830 Perl has no direct equivalent of PCRE_NOTEMPTY or PCRE_NOTEMPTY_ATSTART, but it
1831 does make a special case of a pattern match of the empty string within its
1832 \fBsplit()\fP function, and when using the /g modifier. It is possible to
1833 emulate Perl's behaviour after matching a null string by first trying the match
1834 again at the same offset with PCRE_NOTEMPTY_ATSTART and PCRE_ANCHORED, and then
1835 if that fails, by advancing the starting offset (see below) and trying an
1836 ordinary match again. There is some code that demonstrates how to do this in
1837 the
1838 .\" HREF
1839 \fBpcredemo\fP
1840 .\"
1841 sample program. In the most general case, you have to check to see if the
1842 newline convention recognizes CRLF as a newline, and if so, and the current
1843 character is CR followed by LF, advance the starting offset by two characters
1844 instead of one.
1845 .sp
1847 .sp
1848 There are a number of optimizations that \fBpcre_exec()\fP uses at the start of
1849 a match, in order to speed up the process. For example, if it is known that an
1850 unanchored match must start with a specific character, it searches the subject
1851 for that character, and fails immediately if it cannot find it, without
1852 actually running the main matching function. This means that a special item
1853 such as (*COMMIT) at the start of a pattern is not considered until after a
1854 suitable starting point for the match has been found. Also, when callouts or
1855 (*MARK) items are in use, these "start-up" optimizations can cause them to be
1856 skipped if the pattern is never actually used. The start-up optimizations are
1857 in effect a pre-scan of the subject that takes place before the pattern is run.
1858 .P
1859 The PCRE_NO_START_OPTIMIZE option disables the start-up optimizations, possibly
1860 causing performance to suffer, but ensuring that in cases where the result is
1861 "no match", the callouts do occur, and that items such as (*COMMIT) and (*MARK)
1862 are considered at every possible starting position in the subject string. If
1863 PCRE_NO_START_OPTIMIZE is set at compile time, it cannot be unset at matching
1864 time. The use of PCRE_NO_START_OPTIMIZE at matching time (that is, passing it
1865 to \fBpcre_exec()\fP) disables JIT execution; in this situation, matching is
1866 always done using interpretively.
1867 .P
1868 Setting PCRE_NO_START_OPTIMIZE can change the outcome of a matching operation.
1869 Consider the pattern
1870 .sp
1872 .sp
1873 When this is compiled, PCRE records the fact that a match must start with the
1874 character "A". Suppose the subject string is "DEFABC". The start-up
1875 optimization scans along the subject, finds "A" and runs the first match
1876 attempt from there. The (*COMMIT) item means that the pattern must match the
1877 current starting position, which in this case, it does. However, if the same
1878 match is run with PCRE_NO_START_OPTIMIZE set, the initial scan along the
1879 subject string does not happen. The first match attempt is run starting from
1880 "D" and when this fails, (*COMMIT) prevents any further matches being tried, so
1881 the overall result is "no match". If the pattern is studied, more start-up
1882 optimizations may be used. For example, a minimum length for the subject may be
1883 recorded. Consider the pattern
1884 .sp
1885 (*MARK:A)(X|Y)
1886 .sp
1887 The minimum length for a match is one character. If the subject is "ABC", there
1888 will be attempts to match "ABC", "BC", "C", and then finally an empty string.
1889 If the pattern is studied, the final attempt does not take place, because PCRE
1890 knows that the subject is too short, and so the (*MARK) is never encountered.
1891 In this case, studying the pattern does not affect the overall match result,
1892 which is still "no match", but it does affect the auxiliary information that is
1893 returned.
1894 .sp
1896 .sp
1897 When PCRE_UTF8 is set at compile time, the validity of the subject as a UTF-8
1898 string is automatically checked when \fBpcre_exec()\fP is subsequently called.
1899 The entire string is checked before any other processing takes place. The value
1900 of \fIstartoffset\fP is also checked to ensure that it points to the start of a
1901 UTF-8 character. There is a discussion about the
1902 .\" HTML <a href="pcreunicode.html#utf8strings">
1903 .\" </a>
1904 validity of UTF-8 strings
1905 .\"
1906 in the
1907 .\" HREF
1908 \fBpcreunicode\fP
1909 .\"
1910 page. If an invalid sequence of bytes is found, \fBpcre_exec()\fP returns the
1911 error PCRE_ERROR_BADUTF8 or, if PCRE_PARTIAL_HARD is set and the problem is a
1912 truncated character at the end of the subject, PCRE_ERROR_SHORTUTF8. In both
1913 cases, information about the precise nature of the error may also be returned
1914 (see the descriptions of these errors in the section entitled \fIError return
1915 values from\fP \fBpcre_exec()\fP
1916 .\" HTML <a href="#errorlist">
1917 .\" </a>
1918 below).
1919 .\"
1920 If \fIstartoffset\fP contains a value that does not point to the start of a
1921 UTF-8 character (or to the end of the subject), PCRE_ERROR_BADUTF8_OFFSET is
1922 returned.
1923 .P
1924 If you already know that your subject is valid, and you want to skip these
1925 checks for performance reasons, you can set the PCRE_NO_UTF8_CHECK option when
1926 calling \fBpcre_exec()\fP. You might want to do this for the second and
1927 subsequent calls to \fBpcre_exec()\fP if you are making repeated calls to find
1928 all the matches in a single subject string. However, you should be sure that
1929 the value of \fIstartoffset\fP points to the start of a character (or the end
1930 of the subject). When PCRE_NO_UTF8_CHECK is set, the effect of passing an
1931 invalid string as a subject or an invalid value of \fIstartoffset\fP is
1932 undefined. Your program may crash.
1933 .sp
1936 .sp
1937 These options turn on the partial matching feature. For backwards
1938 compatibility, PCRE_PARTIAL is a synonym for PCRE_PARTIAL_SOFT. A partial match
1939 occurs if the end of the subject string is reached successfully, but there are
1940 not enough subject characters to complete the match. If this happens when
1941 PCRE_PARTIAL_SOFT (but not PCRE_PARTIAL_HARD) is set, matching continues by
1942 testing any remaining alternatives. Only if no complete match can be found is
1943 PCRE_ERROR_PARTIAL returned instead of PCRE_ERROR_NOMATCH. In other words,
1944 PCRE_PARTIAL_SOFT says that the caller is prepared to handle a partial match,
1945 but only if no complete match can be found.
1946 .P
1947 If PCRE_PARTIAL_HARD is set, it overrides PCRE_PARTIAL_SOFT. In this case, if a
1948 partial match is found, \fBpcre_exec()\fP immediately returns
1949 PCRE_ERROR_PARTIAL, without considering any other alternatives. In other words,
1950 when PCRE_PARTIAL_HARD is set, a partial match is considered to be more
1951 important that an alternative complete match.
1952 .P
1953 In both cases, the portion of the string that was inspected when the partial
1954 match was found is set as the first matching string. There is a more detailed
1955 discussion of partial and multi-segment matching, with examples, in the
1956 .\" HREF
1957 \fBpcrepartial\fP
1958 .\"
1959 documentation.
1960 .
1961 .
1962 .SS "The string to be matched by \fBpcre_exec()\fP"
1963 .rs
1964 .sp
1965 The subject string is passed to \fBpcre_exec()\fP as a pointer in
1966 \fIsubject\fP, a length in \fIlength\fP, and a starting offset in
1967 \fIstartoffset\fP. The units for \fIlength\fP and \fIstartoffset\fP are bytes
1968 for the 8-bit library, 16-bit data items for the 16-bit library, and 32-bit
1969 data items for the 32-bit library.
1970 .P
1971 If \fIstartoffset\fP is negative or greater than the length of the subject,
1972 \fBpcre_exec()\fP returns PCRE_ERROR_BADOFFSET. When the starting offset is
1973 zero, the search for a match starts at the beginning of the subject, and this
1974 is by far the most common case. In UTF-8 or UTF-16 mode, the offset must point
1975 to the start of a character, or the end of the subject (in UTF-32 mode, one
1976 data unit equals one character, so all offsets are valid). Unlike the pattern
1977 string, the subject may contain binary zeroes.
1978 .P
1979 A non-zero starting offset is useful when searching for another match in the
1980 same subject by calling \fBpcre_exec()\fP again after a previous success.
1981 Setting \fIstartoffset\fP differs from just passing over a shortened string and
1982 setting PCRE_NOTBOL in the case of a pattern that begins with any kind of
1983 lookbehind. For example, consider the pattern
1984 .sp
1985 \eBiss\eB
1986 .sp
1987 which finds occurrences of "iss" in the middle of words. (\eB matches only if
1988 the current position in the subject is not a word boundary.) When applied to
1989 the string "Mississipi" the first call to \fBpcre_exec()\fP finds the first
1990 occurrence. If \fBpcre_exec()\fP is called again with just the remainder of the
1991 subject, namely "issipi", it does not match, because \eB is always false at the
1992 start of the subject, which is deemed to be a word boundary. However, if
1993 \fBpcre_exec()\fP is passed the entire string again, but with \fIstartoffset\fP
1994 set to 4, it finds the second occurrence of "iss" because it is able to look
1995 behind the starting point to discover that it is preceded by a letter.
1996 .P
1997 Finding all the matches in a subject is tricky when the pattern can match an
1998 empty string. It is possible to emulate Perl's /g behaviour by first trying the
1999 match again at the same offset, with the PCRE_NOTEMPTY_ATSTART and
2000 PCRE_ANCHORED options, and then if that fails, advancing the starting offset
2001 and trying an ordinary match again. There is some code that demonstrates how to
2002 do this in the
2003 .\" HREF
2004 \fBpcredemo\fP
2005 .\"
2006 sample program. In the most general case, you have to check to see if the
2007 newline convention recognizes CRLF as a newline, and if so, and the current
2008 character is CR followed by LF, advance the starting offset by two characters
2009 instead of one.
2010 .P
2011 If a non-zero starting offset is passed when the pattern is anchored, one
2012 attempt to match at the given offset is made. This can only succeed if the
2013 pattern does not require the match to be at the start of the subject.
2014 .
2015 .
2016 .SS "How \fBpcre_exec()\fP returns captured substrings"
2017 .rs
2018 .sp
2019 In general, a pattern matches a certain portion of the subject, and in
2020 addition, further substrings from the subject may be picked out by parts of the
2021 pattern. Following the usage in Jeffrey Friedl's book, this is called
2022 "capturing" in what follows, and the phrase "capturing subpattern" is used for
2023 a fragment of a pattern that picks out a substring. PCRE supports several other
2024 kinds of parenthesized subpattern that do not cause substrings to be captured.
2025 .P
2026 Captured substrings are returned to the caller via a vector of integers whose
2027 address is passed in \fIovector\fP. The number of elements in the vector is
2028 passed in \fIovecsize\fP, which must be a non-negative number. \fBNote\fP: this
2029 argument is NOT the size of \fIovector\fP in bytes.
2030 .P
2031 The first two-thirds of the vector is used to pass back captured substrings,
2032 each substring using a pair of integers. The remaining third of the vector is
2033 used as workspace by \fBpcre_exec()\fP while matching capturing subpatterns,
2034 and is not available for passing back information. The number passed in
2035 \fIovecsize\fP should always be a multiple of three. If it is not, it is
2036 rounded down.
2037 .P
2038 When a match is successful, information about captured substrings is returned
2039 in pairs of integers, starting at the beginning of \fIovector\fP, and
2040 continuing up to two-thirds of its length at the most. The first element of
2041 each pair is set to the offset of the first character in a substring, and the
2042 second is set to the offset of the first character after the end of a
2043 substring. These values are always data unit offsets, even in UTF mode. They
2044 are byte offsets in the 8-bit library, 16-bit data item offsets in the 16-bit
2045 library, and 32-bit data item offsets in the 32-bit library. \fBNote\fP: they
2046 are not character counts.
2047 .P
2048 The first pair of integers, \fIovector[0]\fP and \fIovector[1]\fP, identify the
2049 portion of the subject string matched by the entire pattern. The next pair is
2050 used for the first capturing subpattern, and so on. The value returned by
2051 \fBpcre_exec()\fP is one more than the highest numbered pair that has been set.
2052 For example, if two substrings have been captured, the returned value is 3. If
2053 there are no capturing subpatterns, the return value from a successful match is
2054 1, indicating that just the first pair of offsets has been set.
2055 .P
2056 If a capturing subpattern is matched repeatedly, it is the last portion of the
2057 string that it matched that is returned.
2058 .P
2059 If the vector is too small to hold all the captured substring offsets, it is
2060 used as far as possible (up to two-thirds of its length), and the function
2061 returns a value of zero. If neither the actual string matched nor any captured
2062 substrings are of interest, \fBpcre_exec()\fP may be called with \fIovector\fP
2063 passed as NULL and \fIovecsize\fP as zero. However, if the pattern contains
2064 back references and the \fIovector\fP is not big enough to remember the related
2065 substrings, PCRE has to get additional memory for use during matching. Thus it
2066 is usually advisable to supply an \fIovector\fP of reasonable size.
2067 .P
2068 There are some cases where zero is returned (indicating vector overflow) when
2069 in fact the vector is exactly the right size for the final match. For example,
2070 consider the pattern
2071 .sp
2072 (a)(?:(b)c|bd)
2073 .sp
2074 If a vector of 6 elements (allowing for only 1 captured substring) is given
2075 with subject string "abd", \fBpcre_exec()\fP will try to set the second
2076 captured string, thereby recording a vector overflow, before failing to match
2077 "c" and backing up to try the second alternative. The zero return, however,
2078 does correctly indicate that the maximum number of slots (namely 2) have been
2079 filled. In similar cases where there is temporary overflow, but the final
2080 number of used slots is actually less than the maximum, a non-zero value is
2081 returned.
2082 .P
2083 The \fBpcre_fullinfo()\fP function can be used to find out how many capturing
2084 subpatterns there are in a compiled pattern. The smallest size for
2085 \fIovector\fP that will allow for \fIn\fP captured substrings, in addition to
2086 the offsets of the substring matched by the whole pattern, is (\fIn\fP+1)*3.
2087 .P
2088 It is possible for capturing subpattern number \fIn+1\fP to match some part of
2089 the subject when subpattern \fIn\fP has not been used at all. For example, if
2090 the string "abc" is matched against the pattern (a|(z))(bc) the return from the
2091 function is 4, and subpatterns 1 and 3 are matched, but 2 is not. When this
2092 happens, both values in the offset pairs corresponding to unused subpatterns
2093 are set to -1.
2094 .P
2095 Offset values that correspond to unused subpatterns at the end of the
2096 expression are also set to -1. For example, if the string "abc" is matched
2097 against the pattern (abc)(x(yz)?)? subpatterns 2 and 3 are not matched. The
2098 return from the function is 2, because the highest used capturing subpattern
2099 number is 1, and the offsets for for the second and third capturing subpatterns
2100 (assuming the vector is large enough, of course) are set to -1.
2101 .P
2102 \fBNote\fP: Elements in the first two-thirds of \fIovector\fP that do not
2103 correspond to capturing parentheses in the pattern are never changed. That is,
2104 if a pattern contains \fIn\fP capturing parentheses, no more than
2105 \fIovector[0]\fP to \fIovector[2n+1]\fP are set by \fBpcre_exec()\fP. The other
2106 elements (in the first two-thirds) retain whatever values they previously had.
2107 .P
2108 Some convenience functions are provided for extracting the captured substrings
2109 as separate strings. These are described below.
2110 .
2111 .
2112 .\" HTML <a name="errorlist"></a>
2113 .SS "Error return values from \fBpcre_exec()\fP"
2114 .rs
2115 .sp
2116 If \fBpcre_exec()\fP fails, it returns a negative number. The following are
2117 defined in the header file:
2118 .sp
2120 .sp
2121 The subject string did not match the pattern.
2122 .sp
2124 .sp
2125 Either \fIcode\fP or \fIsubject\fP was passed as NULL, or \fIovector\fP was
2126 NULL and \fIovecsize\fP was not zero.
2127 .sp
2129 .sp
2130 An unrecognized bit was set in the \fIoptions\fP argument.
2131 .sp
2133 .sp
2134 PCRE stores a 4-byte "magic number" at the start of the compiled code, to catch
2135 the case when it is passed a junk pointer and to detect when a pattern that was
2136 compiled in an environment of one endianness is run in an environment with the
2137 other endianness. This is the error that PCRE gives when the magic number is
2138 not present.
2139 .sp
2141 .sp
2142 While running the pattern match, an unknown item was encountered in the
2143 compiled pattern. This error could be caused by a bug in PCRE or by overwriting
2144 of the compiled pattern.
2145 .sp
2147 .sp
2148 If a pattern contains back references, but the \fIovector\fP that is passed to
2149 \fBpcre_exec()\fP is not big enough to remember the referenced substrings, PCRE
2150 gets a block of memory at the start of matching to use for this purpose. If the
2151 call via \fBpcre_malloc()\fP fails, this error is given. The memory is
2152 automatically freed at the end of matching.
2153 .P
2154 This error is also given if \fBpcre_stack_malloc()\fP fails in
2155 \fBpcre_exec()\fP. This can happen only when PCRE has been compiled with
2156 \fB--disable-stack-for-recursion\fP.
2157 .sp
2159 .sp
2160 This error is used by the \fBpcre_copy_substring()\fP,
2161 \fBpcre_get_substring()\fP, and \fBpcre_get_substring_list()\fP functions (see
2162 below). It is never returned by \fBpcre_exec()\fP.
2163 .sp
2165 .sp
2166 The backtracking limit, as specified by the \fImatch_limit\fP field in a
2167 \fBpcre_extra\fP structure (or defaulted) was reached. See the description
2168 above.
2169 .sp
2171 .sp
2172 This error is never generated by \fBpcre_exec()\fP itself. It is provided for
2173 use by callout functions that want to yield a distinctive error code. See the
2174 .\" HREF
2175 \fBpcrecallout\fP
2176 .\"
2177 documentation for details.
2178 .sp
2180 .sp
2181 A string that contains an invalid UTF-8 byte sequence was passed as a subject,
2182 and the PCRE_NO_UTF8_CHECK option was not set. If the size of the output vector
2183 (\fIovecsize\fP) is at least 2, the byte offset to the start of the the invalid
2184 UTF-8 character is placed in the first element, and a reason code is placed in
2185 the second element. The reason codes are listed in the
2186 .\" HTML <a href="#badutf8reasons">
2187 .\" </a>
2188 following section.
2189 .\"
2190 For backward compatibility, if PCRE_PARTIAL_HARD is set and the problem is a
2191 truncated UTF-8 character at the end of the subject (reason codes 1 to 5),
2192 PCRE_ERROR_SHORTUTF8 is returned instead of PCRE_ERROR_BADUTF8.
2193 .sp
2195 .sp
2196 The UTF-8 byte sequence that was passed as a subject was checked and found to
2197 be valid (the PCRE_NO_UTF8_CHECK option was not set), but the value of
2198 \fIstartoffset\fP did not point to the beginning of a UTF-8 character or the
2199 end of the subject.
2200 .sp
2202 .sp
2203 The subject string did not match, but it did match partially. See the
2204 .\" HREF
2205 \fBpcrepartial\fP
2206 .\"
2207 documentation for details of partial matching.
2208 .sp
2210 .sp
2211 This code is no longer in use. It was formerly returned when the PCRE_PARTIAL
2212 option was used with a compiled pattern containing items that were not
2213 supported for partial matching. From release 8.00 onwards, there are no
2214 restrictions on partial matching.
2215 .sp
2217 .sp
2218 An unexpected internal error has occurred. This error could be caused by a bug
2219 in PCRE or by overwriting of the compiled pattern.
2220 .sp
2222 .sp
2223 This error is given if the value of the \fIovecsize\fP argument is negative.
2224 .sp
2226 .sp
2227 The internal recursion limit, as specified by the \fImatch_limit_recursion\fP
2228 field in a \fBpcre_extra\fP structure (or defaulted) was reached. See the
2229 description above.
2230 .sp
2232 .sp
2233 An invalid combination of PCRE_NEWLINE_\fIxxx\fP options was given.
2234 .sp
2236 .sp
2237 The value of \fIstartoffset\fP was negative or greater than the length of the
2238 subject, that is, the value in \fIlength\fP.
2239 .sp
2241 .sp
2242 This error is returned instead of PCRE_ERROR_BADUTF8 when the subject string
2243 ends with a truncated UTF-8 character and the PCRE_PARTIAL_HARD option is set.
2244 Information about the failure is returned as for PCRE_ERROR_BADUTF8. It is in
2245 fact sufficient to detect this case, but this special error code for
2246 PCRE_PARTIAL_HARD precedes the implementation of returned information; it is
2247 retained for backwards compatibility.
2248 .sp
2250 .sp
2251 This error is returned when \fBpcre_exec()\fP detects a recursion loop within
2252 the pattern. Specifically, it means that either the whole pattern or a
2253 subpattern has been called recursively for the second time at the same position
2254 in the subject string. Some simple patterns that might do this are detected and
2255 faulted at compile time, but more complicated cases, in particular mutual
2256 recursions between two different subpatterns, cannot be detected until run
2257 time.
2258 .sp
2260 .sp
2261 This error is returned when a pattern that was successfully studied using a
2262 JIT compile option is being matched, but the memory available for the
2263 just-in-time processing stack is not large enough. See the
2264 .\" HREF
2265 \fBpcrejit\fP
2266 .\"
2267 documentation for more details.
2268 .sp
2270 .sp
2271 This error is given if a pattern that was compiled by the 8-bit library is
2272 passed to a 16-bit or 32-bit library function, or vice versa.
2273 .sp
2275 .sp
2276 This error is given if a pattern that was compiled and saved is reloaded on a
2277 host with different endianness. The utility function
2278 \fBpcre_pattern_to_host_byte_order()\fP can be used to convert such a pattern
2279 so that it runs on the new host.
2280 .sp
2282 .sp
2283 This error is returned when a pattern that was successfully studied using a JIT
2284 compile option is being matched, but the matching mode (partial or complete
2285 match) does not correspond to any JIT compilation mode. When the JIT fast path
2286 function is used, this error may be also given for invalid options. See the
2287 .\" HREF
2288 \fBpcrejit\fP
2289 .\"
2290 documentation for more details.
2291 .sp
2293 .sp
2294 This error is given if \fBpcre_exec()\fP is called with a negative value for
2295 the \fIlength\fP argument.
2296 .P
2297 Error numbers -16 to -20, -22, and 30 are not used by \fBpcre_exec()\fP.
2298 .
2299 .
2300 .\" HTML <a name="badutf8reasons"></a>
2301 .SS "Reason codes for invalid UTF-8 strings"
2302 .rs
2303 .sp
2304 This section applies only to the 8-bit library. The corresponding information
2305 for the 16-bit and 32-bit libraries is given in the
2306 .\" HREF
2307 \fBpcre16\fP
2308 .\"
2309 and
2310 .\" HREF
2311 \fBpcre32\fP
2312 .\"
2313 pages.
2314 .P
2315 When \fBpcre_exec()\fP returns either PCRE_ERROR_BADUTF8 or
2316 PCRE_ERROR_SHORTUTF8, and the size of the output vector (\fIovecsize\fP) is at
2317 least 2, the offset of the start of the invalid UTF-8 character is placed in
2318 the first output vector element (\fIovector[0]\fP) and a reason code is placed
2319 in the second element (\fIovector[1]\fP). The reason codes are given names in
2320 the \fBpcre.h\fP header file:
2321 .sp
2327 .sp
2328 The string ends with a truncated UTF-8 character; the code specifies how many
2329 bytes are missing (1 to 5). Although RFC 3629 restricts UTF-8 characters to be
2330 no longer than 4 bytes, the encoding scheme (originally defined by RFC 2279)
2331 allows for up to 6 bytes, and this is checked first; hence the possibility of
2332 4 or 5 missing bytes.
2333 .sp
2338 PCRE_UTF8_ERR10
2339 .sp
2340 The two most significant bits of the 2nd, 3rd, 4th, 5th, or 6th byte of the
2341 character do not have the binary value 0b10 (that is, either the most
2342 significant bit is 0, or the next bit is 1).
2343 .sp
2344 PCRE_UTF8_ERR11
2345 PCRE_UTF8_ERR12
2346 .sp
2347 A character that is valid by the RFC 2279 rules is either 5 or 6 bytes long;
2348 these code points are excluded by RFC 3629.
2349 .sp
2350 PCRE_UTF8_ERR13
2351 .sp
2352 A 4-byte character has a value greater than 0x10fff; these code points are
2353 excluded by RFC 3629.
2354 .sp
2355 PCRE_UTF8_ERR14
2356 .sp
2357 A 3-byte character has a value in the range 0xd800 to 0xdfff; this range of
2358 code points are reserved by RFC 3629 for use with UTF-16, and so are excluded
2359 from UTF-8.
2360 .sp
2361 PCRE_UTF8_ERR15
2362 PCRE_UTF8_ERR16
2363 PCRE_UTF8_ERR17
2364 PCRE_UTF8_ERR18
2365 PCRE_UTF8_ERR19
2366 .sp
2367 A 2-, 3-, 4-, 5-, or 6-byte character is "overlong", that is, it codes for a
2368 value that can be represented by fewer bytes, which is invalid. For example,
2369 the two bytes 0xc0, 0xae give the value 0x2e, whose correct coding uses just
2370 one byte.
2371 .sp
2372 PCRE_UTF8_ERR20
2373 .sp
2374 The two most significant bits of the first byte of a character have the binary
2375 value 0b10 (that is, the most significant bit is 1 and the second is 0). Such a
2376 byte can only validly occur as the second or subsequent byte of a multi-byte
2377 character.
2378 .sp
2379 PCRE_UTF8_ERR21
2380 .sp
2381 The first byte of a character has the value 0xfe or 0xff. These values can
2382 never occur in a valid UTF-8 string.
2383 .sp
2384 PCRE_UTF8_ERR22
2385 .sp
2386 This error code was formerly used when the presence of a so-called
2387 "non-character" caused an error. Unicode corrigendum #9 makes it clear that
2388 such characters should not cause a string to be rejected, and so this code is
2389 no longer in use and is never returned.
2390 .
2391 .
2393 .rs
2394 .sp
2395 .nf
2396 .B int pcre_copy_substring(const char *\fIsubject\fP, int *\fIovector\fP,
2397 .B " int \fIstringcount\fP, int \fIstringnumber\fP, char *\fIbuffer\fP,"
2398 .B " int \fIbuffersize\fP);"
2399 .sp
2400 .B int pcre_get_substring(const char *\fIsubject\fP, int *\fIovector\fP,
2401 .B " int \fIstringcount\fP, int \fIstringnumber\fP,"
2402 .B " const char **\fIstringptr\fP);"
2403 .sp
2404 .B int pcre_get_substring_list(const char *\fIsubject\fP,
2405 .B " int *\fIovector\fP, int \fIstringcount\fP, const char ***\fIlistptr\fP);"
2406 .fi
2407 .PP
2408 Captured substrings can be accessed directly by using the offsets returned by
2409 \fBpcre_exec()\fP in \fIovector\fP. For convenience, the functions
2410 \fBpcre_copy_substring()\fP, \fBpcre_get_substring()\fP, and
2411 \fBpcre_get_substring_list()\fP are provided for extracting captured substrings
2412 as new, separate, zero-terminated strings. These functions identify substrings
2413 by number. The next section describes functions for extracting named
2414 substrings.
2415 .P
2416 A substring that contains a binary zero is correctly extracted and has a
2417 further zero added on the end, but the result is not, of course, a C string.
2418 However, you can process such a string by referring to the length that is
2419 returned by \fBpcre_copy_substring()\fP and \fBpcre_get_substring()\fP.
2420 Unfortunately, the interface to \fBpcre_get_substring_list()\fP is not adequate
2421 for handling strings containing binary zeros, because the end of the final
2422 string is not independently indicated.
2423 .P
2424 The first three arguments are the same for all three of these functions:
2425 \fIsubject\fP is the subject string that has just been successfully matched,
2426 \fIovector\fP is a pointer to the vector of integer offsets that was passed to
2427 \fBpcre_exec()\fP, and \fIstringcount\fP is the number of substrings that were
2428 captured by the match, including the substring that matched the entire regular
2429 expression. This is the value returned by \fBpcre_exec()\fP if it is greater
2430 than zero. If \fBpcre_exec()\fP returned zero, indicating that it ran out of
2431 space in \fIovector\fP, the value passed as \fIstringcount\fP should be the
2432 number of elements in the vector divided by three.
2433 .P
2434 The functions \fBpcre_copy_substring()\fP and \fBpcre_get_substring()\fP
2435 extract a single substring, whose number is given as \fIstringnumber\fP. A
2436 value of zero extracts the substring that matched the entire pattern, whereas
2437 higher values extract the captured substrings. For \fBpcre_copy_substring()\fP,
2438 the string is placed in \fIbuffer\fP, whose length is given by
2439 \fIbuffersize\fP, while for \fBpcre_get_substring()\fP a new block of memory is
2440 obtained via \fBpcre_malloc\fP, and its address is returned via
2441 \fIstringptr\fP. The yield of the function is the length of the string, not
2442 including the terminating zero, or one of these error codes:
2443 .sp
2445 .sp
2446 The buffer was too small for \fBpcre_copy_substring()\fP, or the attempt to get
2447 memory failed for \fBpcre_get_substring()\fP.
2448 .sp
2450 .sp
2451 There is no substring whose number is \fIstringnumber\fP.
2452 .P
2453 The \fBpcre_get_substring_list()\fP function extracts all available substrings
2454 and builds a list of pointers to them. All this is done in a single block of
2455 memory that is obtained via \fBpcre_malloc\fP. The address of the memory block
2456 is returned via \fIlistptr\fP, which is also the start of the list of string
2457 pointers. The end of the list is marked by a NULL pointer. The yield of the
2458 function is zero if all went well, or the error code
2459 .sp
2461 .sp
2462 if the attempt to get the memory block failed.
2463 .P
2464 When any of these functions encounter a substring that is unset, which can
2465 happen when capturing subpattern number \fIn+1\fP matches some part of the
2466 subject, but subpattern \fIn\fP has not been used at all, they return an empty
2467 string. This can be distinguished from a genuine zero-length substring by
2468 inspecting the appropriate offset in \fIovector\fP, which is negative for unset
2469 substrings.
2470 .P
2471 The two convenience functions \fBpcre_free_substring()\fP and
2472 \fBpcre_free_substring_list()\fP can be used to free the memory returned by
2473 a previous call of \fBpcre_get_substring()\fP or
2474 \fBpcre_get_substring_list()\fP, respectively. They do nothing more than call
2475 the function pointed to by \fBpcre_free\fP, which of course could be called
2476 directly from a C program. However, PCRE is used in some situations where it is
2477 linked via a special interface to another programming language that cannot use
2478 \fBpcre_free\fP directly; it is for these cases that the functions are
2479 provided.
2480 .
2481 .
2483 .rs
2484 .sp
2485 .nf
2486 .B int pcre_get_stringnumber(const pcre *\fIcode\fP,
2487 .B " const char *\fIname\fP);"
2488 .sp
2489 .B int pcre_copy_named_substring(const pcre *\fIcode\fP,
2490 .B " const char *\fIsubject\fP, int *\fIovector\fP,"
2491 .B " int \fIstringcount\fP, const char *\fIstringname\fP,"
2492 .B " char *\fIbuffer\fP, int \fIbuffersize\fP);"
2493 .sp
2494 .B int pcre_get_named_substring(const pcre *\fIcode\fP,
2495 .B " const char *\fIsubject\fP, int *\fIovector\fP,"
2496 .B " int \fIstringcount\fP, const char *\fIstringname\fP,"
2497 .B " const char **\fIstringptr\fP);"
2498 .fi
2499 .PP
2500 To extract a substring by name, you first have to find associated number.
2501 For example, for this pattern
2502 .sp
2503 (a+)b(?<xxx>\ed+)...
2504 .sp
2505 the number of the subpattern called "xxx" is 2. If the name is known to be
2506 unique (PCRE_DUPNAMES was not set), you can find the number from the name by
2507 calling \fBpcre_get_stringnumber()\fP. The first argument is the compiled
2508 pattern, and the second is the name. The yield of the function is the
2509 subpattern number, or PCRE_ERROR_NOSUBSTRING (-7) if there is no subpattern of
2510 that name.
2511 .P
2512 Given the number, you can extract the substring directly, or use one of the
2513 functions described in the previous section. For convenience, there are also
2514 two functions that do the whole job.
2515 .P
2516 Most of the arguments of \fBpcre_copy_named_substring()\fP and
2517 \fBpcre_get_named_substring()\fP are the same as those for the similarly named
2518 functions that extract by number. As these are described in the previous
2519 section, they are not re-described here. There are just two differences:
2520 .P
2521 First, instead of a substring number, a substring name is given. Second, there
2522 is an extra argument, given at the start, which is a pointer to the compiled
2523 pattern. This is needed in order to gain access to the name-to-number
2524 translation table.
2525 .P
2526 These functions call \fBpcre_get_stringnumber()\fP, and if it succeeds, they
2527 then call \fBpcre_copy_substring()\fP or \fBpcre_get_substring()\fP, as
2528 appropriate. \fBNOTE:\fP If PCRE_DUPNAMES is set and there are duplicate names,
2529 the behaviour may not be what you want (see the next section).
2530 .P
2531 \fBWarning:\fP If the pattern uses the (?| feature to set up multiple
2532 subpatterns with the same number, as described in the
2533 .\" HTML <a href="pcrepattern.html#dupsubpatternnumber">
2534 .\" </a>
2535 section on duplicate subpattern numbers
2536 .\"
2537 in the
2538 .\" HREF
2539 \fBpcrepattern\fP
2540 .\"
2541 page, you cannot use names to distinguish the different subpatterns, because
2542 names are not included in the compiled code. The matching process uses only
2543 numbers. For this reason, the use of different names for subpatterns of the
2544 same number causes an error at compile time.
2545 .
2546 .
2548 .rs
2549 .sp
2550 .nf
2551 .B int pcre_get_stringtable_entries(const pcre *\fIcode\fP,
2552 .B " const char *\fIname\fP, char **\fIfirst\fP, char **\fIlast\fP);"
2553 .fi
2554 .PP
2555 When a pattern is compiled with the PCRE_DUPNAMES option, names for subpatterns
2556 are not required to be unique. (Duplicate names are always allowed for
2557 subpatterns with the same number, created by using the (?| feature. Indeed, if
2558 such subpatterns are named, they are required to use the same names.)
2559 .P
2560 Normally, patterns with duplicate names are such that in any one match, only
2561 one of the named subpatterns participates. An example is shown in the
2562 .\" HREF
2563 \fBpcrepattern\fP
2564 .\"
2565 documentation.
2566 .P
2567 When duplicates are present, \fBpcre_copy_named_substring()\fP and
2568 \fBpcre_get_named_substring()\fP return the first substring corresponding to
2569 the given name that is set. If none are set, PCRE_ERROR_NOSUBSTRING (-7) is
2570 returned; no data is returned. The \fBpcre_get_stringnumber()\fP function
2571 returns one of the numbers that are associated with the name, but it is not
2572 defined which it is.
2573 .P
2574 If you want to get full details of all captured substrings for a given name,
2575 you must use the \fBpcre_get_stringtable_entries()\fP function. The first
2576 argument is the compiled pattern, and the second is the name. The third and
2577 fourth are pointers to variables which are updated by the function. After it
2578 has run, they point to the first and last entries in the name-to-number table
2579 for the given name. The function itself returns the length of each entry, or
2580 PCRE_ERROR_NOSUBSTRING (-7) if there are none. The format of the table is
2581 described above in the section entitled \fIInformation about a pattern\fP
2582 .\" HTML <a href="#infoaboutpattern">
2583 .\" </a>
2584 above.
2585 .\"
2586 Given all the relevant entries for the name, you can extract each of their
2587 numbers, and hence the captured data, if any.
2588 .
2589 .
2591 .rs
2592 .sp
2593 The traditional matching function uses a similar algorithm to Perl, which stops
2594 when it finds the first match, starting at a given point in the subject. If you
2595 want to find all possible matches, or the longest possible match, consider
2596 using the alternative matching function (see below) instead. If you cannot use
2597 the alternative function, but still need to find all possible matches, you
2598 can kludge it up by making use of the callout facility, which is described in
2599 the
2600 .\" HREF
2601 \fBpcrecallout\fP
2602 .\"
2603 documentation.
2604 .P
2605 What you have to do is to insert a callout right at the end of the pattern.
2606 When your callout function is called, extract and save the current matched
2607 substring. Then return 1, which forces \fBpcre_exec()\fP to backtrack and try
2608 other alternatives. Ultimately, when it runs out of matches, \fBpcre_exec()\fP
2609 will yield PCRE_ERROR_NOMATCH.
2610 .
2611 .
2613 .rs
2614 .sp
2615 Matching certain patterns using \fBpcre_exec()\fP can use a lot of process
2616 stack, which in certain environments can be rather limited in size. Some users
2617 find it helpful to have an estimate of the amount of stack that is used by
2618 \fBpcre_exec()\fP, to help them set recursion limits, as described in the
2619 .\" HREF
2620 \fBpcrestack\fP
2621 .\"
2622 documentation. The estimate that is output by \fBpcretest\fP when called with
2623 the \fB-m\fP and \fB-C\fP options is obtained by calling \fBpcre_exec\fP with
2624 the values NULL, NULL, NULL, -999, and -999 for its first five arguments.
2625 .P
2626 Normally, if its first argument is NULL, \fBpcre_exec()\fP immediately returns
2627 the negative error code PCRE_ERROR_NULL, but with this special combination of
2628 arguments, it returns instead a negative number whose absolute value is the
2629 approximate stack frame size in bytes. (A negative number is used so that it is
2630 clear that no match has happened.) The value is approximate because in some
2631 cases, recursive calls to \fBpcre_exec()\fP occur when there are one or two
2632 additional variables on the stack.
2633 .P
2634 If PCRE has been compiled to use the heap instead of the stack for recursion,
2635 the value returned is the size of each block that is obtained from the heap.
2636 .
2637 .
2638 .\" HTML <a name="dfamatch"></a>
2640 .rs
2641 .sp
2642 .nf
2643 .B int pcre_dfa_exec(const pcre *\fIcode\fP, "const pcre_extra *\fIextra\fP,"
2644 .B " const char *\fIsubject\fP, int \fIlength\fP, int \fIstartoffset\fP,"
2645 .B " int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP,"
2646 .B " int *\fIworkspace\fP, int \fIwscount\fP);"
2647 .fi
2648 .P
2649 The function \fBpcre_dfa_exec()\fP is called to match a subject string against
2650 a compiled pattern, using a matching algorithm that scans the subject string
2651 just once, and does not backtrack. This has different characteristics to the
2652 normal algorithm, and is not compatible with Perl. Some of the features of PCRE
2653 patterns are not supported. Nevertheless, there are times when this kind of
2654 matching can be useful. For a discussion of the two matching algorithms, and a
2655 list of features that \fBpcre_dfa_exec()\fP does not support, see the
2656 .\" HREF
2657 \fBpcrematching\fP
2658 .\"
2659 documentation.
2660 .P
2661 The arguments for the \fBpcre_dfa_exec()\fP function are the same as for
2662 \fBpcre_exec()\fP, plus two extras. The \fIovector\fP argument is used in a
2663 different way, and this is described below. The other common arguments are used
2664 in the same way as for \fBpcre_exec()\fP, so their description is not repeated
2665 here.
2666 .P
2667 The two additional arguments provide workspace for the function. The workspace
2668 vector should contain at least 20 elements. It is used for keeping track of
2669 multiple paths through the pattern tree. More workspace will be needed for
2670 patterns and subjects where there are a lot of potential matches.
2671 .P
2672 Here is an example of a simple call to \fBpcre_dfa_exec()\fP:
2673 .sp
2674 int rc;
2675 int ovector[10];
2676 int wspace[20];
2677 rc = pcre_dfa_exec(
2678 re, /* result of pcre_compile() */
2679 NULL, /* we didn't study the pattern */
2680 "some string", /* the subject string */
2681 11, /* the length of the subject string */
2682 0, /* start at offset 0 in the subject */
2683 0, /* default options */
2684 ovector, /* vector of integers for substring information */
2685 10, /* number of elements (NOT size in bytes) */
2686 wspace, /* working space vector */
2687 20); /* number of elements (NOT size in bytes) */
2688 .
2689 .SS "Option bits for \fBpcre_dfa_exec()\fP"
2690 .rs
2691 .sp
2692 The unused bits of the \fIoptions\fP argument for \fBpcre_dfa_exec()\fP must be
2693 zero. The only bits that may be set are PCRE_ANCHORED, PCRE_NEWLINE_\fIxxx\fP,
2697 All but the last four of these are exactly the same as for \fBpcre_exec()\fP,
2698 so their description is not repeated here.
2699 .sp
2702 .sp
2703 These have the same general effect as they do for \fBpcre_exec()\fP, but the
2704 details are slightly different. When PCRE_PARTIAL_HARD is set for
2705 \fBpcre_dfa_exec()\fP, it returns PCRE_ERROR_PARTIAL if the end of the subject
2706 is reached and there is still at least one matching possibility that requires
2707 additional characters. This happens even if some complete matches have also
2708 been found. When PCRE_PARTIAL_SOFT is set, the return code PCRE_ERROR_NOMATCH
2709 is converted into PCRE_ERROR_PARTIAL if the end of the subject is reached,
2710 there have been no complete matches, but there is still at least one matching
2711 possibility. The portion of the string that was inspected when the longest
2712 partial match was found is set as the first matching string in both cases.
2713 There is a more detailed discussion of partial and multi-segment matching, with
2714 examples, in the
2715 .\" HREF
2716 \fBpcrepartial\fP
2717 .\"
2718 documentation.
2719 .sp
2721 .sp
2722 Setting the PCRE_DFA_SHORTEST option causes the matching algorithm to stop as
2723 soon as it has found one match. Because of the way the alternative algorithm
2724 works, this is necessarily the shortest possible match at the first possible
2725 matching point in the subject string.
2726 .sp
2728 .sp
2729 When \fBpcre_dfa_exec()\fP returns a partial match, it is possible to call it
2730 again, with additional subject characters, and have it continue with the same
2731 match. The PCRE_DFA_RESTART option requests this action; when it is set, the
2732 \fIworkspace\fP and \fIwscount\fP options must reference the same vector as
2733 before because data about the match so far is left in them after a partial
2734 match. There is more discussion of this facility in the
2735 .\" HREF
2736 \fBpcrepartial\fP
2737 .\"
2738 documentation.
2739 .
2740 .
2741 .SS "Successful returns from \fBpcre_dfa_exec()\fP"
2742 .rs
2743 .sp
2744 When \fBpcre_dfa_exec()\fP succeeds, it may have matched more than one
2745 substring in the subject. Note, however, that all the matches from one run of
2746 the function start at the same point in the subject. The shorter matches are
2747 all initial substrings of the longer matches. For example, if the pattern
2748 .sp
2749 <.*>
2750 .sp
2751 is matched against the string
2752 .sp
2753 This is <something> <something else> <something further> no more
2754 .sp
2755 the three matched strings are
2756 .sp
2757 <something>
2758 <something> <something else>
2759 <something> <something else> <something further>
2760 .sp
2761 On success, the yield of the function is a number greater than zero, which is
2762 the number of matched substrings. The substrings themselves are returned in
2763 \fIovector\fP. Each string uses two elements; the first is the offset to the
2764 start, and the second is the offset to the end. In fact, all the strings have
2765 the same start offset. (Space could have been saved by giving this only once,
2766 but it was decided to retain some compatibility with the way \fBpcre_exec()\fP
2767 returns data, even though the meaning of the strings is different.)
2768 .P
2769 The strings are returned in reverse order of length; that is, the longest
2770 matching string is given first. If there were too many matches to fit into
2771 \fIovector\fP, the yield of the function is zero, and the vector is filled with
2772 the longest matches. Unlike \fBpcre_exec()\fP, \fBpcre_dfa_exec()\fP can use
2773 the entire \fIovector\fP for returning matched strings.
2774 .
2775 .
2776 .SS "Error returns from \fBpcre_dfa_exec()\fP"
2777 .rs
2778 .sp
2779 The \fBpcre_dfa_exec()\fP function returns a negative number when it fails.
2780 Many of the errors are the same as for \fBpcre_exec()\fP, and these are
2781 described
2782 .\" HTML <a href="#errorlist">
2783 .\" </a>
2784 above.
2785 .\"
2786 There are in addition the following errors that are specific to
2787 \fBpcre_dfa_exec()\fP:
2788 .sp
2790 .sp
2791 This return is given if \fBpcre_dfa_exec()\fP encounters an item in the pattern
2792 that it does not support, for instance, the use of \eC or a back reference.
2793 .sp
2795 .sp
2796 This return is given if \fBpcre_dfa_exec()\fP encounters a condition item that
2797 uses a back reference for the condition, or a test for recursion in a specific
2798 group. These are not supported.
2799 .sp
2801 .sp
2802 This return is given if \fBpcre_dfa_exec()\fP is called with an \fIextra\fP
2803 block that contains a setting of the \fImatch_limit\fP or
2804 \fImatch_limit_recursion\fP fields. This is not supported (these fields are
2805 meaningless for DFA matching).
2806 .sp
2808 .sp
2809 This return is given if \fBpcre_dfa_exec()\fP runs out of space in the
2810 \fIworkspace\fP vector.
2811 .sp
2813 .sp
2814 When a recursive subpattern is processed, the matching function calls itself
2815 recursively, using private vectors for \fIovector\fP and \fIworkspace\fP. This
2816 error is given if the output vector is not large enough. This should be
2817 extremely rare, as a vector of size 1000 is used.
2818 .sp
2820 .sp
2821 When \fBpcre_dfa_exec()\fP is called with the \fBPCRE_DFA_RESTART\fP option,
2822 some plausibility checks are made on the contents of the workspace, which
2823 should contain data about the previous partial match. If any of these checks
2824 fail, this error is given.
2825 .
2826 .
2827 .SH "SEE ALSO"
2828 .rs
2829 .sp
2830 \fBpcre16\fP(3), \fBpcre32\fP(3), \fBpcrebuild\fP(3), \fBpcrecallout\fP(3),
2831 \fBpcrecpp(3)\fP(3), \fBpcrematching\fP(3), \fBpcrepartial\fP(3),
2832 \fBpcreposix\fP(3), \fBpcreprecompile\fP(3), \fBpcresample\fP(3),
2833 \fBpcrestack\fP(3).
2834 .
2835 .
2837 .rs
2838 .sp
2839 .nf
2840 Philip Hazel
2841 University Computing Service
2842 Cambridge CB2 3QH, England.
2843 .fi
2844 .
2845 .
2847 .rs
2848 .sp
2849 .nf
2850 Last updated: 05 July 2013
2851 Copyright (c) 1997-2013 University of Cambridge.
2852 .fi


Name Value
svn:eol-style native
svn:keywords "Author Date Id Revision Url"

  ViewVC Help
Powered by ViewVC 1.1.5