/[pcre]/code/trunk/doc/pcreapi.3
ViewVC logotype

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1055 - (show annotations)
Tue Oct 16 15:53:30 2012 UTC (6 years, 8 months ago) by chpe
File size: 118617 byte(s)
pcre32: Add 32-bit library

Create libpcre32 that operates on 32-bit characters (UTF-32).

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

Properties

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

  ViewVC Help
Powered by ViewVC 1.1.5