embedaddon/pcre/doc/pcreapi.3 - diff

Return to pcreapi.3 CVS log

Up to [ELWIX - Embedded LightWeight unIX -] / embedaddon / pcre / doc

Diff for /embedaddon/pcre/doc/pcreapi.3 between versions 1.1 and 1.1.1.5

version 1.1, 2012/02/21 23:05:51	version 1.1.1.5, 2014/06/15 19:46:05
Line 1	Line 1
.TH PCREAPI 3	.TH PCREAPI 3 "12 November 2013" "PCRE 8.34"
.SH NAME	.SH NAME
PCRE - Perl-compatible regular expressions	PCRE - Perl-compatible regular expressions
	.sp
	.B #include <pcre.h>
	.
	.
.SH "PCRE NATIVE API BASIC FUNCTIONS"	.SH "PCRE NATIVE API BASIC FUNCTIONS"
.rs	.rs
.sp	.sp
.B #include <pcre.h>	.nf
.PP
.SM
.B pcre pcre_compile(const char \fIpattern\fP, int \fIoptions\fP,	.B pcre pcre_compile(const char \fIpattern\fP, int \fIoptions\fP,
.ti +5n	.B " const char *\fIerrptr\fP, int \fIerroffset\fP,"
.B const char *\fIerrptr\fP, int \fIerroffset\fP,	.B " const unsigned char *\fItableptr\fP);"
.ti +5n	.sp
.B const unsigned char *\fItableptr\fP);
.PP
.B pcre pcre_compile2(const char \fIpattern\fP, int \fIoptions\fP,	.B pcre pcre_compile2(const char \fIpattern\fP, int \fIoptions\fP,
.ti +5n	.B " int *\fIerrorcodeptr\fP,"
.B int *\fIerrorcodeptr\fP,	.B " const char *\fIerrptr\fP, int \fIerroffset\fP,"
.ti +5n	.B " const unsigned char *\fItableptr\fP);"
.B const char *\fIerrptr\fP, int \fIerroffset\fP,	.sp
.ti +5n
.B const unsigned char *\fItableptr\fP);
.PP
.B pcre_extra pcre_study(const pcre \fIcode\fP, int \fIoptions\fP,	.B pcre_extra pcre_study(const pcre \fIcode\fP, int \fIoptions\fP,
.ti +5n	.B " const char **\fIerrptr\fP);"
.B const char **\fIerrptr\fP);	.B void pcre_free_study(pcre_extra *\fIextra\fP);
.PP
.B void pcre_free_study(pcre_extra *\fIextra\fP);	.B void pcre_free_study(pcre_extra *\fIextra\fP);
.PP	.sp
.B int pcre_exec(const pcre \fIcode\fP, "const pcre_extra \fIextra\fP,"	.B int pcre_exec(const pcre \fIcode\fP, "const pcre_extra \fIextra\fP,"
.ti +5n	.B " const char *\fIsubject\fP, int \fIlength\fP, int \fIstartoffset\fP,"
.B "const char *\fIsubject\fP," int \fIlength\fP, int \fIstartoffset\fP,	.B " int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP);"
.ti +5n	.sp
.B int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP);	.B int pcre_dfa_exec(const pcre \fIcode\fP, "const pcre_extra \fIextra\fP,"
	.B " const char *\fIsubject\fP, int \fIlength\fP, int \fIstartoffset\fP,"
	.B " int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP,"
	.B " int *\fIworkspace\fP, int \fIwscount\fP);"
	.fi
.	.
.	.
.SH "PCRE NATIVE API AUXILIARY FUNCTIONS"	.SH "PCRE NATIVE API STRING EXTRACTION FUNCTIONS"
.rs	.rs
.sp	.sp
.B pcre_jit_stack *pcre_jit_stack_alloc(int \fIstartsize\fP, int \fImaxsize\fP);	.nf
.PP
.B void pcre_jit_stack_free(pcre_jit_stack *\fIstack\fP);
.PP
.B void pcre_assign_jit_stack(pcre_extra *\fIextra\fP,
.ti +5n
.B pcre_jit_callback \fIcallback\fP, void *\fIdata\fP);
.PP
.B int pcre_dfa_exec(const pcre \fIcode\fP, "const pcre_extra \fIextra\fP,"
.ti +5n
.B "const char *\fIsubject\fP," int \fIlength\fP, int \fIstartoffset\fP,
.ti +5n
.B int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP,
.ti +5n
.B int *\fIworkspace\fP, int \fIwscount\fP);
.PP
.B int pcre_copy_named_substring(const pcre *\fIcode\fP,	.B int pcre_copy_named_substring(const pcre *\fIcode\fP,
.ti +5n	.B " const char \fIsubject\fP, int \fIovector\fP,"
.B const char \fIsubject\fP, int \fIovector\fP,	.B " int \fIstringcount\fP, const char *\fIstringname\fP,"
.ti +5n	.B " char *\fIbuffer\fP, int \fIbuffersize\fP);"
.B int \fIstringcount\fP, const char *\fIstringname\fP,	.sp
.ti +5n
.B char *\fIbuffer\fP, int \fIbuffersize\fP);
.PP
.B int pcre_copy_substring(const char \fIsubject\fP, int \fIovector\fP,	.B int pcre_copy_substring(const char \fIsubject\fP, int \fIovector\fP,
.ti +5n	.B " int \fIstringcount\fP, int \fIstringnumber\fP, char *\fIbuffer\fP,"
.B int \fIstringcount\fP, int \fIstringnumber\fP, char *\fIbuffer\fP,	.B " int \fIbuffersize\fP);"
.ti +5n	.sp
.B int \fIbuffersize\fP);
.PP
.B int pcre_get_named_substring(const pcre *\fIcode\fP,	.B int pcre_get_named_substring(const pcre *\fIcode\fP,
.ti +5n	.B " const char \fIsubject\fP, int \fIovector\fP,"
.B const char \fIsubject\fP, int \fIovector\fP,	.B " int \fIstringcount\fP, const char *\fIstringname\fP,"
.ti +5n	.B " const char **\fIstringptr\fP);"
.B int \fIstringcount\fP, const char *\fIstringname\fP,	.sp
.ti +5n
.B const char **\fIstringptr\fP);
.PP
.B int pcre_get_stringnumber(const pcre *\fIcode\fP,	.B int pcre_get_stringnumber(const pcre *\fIcode\fP,
.ti +5n	.B " const char *\fIname\fP);"
.B const char *\fIname\fP);	.B int pcre_get_stringtable_entries(const pcre *\fIcode\fP,
.PP
.B int pcre_get_stringtable_entries(const pcre *\fIcode\fP,	.B int pcre_get_stringtable_entries(const pcre *\fIcode\fP,
.ti +5n	.B " const char \fIname\fP, char \fIfirst\fP, char *\fIlast\fP);"
.B const char \fIname\fP, char \fIfirst\fP, char *\fIlast\fP);	.B int pcre_get_substring(const char \fIsubject\fP, int \fIovector\fP,
.PP
.B int pcre_get_substring(const char \fIsubject\fP, int \fIovector\fP,	.B int pcre_get_substring(const char \fIsubject\fP, int \fIovector\fP,
.ti +5n	.B " int \fIstringcount\fP, int \fIstringnumber\fP,"
.B int \fIstringcount\fP, int \fIstringnumber\fP,	.B " const char **\fIstringptr\fP);"
.ti +5n	.sp
.B const char **\fIstringptr\fP);
.PP
.B int pcre_get_substring_list(const char *\fIsubject\fP,	.B int pcre_get_substring_list(const char *\fIsubject\fP,
.ti +5n	.B " int \fIovector\fP, int \fIstringcount\fP, const char **\fIlistptr\fP);"
.B int \fIovector\fP, int \fIstringcount\fP, "const char **\fIlistptr\fP);"	.B void pcre_free_substring(const char *\fIstringptr\fP);
.PP
.B void pcre_free_substring(const char *\fIstringptr\fP);	.B void pcre_free_substring(const char *\fIstringptr\fP);
.PP	.sp
.B void pcre_free_substring_list(const char **\fIstringptr\fP);	.B void pcre_free_substring_list(const char **\fIstringptr\fP);
.PP	.fi
	.
	.
	.SH "PCRE NATIVE API AUXILIARY FUNCTIONS"
	.rs
	.sp
	.nf
	.B int pcre_jit_exec(const pcre \fIcode\fP, "const pcre_extra \fIextra\fP,"
	.B " const char *\fIsubject\fP, int \fIlength\fP, int \fIstartoffset\fP,"
	.B " int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP,"
	.B " pcre_jit_stack *\fIjstack\fP);"
	.sp
	.B pcre_jit_stack *pcre_jit_stack_alloc(int \fIstartsize\fP, int \fImaxsize\fP);
	.sp
	.B void pcre_jit_stack_free(pcre_jit_stack *\fIstack\fP);
	.sp
	.B void pcre_assign_jit_stack(pcre_extra *\fIextra\fP,
	.B " pcre_jit_callback \fIcallback\fP, void *\fIdata\fP);"
	.sp
.B const unsigned char *pcre_maketables(void);	.B const unsigned char *pcre_maketables(void);
.PP	.sp
.B int pcre_fullinfo(const pcre \fIcode\fP, "const pcre_extra \fIextra\fP,"	.B int pcre_fullinfo(const pcre \fIcode\fP, "const pcre_extra \fIextra\fP,"
.ti +5n	.B " int \fIwhat\fP, void *\fIwhere\fP);"
.B int \fIwhat\fP, void *\fIwhere\fP);	.B int pcre_refcount(pcre *\fIcode\fP, int \fIadjust\fP);
.PP
.B int pcre_info(const pcre \fIcode\fP, int \fIoptptr\fP, int
.B *\fIfirstcharptr\fP);
.PP
.B int pcre_refcount(pcre *\fIcode\fP, int \fIadjust\fP);	.B int pcre_refcount(pcre *\fIcode\fP, int \fIadjust\fP);
.PP	.sp
.B int pcre_config(int \fIwhat\fP, void *\fIwhere\fP);	.B int pcre_config(int \fIwhat\fP, void *\fIwhere\fP);
.PP	.sp
.B char *pcre_version(void);	.B const char *pcre_version(void);
	.sp
	.B int pcre_pattern_to_host_byte_order(pcre *\fIcode\fP,
	.B " pcre_extra \fIextra\fP, const unsigned char \fItables\fP);"
	.fi
.	.
.	.
.SH "PCRE NATIVE API INDIRECTED FUNCTIONS"	.SH "PCRE NATIVE API INDIRECTED FUNCTIONS"
.rs	.rs
.sp	.sp
	.nf
.B void (pcre_malloc)(size_t);	.B void (pcre_malloc)(size_t);
.PP	.sp
.B void (pcre_free)(void );	.B void (pcre_free)(void );
.PP	.sp
.B void (pcre_stack_malloc)(size_t);	.B void (pcre_stack_malloc)(size_t);
.PP	.sp
.B void (pcre_stack_free)(void );	.B void (pcre_stack_free)(void );
.PP	.sp
.B int (pcre_callout)(pcre_callout_block );	.B int (pcre_callout)(pcre_callout_block );
	.fi
.	.
.	.
	.SH "PCRE 8-BIT, 16-BIT, AND 32-BIT LIBRARIES"
	.rs
	.sp
	As well as support for 8-bit character strings, PCRE also supports 16-bit
	strings (from release 8.30) and 32-bit strings (from release 8.32), by means of
	two additional libraries. They can be built as well as, or instead of, the
	8-bit library. To avoid too much complication, this document describes the
	8-bit versions of the functions, with only occasional references to the 16-bit
	and 32-bit libraries.
	.P
	The 16-bit and 32-bit functions operate in the same way as their 8-bit
	counterparts; they just use different data types for their arguments and
	results, and their names start with \fBpcre16_\fP or \fBpcre32_\fP instead of
	\fBpcre_\fP. For every option that has UTF8 in its name (for example,
	PCRE_UTF8), there are corresponding 16-bit and 32-bit names with UTF8 replaced
	by UTF16 or UTF32, respectively. This facility is in fact just cosmetic; the
	16-bit and 32-bit option names define the same bit values.
	.P
	References to bytes and UTF-8 in this document should be read as references to
	16-bit data units and UTF-16 when using the 16-bit library, or 32-bit data
	units and UTF-32 when using the 32-bit library, unless specified otherwise.
	More details of the specific differences for the 16-bit and 32-bit libraries
	are given in the
	.\" HREF
	\fBpcre16\fP
	.\"
	and
	.\" HREF
	\fBpcre32\fP
	.\"
	pages.
	.
	.
.SH "PCRE API OVERVIEW"	.SH "PCRE API OVERVIEW"
.rs	.rs
.sp	.sp
PCRE has its own native API, which is described in this document. There are	PCRE has its own native API, which is described in this document. There are
also some wrapper functions that correspond to the POSIX regular expression	also some wrapper functions (for the 8-bit library only) that correspond to the
API, but they do not give access to all the functionality. They are described	POSIX regular expression API, but they do not give access to all the
in the	functionality. They are described in the
.\" HREF	.\" HREF
\fBpcreposix\fP	\fBpcreposix\fP
.\"	.\"
documentation. Both of these APIs define a set of C function calls. A C++	documentation. Both of these APIs define a set of C function calls. A C++
wrapper is also distributed with PCRE. It is documented in the	wrapper (again for the 8-bit library only) is also distributed with PCRE. It is
	documented in the
.\" HREF	.\" HREF
\fBpcrecpp\fP	\fBpcrecpp\fP
.\"	.\"
page.	page.
.P	.P
The native API C function prototypes are defined in the header file	The native API C function prototypes are defined in the header file
\fBpcre.h\fP, and on Unix systems the library itself is called \fBlibpcre\fP.	\fBpcre.h\fP, and on Unix-like systems the (8-bit) library itself is called
It can normally be accessed by adding \fB-lpcre\fP to the command for linking	\fBlibpcre\fP. It can normally be accessed by adding \fB-lpcre\fP to the
an application that uses PCRE. The header file defines the macros PCRE_MAJOR	command for linking an application that uses PCRE. The header file defines the
and PCRE_MINOR to contain the major and minor release numbers for the library.	macros PCRE_MAJOR and PCRE_MINOR to contain the major and minor release numbers
Applications can use these to include support for different releases of PCRE.	for the library. Applications can use these to include support for different
	releases of PCRE.
.P	.P
In a Windows environment, if you want to statically link an application program	In a Windows environment, if you want to statically link an application program
against a non-dll \fBpcre.a\fP file, you must define PCRE_STATIC before	against a non-dll \fBpcre.a\fP file, you must define PCRE_STATIC before
Line 178 used if available, by setting an option that is ignore	Line 205 used if available, by setting an option that is ignore
relevant. More complicated programs might need to make use of the functions	relevant. More complicated programs might need to make use of the functions
\fBpcre_jit_stack_alloc()\fP, \fBpcre_jit_stack_free()\fP, and	\fBpcre_jit_stack_alloc()\fP, \fBpcre_jit_stack_free()\fP, and
\fBpcre_assign_jit_stack()\fP in order to control the JIT code's memory usage.	\fBpcre_assign_jit_stack()\fP in order to control the JIT code's memory usage.
These functions are discussed in the	.P
	From release 8.32 there is also a direct interface for JIT execution, which
	gives improved performance. The JIT-specific functions are discussed in the
.\" HREF	.\" HREF
\fBpcrejit\fP	\fBpcrejit\fP
.\"	.\"
Line 218 specialist use. Most commonly, no special tables are p	Line 247 specialist use. Most commonly, no special tables are p
internal tables that are generated when PCRE is built are used.	internal tables that are generated when PCRE is built are used.
.P	.P
The function \fBpcre_fullinfo()\fP is used to find out information about a	The function \fBpcre_fullinfo()\fP is used to find out information about a
compiled pattern; \fBpcre_info()\fP is an obsolete version that returns only	compiled pattern. The function \fBpcre_version()\fP returns a pointer to a
some of the available information, but is retained for backwards compatibility.	string containing the version of PCRE and its date of release.
The function \fBpcre_version()\fP returns a pointer to a string containing the
version of PCRE and its date of release.
.P	.P
The function \fBpcre_refcount()\fP maintains a reference count in a data block	The function \fBpcre_refcount()\fP maintains a reference count in a data block
containing a compiled pattern. This is provided for the benefit of	containing a compiled pattern. This is provided for the benefit of
Line 269 PCRE supports five different conventions for indicatin	Line 296 PCRE supports five different conventions for indicatin
strings: a single CR (carriage return) character, a single LF (linefeed)	strings: a single CR (carriage return) character, a single LF (linefeed)
character, the two-character sequence CRLF, any of the three preceding, or any	character, the two-character sequence CRLF, any of the three preceding, or any
Unicode newline sequence. The Unicode newline sequences are the three just	Unicode newline sequence. The Unicode newline sequences are the three just
mentioned, plus the single characters VT (vertical tab, U+000B), FF (formfeed,	mentioned, plus the single characters VT (vertical tab, U+000B), FF (form feed,
U+000C), NEL (next line, U+0085), LS (line separator, U+2028), and PS	U+000C), NEL (next line, U+0085), LS (line separator, U+2028), and PS
(paragraph separator, U+2029).	(paragraph separator, U+2029).
.P	.P
Line 332 which it was compiled. Details are given in the	Line 359 which it was compiled. Details are given in the
.\" HREF	.\" HREF
\fBpcreprecompile\fP	\fBpcreprecompile\fP
.\"	.\"
documentation. However, compiling a regular expression with one version of PCRE	documentation, which includes a description of the
for use with a different version is not guaranteed to work and may cause	\fBpcre_pattern_to_host_byte_order()\fP function. However, compiling a regular
crashes.	expression with one version of PCRE for use with a different version is not
	guaranteed to work and may cause crashes.
.	.
.	.
.SH "CHECKING BUILD-TIME OPTIONS"	.SH "CHECKING BUILD-TIME OPTIONS"
Line 351 documentation has more details about these optional fe	Line 379 documentation has more details about these optional fe
.P	.P
The first argument for \fBpcre_config()\fP is an integer, specifying which	The first argument for \fBpcre_config()\fP is an integer, specifying which
information is required; the second argument is a pointer to a variable into	information is required; the second argument is a pointer to a variable into
which the information is placed. The following information is available:	which the information is placed. The returned value is zero on success, or the
	negative error code PCRE_ERROR_BADOPTION if the value in the first argument is
	not recognized. The following information is available:
.sp	.sp
PCRE_CONFIG_UTF8	PCRE_CONFIG_UTF8
.sp	.sp
The output is an integer that is set to one if UTF-8 support is available;	The output is an integer that is set to one if UTF-8 support is available;
otherwise it is set to zero.	otherwise it is set to zero. This value should normally be given to the 8-bit
	version of this function, \fBpcre_config()\fP. If it is given to the 16-bit
	or 32-bit version of this function, the result is PCRE_ERROR_BADOPTION.
.sp	.sp
	PCRE_CONFIG_UTF16
	.sp
	The output is an integer that is set to one if UTF-16 support is available;
	otherwise it is set to zero. This value should normally be given to the 16-bit
	version of this function, \fBpcre16_config()\fP. If it is given to the 8-bit
	or 32-bit version of this function, the result is PCRE_ERROR_BADOPTION.
	.sp
	PCRE_CONFIG_UTF32
	.sp
	The output is an integer that is set to one if UTF-32 support is available;
	otherwise it is set to zero. This value should normally be given to the 32-bit
	version of this function, \fBpcre32_config()\fP. If it is given to the 8-bit
	or 16-bit version of this function, the result is PCRE_ERROR_BADOPTION.
	.sp
PCRE_CONFIG_UNICODE_PROPERTIES	PCRE_CONFIG_UNICODE_PROPERTIES
.sp	.sp
The output is an integer that is set to one if support for Unicode character	The output is an integer that is set to one if support for Unicode character
Line 368 properties is available; otherwise it is set to zero.	Line 414 properties is available; otherwise it is set to zero.
The output is an integer that is set to one if support for just-in-time	The output is an integer that is set to one if support for just-in-time
compiling is available; otherwise it is set to zero.	compiling is available; otherwise it is set to zero.
.sp	.sp
	PCRE_CONFIG_JITTARGET
	.sp
	The output is a pointer to a zero-terminated "const char *" string. If JIT
	support is available, the string contains the name of the architecture for
	which the JIT compiler is configured, for example "x86 32bit (little endian +
	unaligned)". If JIT support is not available, the result is NULL.
	.sp
PCRE_CONFIG_NEWLINE	PCRE_CONFIG_NEWLINE
.sp	.sp
The output is an integer whose value specifies the default character sequence	The output is an integer whose value specifies the default character sequence
that is recognized as meaning "newline". The four values that are supported	that is recognized as meaning "newline". The values that are supported in
are: 10 for LF, 13 for CR, 3338 for CRLF, -2 for ANYCRLF, and -1 for ANY.	ASCII/Unicode environments are: 10 for LF, 13 for CR, 3338 for CRLF, -2 for
Though they are derived from ASCII, the same values are returned in EBCDIC	ANYCRLF, and -1 for ANY. In EBCDIC environments, CR, ANYCRLF, and ANY yield the
environments. The default should normally correspond to the standard sequence	same values. However, the value for LF is normally 21, though some EBCDIC
for your operating system.	environments use 37. The corresponding values for CRLF are 3349 and 3365. The
	default should normally correspond to the standard sequence for your operating
	system.
.sp	.sp
PCRE_CONFIG_BSR	PCRE_CONFIG_BSR
.sp	.sp
Line 387 or CRLF. The default can be overridden when a pattern	Line 442 or CRLF. The default can be overridden when a pattern
PCRE_CONFIG_LINK_SIZE	PCRE_CONFIG_LINK_SIZE
.sp	.sp
The output is an integer that contains the number of bytes used for internal	The output is an integer that contains the number of bytes used for internal
linkage in compiled regular expressions. The value is 2, 3, or 4. Larger values	linkage in compiled regular expressions. For the 8-bit library, the value can
allow larger regular expressions to be compiled, at the expense of slower	be 2, 3, or 4. For the 16-bit library, the value is either 2 or 4 and is still
matching. The default value of 2 is sufficient for all but the most massive	a number of bytes. For the 32-bit library, the value is either 2 or 4 and is
patterns, since it allows the compiled pattern to be up to 64K in size.	still a number of bytes. The default value of 2 is sufficient for all but the
	most massive patterns, since it allows the compiled pattern to be up to 64K in
	size. Larger values allow larger regular expressions to be compiled, at the
	expense of slower matching.
.sp	.sp
PCRE_CONFIG_POSIX_MALLOC_THRESHOLD	PCRE_CONFIG_POSIX_MALLOC_THRESHOLD
.sp	.sp
Line 402 the	Line 460 the
.\"	.\"
documentation.	documentation.
.sp	.sp
	PCRE_CONFIG_PARENS_LIMIT
	.sp
	The output is a long integer that gives the maximum depth of nesting of
	parentheses (of any kind) in a pattern. This limit is imposed to cap the amount
	of system stack used when a pattern is compiled. It is specified when PCRE is
	built; the default is 250.
	.sp
PCRE_CONFIG_MATCH_LIMIT	PCRE_CONFIG_MATCH_LIMIT
.sp	.sp
The output is a long integer that gives the default limit for the number of	The output is a long integer that gives the default limit for the number of
Line 428 avoiding the use of the stack.	Line 493 avoiding the use of the stack.
.SH "COMPILING A PATTERN"	.SH "COMPILING A PATTERN"
.rs	.rs
.sp	.sp
	.nf
.B pcre pcre_compile(const char \fIpattern\fP, int \fIoptions\fP,	.B pcre pcre_compile(const char \fIpattern\fP, int \fIoptions\fP,
.ti +5n	.B " const char *\fIerrptr\fP, int \fIerroffset\fP,"
.B const char *\fIerrptr\fP, int \fIerroffset\fP,	.B " const unsigned char *\fItableptr\fP);"
.ti +5n
.B const unsigned char *\fItableptr\fP);
.sp	.sp
.B pcre pcre_compile2(const char \fIpattern\fP, int \fIoptions\fP,	.B pcre pcre_compile2(const char \fIpattern\fP, int \fIoptions\fP,
.ti +5n	.B " int *\fIerrorcodeptr\fP,"
.B int *\fIerrorcodeptr\fP,	.B " const char *\fIerrptr\fP, int \fIerroffset\fP,"
.ti +5n	.B " const unsigned char *\fItableptr\fP);"
.B const char *\fIerrptr\fP, int \fIerroffset\fP,	.fi
.ti +5n
.B const unsigned char *\fItableptr\fP);
.P	.P
Either of the functions \fBpcre_compile()\fP or \fBpcre_compile2()\fP can be	Either of the functions \fBpcre_compile()\fP or \fBpcre_compile2()\fP can be
called to compile a pattern into an internal form. The only difference between	called to compile a pattern into an internal form. The only difference between
Line 473 documentation). For those options that can be differen	Line 535 documentation). For those options that can be differen
the pattern, the contents of the \fIoptions\fP argument specifies their	the pattern, the contents of the \fIoptions\fP argument specifies their
settings at the start of compilation and execution. The PCRE_ANCHORED,	settings at the start of compilation and execution. The PCRE_ANCHORED,
PCRE_BSR_\fIxxx\fP, PCRE_NEWLINE_\fIxxx\fP, PCRE_NO_UTF8_CHECK, and	PCRE_BSR_\fIxxx\fP, PCRE_NEWLINE_\fIxxx\fP, PCRE_NO_UTF8_CHECK, and
PCRE_NO_START_OPT options can be set at the time of matching as well as at	PCRE_NO_START_OPTIMIZE options can be set at the time of matching as well as at
compile time.	compile time.
.P	.P
If \fIerrptr\fP is NULL, \fBpcre_compile()\fP returns NULL immediately.	If \fIerrptr\fP is NULL, \fBpcre_compile()\fP returns NULL immediately.
Line 481 Otherwise, if compilation of a pattern fails, \fBpcre_	Line 543 Otherwise, if compilation of a pattern fails, \fBpcre_
NULL, and sets the variable pointed to by \fIerrptr\fP to point to a textual	NULL, and sets the variable pointed to by \fIerrptr\fP to point to a textual
error message. This is a static string that is part of the library. You must	error message. This is a static string that is part of the library. You must
not try to free it. Normally, the offset from the start of the pattern to the	not try to free it. Normally, the offset from the start of the pattern to the
byte that was being processed when the error was discovered is placed in the	data unit that was being processed when the error was discovered is placed in
variable pointed to by \fIerroffset\fP, which must not be NULL (if it is, an	the variable pointed to by \fIerroffset\fP, which must not be NULL (if it is,
immediate error is given). However, for an invalid UTF-8 string, the offset is	an immediate error is given). However, for an invalid UTF-8 or UTF-16 string,
that of the first byte of the failing character. Also, some errors are not	the offset is that of the first data unit of the failing character.
detected until checks are carried out when the whole pattern has been scanned;
in these cases the offset passed back is the length of the pattern.
.P	.P
Note that the offset is in bytes, not characters, even in UTF-8 mode. It may	Some errors are not detected until the whole pattern has been scanned; in these
sometimes point into the middle of a UTF-8 character.	cases, the offset passed back is the length of the pattern. Note that the
	offset is in data units, not characters, even in a UTF mode. It may sometimes
	point into the middle of a UTF-8 or UTF-16 character.
.P	.P
If \fBpcre_compile2()\fP is used instead of \fBpcre_compile()\fP, and the	If \fBpcre_compile2()\fP is used instead of \fBpcre_compile()\fP, and the
\fIerrorcodeptr\fP argument is not NULL, a non-zero error code number is	\fIerrorcodeptr\fP argument is not NULL, a non-zero error code number is
Line 500 If the final argument, \fItableptr\fP, is NULL, PCRE u	Line 562 If the final argument, \fItableptr\fP, is NULL, PCRE u
character tables that are built when PCRE is compiled, using the default C	character tables that are built when PCRE is compiled, using the default C
locale. Otherwise, \fItableptr\fP must be an address that is the result of a	locale. Otherwise, \fItableptr\fP must be an address that is the result of a
call to \fBpcre_maketables()\fP. This value is stored with the compiled	call to \fBpcre_maketables()\fP. This value is stored with the compiled
pattern, and used again by \fBpcre_exec()\fP, unless another table pointer is	pattern, and used again by \fBpcre_exec()\fP and \fBpcre_dfa_exec()\fP when the
passed to it. For more discussion, see the section on locale support below.	pattern is matched. For more discussion, see the section on locale support
	below.
.P	.P
This code fragment shows a typical straightforward call to \fBpcre_compile()\fP:	This code fragment shows a typical straightforward call to \fBpcre_compile()\fP:
.sp	.sp
Line 589 documentation.	Line 652 documentation.
.sp	.sp
PCRE_EXTENDED	PCRE_EXTENDED
.sp	.sp
If this bit is set, whitespace data characters in the pattern are totally	If this bit is set, most white space characters in the pattern are totally
ignored except when escaped or inside a character class. Whitespace does not	ignored except when escaped or inside a character class. However, white space
include the VT character (code 11). In addition, characters between an	is not allowed within sequences such as (?> that introduce various
unescaped # outside a character class and the next newline, inclusive, are also	parenthesized subpatterns, nor within a numerical quantifier such as {1,3}.
ignored. This is equivalent to Perl's /x option, and it can be changed within a	However, ignorable white space is permitted between an item and a following
pattern by a (?x) option setting.	quantifier and between a quantifier and a following + that indicates
	possessiveness.
.P	.P
	White space did not used to include the VT character (code 11), because Perl
	did not treat this character as white space. However, Perl changed at release
	5.18, so PCRE followed at release 8.34, and VT is now treated as white space.
	.P
	PCRE_EXTENDED also causes characters between an unescaped # outside a character
	class and the next newline, inclusive, to be ignored. PCRE_EXTENDED is
	equivalent to Perl's /x option, and it can be changed within a pattern by a
	(?x) option setting.
	.P
Which characters are interpreted as newlines is controlled by the options	Which characters are interpreted as newlines is controlled by the options
passed to \fBpcre_compile()\fP or by a special sequence at the start of the	passed to \fBpcre_compile()\fP or by a special sequence at the start of the
pattern, as described in the section entitled	pattern, as described in the section entitled
Line 608 comment is a literal newline sequence in the pattern;	Line 681 comment is a literal newline sequence in the pattern;
happen to represent a newline do not count.	happen to represent a newline do not count.
.P	.P
This option makes it possible to include comments inside complicated patterns.	This option makes it possible to include comments inside complicated patterns.
Note, however, that this applies only to data characters. Whitespace characters	Note, however, that this applies only to data characters. White space characters
may never appear within special character sequences in a pattern, for example	may never appear within special character sequences in a pattern, for example
within the sequence (?( that introduces a conditional subpattern.	within the sequence (?( that introduces a conditional subpattern.
.sp	.sp
Line 660 binary zero character followed by z).	Line 733 binary zero character followed by z).
.sp	.sp
PCRE_MULTILINE	PCRE_MULTILINE
.sp	.sp
By default, PCRE treats the subject string as consisting of a single line of	By default, for the purposes of matching "start of line" and "end of line",
characters (even if it actually contains newlines). The "start of line"	PCRE treats the subject string as consisting of a single line of characters,
metacharacter (^) matches only at the start of the string, while the "end of	even if it actually contains newlines. The "start of line" metacharacter (^)
line" metacharacter ($) matches only at the end of the string, or before a	matches only at the start of the string, and the "end of line" metacharacter
terminating newline (unless PCRE_DOLLAR_ENDONLY is set). This is the same as	($) matches only at the end of the string, or before a terminating newline
Perl.	(except when PCRE_DOLLAR_ENDONLY is set). Note, however, that unless
	PCRE_DOTALL is set, the "any character" metacharacter (.) does not match at a
	newline. This behaviour (for ^, $, and dot) is the same as Perl.
.P	.P
When PCRE_MULTILINE it is set, the "start of line" and "end of line" constructs	When PCRE_MULTILINE it is set, the "start of line" and "end of line" constructs
match immediately following or immediately before internal newlines in the	match immediately following or immediately before internal newlines in the
Line 674 equivalent to Perl's /m option, and it can be changed	Line 749 equivalent to Perl's /m option, and it can be changed
(?m) option setting. If there are no newlines in a subject string, or no	(?m) option setting. If there are no newlines in a subject string, or no
occurrences of ^ or $ in a pattern, setting PCRE_MULTILINE has no effect.	occurrences of ^ or $ in a pattern, setting PCRE_MULTILINE has no effect.
.sp	.sp
	PCRE_NEVER_UTF
	.sp
	This option locks out interpretation of the pattern as UTF-8 (or UTF-16 or
	UTF-32 in the 16-bit and 32-bit libraries). In particular, it prevents the
	creator of the pattern from switching to UTF interpretation by starting the
	pattern with (*UTF). This may be useful in applications that process patterns
	from external sources. The combination of PCRE_UTF8 and PCRE_NEVER_UTF also
	causes an error.
	.sp
PCRE_NEWLINE_CR	PCRE_NEWLINE_CR
PCRE_NEWLINE_LF	PCRE_NEWLINE_LF
PCRE_NEWLINE_CRLF	PCRE_NEWLINE_CRLF
Line 686 indicated by a single character (CR or LF, respectivel	Line 770 indicated by a single character (CR or LF, respectivel
PCRE_NEWLINE_CRLF specifies that a newline is indicated by the two-character	PCRE_NEWLINE_CRLF specifies that a newline is indicated by the two-character
CRLF sequence. Setting PCRE_NEWLINE_ANYCRLF specifies that any of the three	CRLF sequence. Setting PCRE_NEWLINE_ANYCRLF specifies that any of the three
preceding sequences should be recognized. Setting PCRE_NEWLINE_ANY specifies	preceding sequences should be recognized. Setting PCRE_NEWLINE_ANY specifies
that any Unicode newline sequence should be recognized. The Unicode newline	that any Unicode newline sequence should be recognized.
sequences are the three just mentioned, plus the single characters VT (vertical	.P
tab, U+000B), FF (formfeed, U+000C), NEL (next line, U+0085), LS (line	In an ASCII/Unicode environment, the Unicode newline sequences are the three
separator, U+2028), and PS (paragraph separator, U+2029). The last two are	just mentioned, plus the single characters VT (vertical tab, U+000B), FF (form
	feed, U+000C), NEL (next line, U+0085), LS (line separator, U+2028), and PS
	(paragraph separator, U+2029). For the 8-bit library, the last two are
recognized only in UTF-8 mode.	recognized only in UTF-8 mode.
.P	.P
	When PCRE is compiled to run in an EBCDIC (mainframe) environment, the code for
	CR is 0x0d, the same as ASCII. However, the character code for LF is normally
	0x15, though in some EBCDIC environments 0x25 is used. Whichever of these is
	not LF is made to correspond to Unicode's NEL character. EBCDIC codes are all
	less than 256. For more details, see the
	.\" HREF
	\fBpcrebuild\fP
	.\"
	documentation.
	.P
The newline setting in the options word uses three bits that are treated	The newline setting in the options word uses three bits that are treated
as a number, giving eight possibilities. Currently only six are used (default	as a number, giving eight possibilities. Currently only six are used (default
plus the five values above). This means that if you set more than one newline	plus the five values above). This means that if you set more than one newline
Line 700 PCRE_NEWLINE_CR with PCRE_NEWLINE_LF is equivalent to	Line 796 PCRE_NEWLINE_CR with PCRE_NEWLINE_LF is equivalent to
other combinations may yield unused numbers and cause an error.	other combinations may yield unused numbers and cause an error.
.P	.P
The only time that a line break in a pattern is specially recognized when	The only time that a line break in a pattern is specially recognized when
compiling is when PCRE_EXTENDED is set. CR and LF are whitespace characters,	compiling is when PCRE_EXTENDED is set. CR and LF are white space characters,
and so are ignored in this mode. Also, an unescaped # outside a character class	and so are ignored in this mode. Also, an unescaped # outside a character class
indicates a comment that lasts until after the next line break sequence. In	indicates a comment that lasts until after the next line break sequence. In
other circumstances, line break sequences in patterns are treated as literal	other circumstances, line break sequences in patterns are treated as literal
Line 717 were followed by ?: but named parentheses can still be	Line 813 were followed by ?: but named parentheses can still be
they acquire numbers in the usual way). There is no equivalent of this option	they acquire numbers in the usual way). There is no equivalent of this option
in Perl.	in Perl.
.sp	.sp
NO_START_OPTIMIZE	PCRE_NO_AUTO_POSSESS
.sp	.sp
	If this option is set, it disables "auto-possessification". This is an
	optimization that, for example, turns a+b into a++b in order to avoid
	backtracks into a+ that can never be successful. However, if callouts are in
	use, auto-possessification means that some of them are never taken. You can set
	this option if you want the matching functions to do a full unoptimized search
	and run all the callouts, but it is mainly provided for testing purposes.
	.sp
	PCRE_NO_START_OPTIMIZE
	.sp
This is an option that acts at matching time; that is, it is really an option	This is an option that acts at matching time; that is, it is really an option
for \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP. If it is set at compile time,	for \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP. If it is set at compile time,
it is remembered with the compiled pattern and assumed at matching time. For	it is remembered with the compiled pattern and assumed at matching time. This
details see the discussion of PCRE_NO_START_OPTIMIZE	is necessary if you want to use JIT execution, because the JIT compiler needs
	to know whether or not this option is set. For details see the discussion of
	PCRE_NO_START_OPTIMIZE
.\" HTML <a href="#execoptions">	.\" HTML <a href="#execoptions">
.\" </a>	.\" </a>
below.	below.
Line 755 with Perl. It can also be set by a (?U) option setting	Line 862 with Perl. It can also be set by a (?U) option setting
PCRE_UTF8	PCRE_UTF8
.sp	.sp
This option causes PCRE to regard both the pattern and the subject as strings	This option causes PCRE to regard both the pattern and the subject as strings
of UTF-8 characters instead of single-byte character strings. However, it is	of UTF-8 characters instead of single-byte strings. However, it is available
available only when PCRE is built to include UTF-8 support. If not, the use	only when PCRE is built to include UTF support. If not, the use of this option
of this option provokes an error. Details of how this option changes the	provokes an error. Details of how this option changes the behaviour of PCRE are
behaviour of PCRE are given in the	given in the
.\" HREF	.\" HREF
\fBpcreunicode\fP	\fBpcreunicode\fP
.\"	.\"
Line 768 page.	Line 875 page.
.sp	.sp
When PCRE_UTF8 is set, the validity of the pattern as a UTF-8 string is	When PCRE_UTF8 is set, the validity of the pattern as a UTF-8 string is
automatically checked. There is a discussion about the	automatically checked. There is a discussion about the
.\" HTML <a href="pcre.html#utf8strings">	.\" HTML <a href="pcreunicode.html#utf8strings">
.\" </a>	.\" </a>
validity of UTF-8 strings	validity of UTF-8 strings
.\"	.\"
in the main	in the
.\" HREF	.\" HREF
\fBpcre\fP	\fBpcreunicode\fP
.\"	.\"
page. If an invalid UTF-8 sequence of bytes is found, \fBpcre_compile()\fP	page. If an invalid UTF-8 sequence is found, \fBpcre_compile()\fP returns an
returns an error. If you already know that your pattern is valid, and you want	error. If you already know that your pattern is valid, and you want to skip
to skip this check for performance reasons, you can set the PCRE_NO_UTF8_CHECK	this check for performance reasons, you can set the PCRE_NO_UTF8_CHECK option.
option. When it is set, the effect of passing an invalid UTF-8 string as a	When it is set, the effect of passing an invalid UTF-8 string as a pattern is
pattern is undefined. It may cause your program to crash. Note that this option	undefined. It may cause your program to crash or loop. Note that this option
can also be passed to \fBpcre_exec()\fP and \fBpcre_dfa_exec()\fP, to suppress	can also be passed to \fBpcre_exec()\fP and \fBpcre_dfa_exec()\fP, to suppress
the UTF-8 validity checking of subject strings.	the validity checking of subject strings only. If the same string is being
	matched many times, the option can be safely set for the second and subsequent
	matchings to improve performance.
.	.
.	.
.SH "COMPILATION ERROR CODES"	.SH "COMPILATION ERROR CODES"
Line 790 the UTF-8 validity checking of subject strings.	Line 899 the UTF-8 validity checking of subject strings.
.sp	.sp
The following table lists the error codes than may be returned by	The following table lists the error codes than may be returned by
\fBpcre_compile2()\fP, along with the error messages that may be returned by	\fBpcre_compile2()\fP, along with the error messages that may be returned by
both compiling functions. As PCRE has developed, some error codes have fallen	both compiling functions. Note that error messages are always 8-bit ASCII
out of use. To avoid confusion, they have not been re-used.	strings, even in 16-bit or 32-bit mode. As PCRE has developed, some error codes
	have fallen out of use. To avoid confusion, they have not been re-used.
.sp	.sp
0 no error	0 no error
1 \e at end of pattern	1 \e at end of pattern
Line 825 out of use. To avoid confusion, they have not been re-	Line 935 out of use. To avoid confusion, they have not been re-
29 (?R or (?[+-]digits must be followed by )	29 (?R or (?[+-]digits must be followed by )
30 unknown POSIX class name	30 unknown POSIX class name
31 POSIX collating elements are not supported	31 POSIX collating elements are not supported
32 this version of PCRE is not compiled with PCRE_UTF8 support	32 this version of PCRE is compiled without UTF support
33 [this code is not in use]	33 [this code is not in use]
34 character value in \ex{...} sequence is too large	34 character value in \ex{} or \eo{} is too large
35 invalid condition (?(0)	35 invalid condition (?(0)
36 \eC not allowed in lookbehind assertion	36 \eC not allowed in lookbehind assertion
37 PCRE does not support \eL, \el, \eN{name}, \eU, or \eu	37 PCRE does not support \eL, \el, \eN{name}, \eU, or \eu
Line 837 out of use. To avoid confusion, they have not been re-	Line 947 out of use. To avoid confusion, they have not been re-
41 unrecognized character after (?P	41 unrecognized character after (?P
42 syntax error in subpattern name (missing terminator)	42 syntax error in subpattern name (missing terminator)
43 two named subpatterns have the same name	43 two named subpatterns have the same name
44 invalid UTF-8 string	44 invalid UTF-8 string (specifically UTF-8)
45 support for \eP, \ep, and \eX has not been compiled	45 support for \eP, \ep, and \eX has not been compiled
46 malformed \eP or \ep sequence	46 malformed \eP or \ep sequence
47 unknown property name after \eP or \ep	47 unknown property name after \eP or \ep
48 subpattern name is too long (maximum 32 characters)	48 subpattern name is too long (maximum 32 characters)
49 too many named subpatterns (maximum 10000)	49 too many named subpatterns (maximum 10000)
50 [this code is not in use]	50 [this code is not in use]
51 octal value is greater than \e377 (not in UTF-8 mode)	51 octal value is greater than \e377 in 8-bit non-UTF-8 mode
52 internal error: overran compiling workspace	52 internal error: overran compiling workspace
53 internal error: previously-checked referenced subpattern	53 internal error: previously-checked referenced subpattern
not found	not found
Line 855 out of use. To avoid confusion, they have not been re-	Line 965 out of use. To avoid confusion, they have not been re-
name/number or by a plain number	name/number or by a plain number
58 a numbered reference must not be zero	58 a numbered reference must not be zero
59 an argument is not allowed for (ACCEPT), (FAIL), or (*COMMIT)	59 an argument is not allowed for (ACCEPT), (FAIL), or (*COMMIT)
60 (*VERB) not recognized	60 (*VERB) not recognized or malformed
61 number is too big	61 number is too big
62 subpattern name expected	62 subpattern name expected
63 digit expected after (?+	63 digit expected after (?+
Line 863 out of use. To avoid confusion, they have not been re-	Line 973 out of use. To avoid confusion, they have not been re-
65 different names for subpatterns of the same number are	65 different names for subpatterns of the same number are
not allowed	not allowed
66 (*MARK) must have an argument	66 (*MARK) must have an argument
67 this version of PCRE is not compiled with PCRE_UCP support	67 this version of PCRE is not compiled with Unicode property
	support
68 \ec must be followed by an ASCII character	68 \ec must be followed by an ASCII character
69 \ek is not followed by a braced, angle-bracketed, or quoted name	69 \ek is not followed by a braced, angle-bracketed, or quoted name
	70 internal error: unknown opcode in find_fixedlength()
	71 \eN is not supported in a class
	72 too many forward references
	73 disallowed Unicode code point (>= 0xd800 && <= 0xdfff)
	74 invalid UTF-16 string (specifically UTF-16)
	75 name is too long in (MARK), (PRUNE), (SKIP), or (THEN)
	76 character value in \eu.... sequence is too large
	77 invalid UTF-32 string (specifically UTF-32)
	78 setting UTF is disabled by the application
	79 non-hex character in \ex{} (closing brace missing?)
	80 non-octal character in \eo{} (closing brace missing?)
	81 missing opening brace after \eo
	82 parentheses are too deeply nested
	83 invalid range in character class
.sp	.sp
The numbers 32 and 10000 in errors 48 and 49 are defaults; different values may	The numbers 32 and 10000 in errors 48 and 49 are defaults; different values may
be used if the limits were changed when PCRE was built.	be used if the limits were changed when PCRE was built.
Line 875 be used if the limits were changed when PCRE was built	Line 1000 be used if the limits were changed when PCRE was built
.SH "STUDYING A PATTERN"	.SH "STUDYING A PATTERN"
.rs	.rs
.sp	.sp
.B pcre_extra pcre_study(const pcre \fIcode\fP, int \fIoptions\fP	.nf
.ti +5n	.B pcre_extra pcre_study(const pcre \fIcode\fP, int \fIoptions\fP,
.B const char **\fIerrptr\fP);	.B " const char **\fIerrptr\fP);"
	.fi
.PP	.PP
If a compiled pattern is going to be used several times, it is worth spending	If a compiled pattern is going to be used several times, it is worth spending
more time analyzing it in order to speed up the time taken for matching. The	more time analyzing it in order to speed up the time taken for matching. The
Line 898 below	Line 1024 below
in the section on matching a pattern.	in the section on matching a pattern.
.P	.P
If studying the pattern does not produce any useful information,	If studying the pattern does not produce any useful information,
\fBpcre_study()\fP returns NULL. In that circumstance, if the calling program	\fBpcre_study()\fP returns NULL by default. In that circumstance, if the
wants to pass any of the other fields to \fBpcre_exec()\fP or	calling program wants to pass any of the other fields to \fBpcre_exec()\fP or
\fBpcre_dfa_exec()\fP, it must set up its own \fBpcre_extra\fP block.	\fBpcre_dfa_exec()\fP, it must set up its own \fBpcre_extra\fP block. However,
	if \fBpcre_study()\fP is called with the PCRE_STUDY_EXTRA_NEEDED option, it
	returns a \fBpcre_extra\fP block even if studying did not find any additional
	information. It may still return NULL, however, if an error occurs in
	\fBpcre_study()\fP.
.P	.P
The second argument of \fBpcre_study()\fP contains option bits. There is only	The second argument of \fBpcre_study()\fP contains option bits. There are three
one option: PCRE_STUDY_JIT_COMPILE. If this is set, and the just-in-time	further options in addition to PCRE_STUDY_EXTRA_NEEDED:
compiler is available, the pattern is further compiled into machine code that	.sp
executes much faster than the \fBpcre_exec()\fP matching function. If	PCRE_STUDY_JIT_COMPILE
the just-in-time compiler is not available, this option is ignored. All other	PCRE_STUDY_JIT_PARTIAL_HARD_COMPILE
bits in the \fIoptions\fP argument must be zero.	PCRE_STUDY_JIT_PARTIAL_SOFT_COMPILE
	.sp
	If any of these are set, and the just-in-time compiler is available, the
	pattern is further compiled into machine code that executes much faster than
	the \fBpcre_exec()\fP interpretive matching function. If the just-in-time
	compiler is not available, these options are ignored. All undefined bits in the
	\fIoptions\fP argument must be zero.
.P	.P
JIT compilation is a heavyweight optimization. It can take some time for	JIT compilation is a heavyweight optimization. It can take some time for
patterns to be analyzed, and for one-off matches and simple patterns the	patterns to be analyzed, and for one-off matches and simple patterns the
Line 931 When you are finished with a pattern, you can free the	Line 1067 When you are finished with a pattern, you can free the
study data by calling \fBpcre_free_study()\fP. This function was added to the	study data by calling \fBpcre_free_study()\fP. This function was added to the
API for release 8.20. For earlier versions, the memory could be freed with	API for release 8.20. For earlier versions, the memory could be freed with
\fBpcre_free()\fP, just like the pattern itself. This will still work in cases	\fBpcre_free()\fP, just like the pattern itself. This will still work in cases
where PCRE_STUDY_JIT_COMPILE is not used, but it is advisable to change to the	where JIT optimization is not used, but it is advisable to change to the new
new function when convenient.	function when convenient.
.P	.P
This is a typical way in which \fBpcre_study\fP() is used (except that in a	This is a typical way in which \fBpcre_study\fP() is used (except that in a
real application there should be tests for errors):	real application there should be tests for errors):
Line 954 real application there should be tests for errors):	Line 1090 real application there should be tests for errors):
Studying a pattern does two things: first, a lower bound for the length of	Studying a pattern does two things: first, a lower bound for the length of
subject string that is needed to match the pattern is computed. This does not	subject string that is needed to match the pattern is computed. This does not
mean that there are any strings of that length that match, but it does	mean that there are any strings of that length that match, but it does
guarantee that no shorter strings match. The value is used by	guarantee that no shorter strings match. The value is used to avoid wasting
\fBpcre_exec()\fP and \fBpcre_dfa_exec()\fP to avoid wasting time by trying to	time by trying to match strings that are shorter than the lower bound. You can
match strings that are shorter than the lower bound. You can find out the value	find out the value in a calling program via the \fBpcre_fullinfo()\fP function.
in a calling program via the \fBpcre_fullinfo()\fP function.
.P	.P
Studying a pattern is also useful for non-anchored patterns that do not have a	Studying a pattern is also useful for non-anchored patterns that do not have a
single fixed starting character. A bitmap of possible starting bytes is	single fixed starting character. A bitmap of possible starting bytes is
created. This speeds up finding a position in the subject at which to start	created. This speeds up finding a position in the subject at which to start
matching.	matching. (In 16-bit mode, the bitmap is used for 16-bit values less than 256.
	In 32-bit mode, the bitmap is used for 32-bit values less than 256.)
.P	.P
These two optimizations apply to both \fBpcre_exec()\fP and	These two optimizations apply to both \fBpcre_exec()\fP and
\fBpcre_dfa_exec()\fP. However, they are not used by \fBpcre_exec()\fP if	\fBpcre_dfa_exec()\fP, and the information is also used by the JIT compiler.
\fBpcre_study()\fP is called with the PCRE_STUDY_JIT_COMPILE option, and	The optimizations can be disabled by setting the PCRE_NO_START_OPTIMIZE option.
just-in-time compiling is successful. The optimizations can be disabled by	You might want to do this if your pattern contains callouts or (*MARK) and you
setting the PCRE_NO_START_OPTIMIZE option when calling \fBpcre_exec()\fP or	want to make use of these facilities in cases where matching fails.
\fBpcre_dfa_exec()\fP. You might want to do this if your pattern contains	.P
callouts or (*MARK) (which cannot be handled by the JIT compiler), and you want	PCRE_NO_START_OPTIMIZE can be specified at either compile time or execution
to make use of these facilities in cases where matching fails. See the	time. However, if PCRE_NO_START_OPTIMIZE is passed to \fBpcre_exec()\fP, (that
discussion of PCRE_NO_START_OPTIMIZE	is, after any JIT compilation has happened) JIT execution is disabled. For JIT
	execution to work with PCRE_NO_START_OPTIMIZE, the option must be set at
	compile time.
	.P
	There is a longer discussion of PCRE_NO_START_OPTIMIZE
.\" HTML <a href="#execoptions">	.\" HTML <a href="#execoptions">
.\" </a>	.\" </a>
below.	below.
Line 985 below.	Line 1125 below.
.sp	.sp
PCRE handles caseless matching, and determines whether characters are letters,	PCRE handles caseless matching, and determines whether characters are letters,
digits, or whatever, by reference to a set of tables, indexed by character	digits, or whatever, by reference to a set of tables, indexed by character
value. When running in UTF-8 mode, this applies only to characters with codes	code point. When running in UTF-8 mode, or in the 16- or 32-bit libraries, this
less than 128. By default, higher-valued codes never match escapes such as \ew	applies only to characters with code points less than 256. By default,
or \ed, but they can be tested with \ep if PCRE is built with Unicode character	higher-valued code points never match escapes such as \ew or \ed. However, if
property support. Alternatively, the PCRE_UCP option can be set at compile	PCRE is built with Unicode property support, all characters can be tested with
time; this causes \ew and friends to use Unicode property support instead of	\ep and \eP, or, alternatively, the PCRE_UCP option can be set when a pattern
built-in tables. The use of locales with Unicode is discouraged. If you are	is compiled; this causes \ew and friends to use Unicode property support
handling characters with codes greater than 128, you should either use UTF-8	instead of the built-in tables.
and Unicode, or use locales, but not try to mix the two.
.P	.P
	The use of locales with Unicode is discouraged. If you are handling characters
	with code points greater than 128, you should either use Unicode support, or
	use locales, but not try to mix the two.
	.P
PCRE contains an internal set of tables that are used when the final argument	PCRE contains an internal set of tables that are used when the final argument
of \fBpcre_compile()\fP is NULL. These are sufficient for many applications.	of \fBpcre_compile()\fP is NULL. These are sufficient for many applications.
Normally, the internal tables recognize only ASCII characters. However, when	Normally, the internal tables recognize only ASCII characters. However, when
Line 1007 for this locale support is expected to die away.	Line 1150 for this locale support is expected to die away.
.P	.P
External tables are built by calling the \fBpcre_maketables()\fP function,	External tables are built by calling the \fBpcre_maketables()\fP function,
which has no arguments, in the relevant locale. The result can then be passed	which has no arguments, in the relevant locale. The result can then be passed
to \fBpcre_compile()\fP or \fBpcre_exec()\fP as often as necessary. For	to \fBpcre_compile()\fP as often as necessary. For example, to build and use
example, to build and use tables that are appropriate for the French locale	tables that are appropriate for the French locale (where accented characters
(where accented characters with values greater than 128 are treated as letters),	with values greater than 128 are treated as letters), the following code could
the following code could be used:	be used:
.sp	.sp
setlocale(LC_CTYPE, "fr_FR");	setlocale(LC_CTYPE, "fr_FR");
tables = pcre_maketables();	tables = pcre_maketables();
Line 1026 needed.	Line 1169 needed.
.P	.P
The pointer that is passed to \fBpcre_compile()\fP is saved with the compiled	The pointer that is passed to \fBpcre_compile()\fP is saved with the compiled
pattern, and the same tables are used via this pointer by \fBpcre_study()\fP	pattern, and the same tables are used via this pointer by \fBpcre_study()\fP
and normally also by \fBpcre_exec()\fP. Thus, by default, for any single	and also by \fBpcre_exec()\fP and \fBpcre_dfa_exec()\fP. Thus, for any single
pattern, compilation, studying and matching all happen in the same locale, but	pattern, compilation, studying and matching all happen in the same locale, but
different patterns can be compiled in different locales.	different patterns can be processed in different locales.
.P	.P
It is possible to pass a table pointer or NULL (indicating the use of the	It is possible to pass a table pointer or NULL (indicating the use of the
internal tables) to \fBpcre_exec()\fP. Although not intended for this purpose,	internal tables) to \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP (see the
this facility could be used to match a pattern in a different locale from the	discussion below in the section on matching a pattern). This facility is
one in which it was compiled. Passing table pointers at run time is discussed	provided for use with pre-compiled patterns that have been saved and reloaded.
below in the section on matching a pattern.	Character tables are not saved with patterns, so if a non-standard table was
	used at compile time, it must be provided again when the reloaded pattern is
	matched. Attempting to use this facility to match a pattern in a different
	locale from the one in which it was compiled is likely to lead to anomalous
	(usually incorrect) results.
.	.
.	.
.\" HTML <a name="infoaboutpattern"></a>	.\" HTML <a name="infoaboutpattern"></a>
.SH "INFORMATION ABOUT A PATTERN"	.SH "INFORMATION ABOUT A PATTERN"
.rs	.rs
.sp	.sp
	.nf
.B int pcre_fullinfo(const pcre \fIcode\fP, "const pcre_extra \fIextra\fP,"	.B int pcre_fullinfo(const pcre \fIcode\fP, "const pcre_extra \fIextra\fP,"
.ti +5n	.B " int \fIwhat\fP, void *\fIwhere\fP);"
.B int \fIwhat\fP, void *\fIwhere\fP);	.PP
.PP	.PP
The \fBpcre_fullinfo()\fP function returns information about a compiled	The \fBpcre_fullinfo()\fP function returns information about a compiled
pattern. It replaces the obsolete \fBpcre_info()\fP function, which is	pattern. It replaces the \fBpcre_info()\fP function, which was removed from the
nevertheless retained for backwards compability (and is documented below).	library at version 8.30, after more than 10 years of obsolescence.
.P	.P
The first argument for \fBpcre_fullinfo()\fP is a pointer to the compiled	The first argument for \fBpcre_fullinfo()\fP is a pointer to the compiled
pattern. The second argument is the result of \fBpcre_study()\fP, or NULL if	pattern. The second argument is the result of \fBpcre_study()\fP, or NULL if
Line 1056 information is required, and the fourth argument is a	Line 1204 information is required, and the fourth argument is a
to receive the data. The yield of the function is zero for success, or one of	to receive the data. The yield of the function is zero for success, or one of
the following negative numbers:	the following negative numbers:
.sp	.sp
PCRE_ERROR_NULL the argument \fIcode\fP was NULL	PCRE_ERROR_NULL the argument \fIcode\fP was NULL
the argument \fIwhere\fP was NULL	the argument \fIwhere\fP was NULL
PCRE_ERROR_BADMAGIC the "magic number" was not found	PCRE_ERROR_BADMAGIC the "magic number" was not found
PCRE_ERROR_BADOPTION the value of \fIwhat\fP was invalid	PCRE_ERROR_BADENDIANNESS the pattern was compiled with different
	endianness
	PCRE_ERROR_BADOPTION the value of \fIwhat\fP was invalid
	PCRE_ERROR_UNSET the requested field is not set
.sp	.sp
The "magic number" is placed at the start of each compiled pattern as an simple	The "magic number" is placed at the start of each compiled pattern as an simple
check against passing an arbitrary memory pointer. Here is a typical call of	check against passing an arbitrary memory pointer. The endianness error can
\fBpcre_fullinfo()\fP, to obtain the length of the compiled pattern:	occur if a compiled pattern is saved and reloaded on a different host. Here is
	a typical call of \fBpcre_fullinfo()\fP, to obtain the length of the compiled
	pattern:
.sp	.sp
int rc;	int rc;
size_t length;	size_t length;
Line 1097 a NULL table pointer.	Line 1250 a NULL table pointer.
.sp	.sp
PCRE_INFO_FIRSTBYTE	PCRE_INFO_FIRSTBYTE
.sp	.sp
Return information about the first byte of any matched string, for a	Return information about the first data unit of any matched string, for a
non-anchored pattern. The fourth argument should point to an \fBint\fP	non-anchored pattern. (The name of this option refers to the 8-bit library,
variable. (This option used to be called PCRE_INFO_FIRSTCHAR; the old name is	where data units are bytes.) The fourth argument should point to an \fBint\fP
still recognized for backwards compatibility.)	variable.
.P	.P
If there is a fixed first byte, for example, from a pattern such as	If there is a fixed first value, for example, the letter "c" from a pattern
(cat\|cow\|coyote), its value is returned. Otherwise, if either	such as (cat\|cow\|coyote), its value is returned. In the 8-bit library, the
	value is always less than 256. In the 16-bit library the value can be up to
	0xffff. In the 32-bit library the value can be up to 0x10ffff.
	.P
	If there is no fixed first value, and if either
.sp	.sp
(a) the pattern was compiled with the PCRE_MULTILINE option, and every branch	(a) the pattern was compiled with the PCRE_MULTILINE option, and every branch
starts with "^", or	starts with "^", or
Line 1114 starts with "^", or	Line 1271 starts with "^", or
-1 is returned, indicating that the pattern matches only at the start of a	-1 is returned, indicating that the pattern matches only at the start of a
subject string or after any newline within the string. Otherwise -2 is	subject string or after any newline within the string. Otherwise -2 is
returned. For anchored patterns, -2 is returned.	returned. For anchored patterns, -2 is returned.
	.P
	Since for the 32-bit library using the non-UTF-32 mode, this function is unable
	to return the full 32-bit range of the character, this value is deprecated;
	instead the PCRE_INFO_FIRSTCHARACTERFLAGS and PCRE_INFO_FIRSTCHARACTER values
	should be used.
.sp	.sp
PCRE_INFO_FIRSTTABLE	PCRE_INFO_FIRSTTABLE
.sp	.sp
If the pattern was studied, and this resulted in the construction of a 256-bit	If the pattern was studied, and this resulted in the construction of a 256-bit
table indicating a fixed set of bytes for the first byte in any matching	table indicating a fixed set of values for the first data unit in any matching
string, a pointer to the table is returned. Otherwise NULL is returned. The	string, a pointer to the table is returned. Otherwise NULL is returned. The
fourth argument should point to an \fBunsigned char *\fP variable.	fourth argument should point to an \fBunsigned char *\fP variable.
.sp	.sp
Line 1136 Return 1 if the (?J) or (?-J) option setting is used i	Line 1298 Return 1 if the (?J) or (?-J) option setting is used i
.sp	.sp
PCRE_INFO_JIT	PCRE_INFO_JIT
.sp	.sp
Return 1 if the pattern was studied with the PCRE_STUDY_JIT_COMPILE option, and	Return 1 if the pattern was studied with one of the JIT options, and
just-in-time compiling was successful. The fourth argument should point to an	just-in-time compiling was successful. The fourth argument should point to an
\fBint\fP variable. A return value of 0 means that JIT support is not available	\fBint\fP variable. A return value of 0 means that JIT support is not available
in this version of PCRE, or that the pattern was not studied with the	in this version of PCRE, or that the pattern was not studied with a JIT option,
PCRE_STUDY_JIT_COMPILE option, or that the JIT compiler could not handle this	or that the JIT compiler could not handle this particular pattern. See the
particular pattern. See the
.\" HREF	.\" HREF
\fBpcrejit\fP	\fBpcrejit\fP
.\"	.\"
Line 1149 documentation for details of what can and cannot be ha	Line 1310 documentation for details of what can and cannot be ha
.sp	.sp
PCRE_INFO_JITSIZE	PCRE_INFO_JITSIZE
.sp	.sp
If the pattern was successfully studied with the PCRE_STUDY_JIT_COMPILE option,	If the pattern was successfully studied with a JIT option, return the size of
return the size of the JIT compiled code, otherwise return zero. The fourth	the JIT compiled code, otherwise return zero. The fourth argument should point
argument should point to a \fBsize_t\fP variable.	to a \fBsize_t\fP variable.
.sp	.sp
PCRE_INFO_LASTLITERAL	PCRE_INFO_LASTLITERAL
.sp	.sp
Return the value of the rightmost literal byte that must exist in any matched	Return the value of the rightmost literal data unit that must exist in any
string, other than at its start, if such a byte has been recorded. The fourth	matched string, other than at its start, if such a value has been recorded. The
argument should point to an \fBint\fP variable. If there is no such byte, -1 is	fourth argument should point to an \fBint\fP variable. If there is no such
returned. For anchored patterns, a last literal byte is recorded only if it	value, -1 is returned. For anchored patterns, a last literal value is recorded
follows something of variable length. For example, for the pattern	only if it follows something of variable length. For example, for the pattern
/^a\ed+z\ed+/ the returned value is "z", but for /^a\edz\ed/ the returned value	/^a\ed+z\ed+/ the returned value is "z", but for /^a\edz\ed/ the returned value
is -1.	is -1.
	.P
	Since for the 32-bit library using the non-UTF-32 mode, this function is unable
	to return the full 32-bit range of characters, this value is deprecated;
	instead the PCRE_INFO_REQUIREDCHARFLAGS and PCRE_INFO_REQUIREDCHAR values should
	be used.
.sp	.sp
	PCRE_INFO_MATCH_EMPTY
	.sp
	Return 1 if the pattern can match an empty string, otherwise 0. The fourth
	argument should point to an \fBint\fP variable.
	.sp
	PCRE_INFO_MATCHLIMIT
	.sp
	If the pattern set a match limit by including an item of the form
	(*LIMIT_MATCH=nnnn) at the start, the value is returned. The fourth argument
	should point to an unsigned 32-bit integer. If no such value has been set, the
	call to \fBpcre_fullinfo()\fP returns the error PCRE_ERROR_UNSET.
	.sp
	PCRE_INFO_MAXLOOKBEHIND
	.sp
	Return the number of characters (NB not data units) in the longest lookbehind
	assertion in the pattern. This information is useful when doing multi-segment
	matching using the partial matching facilities. Note that the simple assertions
	\eb and \eB require a one-character lookbehind. \eA also registers a
	one-character lookbehind, though it does not actually inspect the previous
	character. This is to ensure that at least one character from the old segment
	is retained when a new segment is processed. Otherwise, if there are no
	lookbehinds in the pattern, \eA might match incorrectly at the start of a new
	segment.
	.sp
PCRE_INFO_MINLENGTH	PCRE_INFO_MINLENGTH
.sp	.sp
If the pattern was studied and a minimum length for matching subject strings	If the pattern was studied and a minimum length for matching subject strings
was computed, its value is returned. Otherwise the returned value is -1. The	was computed, its value is returned. Otherwise the returned value is -1. The
value is a number of characters, not bytes (this may be relevant in UTF-8	value is a number of characters, which in UTF mode may be different from the
mode). The fourth argument should point to an \fBint\fP variable. A	number of data units. The fourth argument should point to an \fBint\fP
non-negative value is a lower bound to the length of any matching string. There	variable. A non-negative value is a lower bound to the length of any matching
may not be any strings of that length that do actually match, but every string	string. There may not be any strings of that length that do actually match, but
that does match is at least that long.	every string that does match is at least that long.
.sp	.sp
PCRE_INFO_NAMECOUNT	PCRE_INFO_NAMECOUNT
PCRE_INFO_NAMEENTRYSIZE	PCRE_INFO_NAMEENTRYSIZE
Line 1191 The map consists of a number of fixed-size entries. PC	Line 1381 The map consists of a number of fixed-size entries. PC
the number of entries, and PCRE_INFO_NAMEENTRYSIZE gives the size of each	the number of entries, and PCRE_INFO_NAMEENTRYSIZE gives the size of each
entry; both of these return an \fBint\fP value. The entry size depends on the	entry; both of these return an \fBint\fP value. The entry size depends on the
length of the longest name. PCRE_INFO_NAMETABLE returns a pointer to the first	length of the longest name. PCRE_INFO_NAMETABLE returns a pointer to the first
entry of the table (a pointer to \fBchar\fP). The first two bytes of each entry	entry of the table. This is a pointer to \fBchar\fP in the 8-bit library, where
are the number of the capturing parenthesis, most significant byte first. The	the first two bytes of each entry are the number of the capturing parenthesis,
rest of the entry is the corresponding name, zero terminated.	most significant byte first. In the 16-bit library, the pointer points to
	16-bit data units, the first of which contains the parenthesis number. In the
	32-bit library, the pointer points to 32-bit data units, the first of which
	contains the parenthesis number. The rest of the entry is the corresponding
	name, zero terminated.
.P	.P
The names are in alphabetical order. Duplicate names may appear if (?\| is used	The names are in alphabetical order. If (?\| is used to create multiple groups
to create multiple groups with the same number, as described in the	with the same number, as described in the
.\" HTML <a href="pcrepattern.html#dupsubpatternnumber">	.\" HTML <a href="pcrepattern.html#dupsubpatternnumber">
.\" </a>	.\" </a>
section on duplicate subpattern numbers	section on duplicate subpattern numbers
Line 1205 in the	Line 1399 in the
.\" HREF	.\" HREF
\fBpcrepattern\fP	\fBpcrepattern\fP
.\"	.\"
page. Duplicate names for subpatterns with different numbers are permitted only	page, the groups may be given the same name, but there is only one entry in the
if PCRE_DUPNAMES is set. In all cases of duplicate names, they appear in the	table. Different names for groups of the same number are not permitted.
table in the order in which they were found in the pattern. In the absence of	Duplicate names for subpatterns with different numbers are permitted,
(?\| this is the order of increasing number; when (?\| is used this is not	but only if PCRE_DUPNAMES is set. They appear in the table in the order in
necessarily the case because later subpatterns may have lower numbers.	which they were found in the pattern. In the absence of (?\| this is the order
	of increasing number; when (?\| is used this is not necessarily the case because
	later subpatterns may have lower numbers.
.P	.P
As a simple example of the name/number table, consider the following pattern	As a simple example of the name/number table, consider the following pattern
(assume PCRE_EXTENDED is set, so white space - including newlines - is	after compilation by the 8-bit library (assume PCRE_EXTENDED is set, so white
ignored):	space - including newlines - is ignored):
.sp	.sp
.\" JOIN	.\" JOIN
(?<date> (?<year>(\ed\ed)?\ed\ed) -	(?<date> (?<year>(\ed\ed)?\ed\ed) -
Line 1266 alternatives begin with one of the following:	Line 1462 alternatives begin with one of the following:
For such patterns, the PCRE_ANCHORED bit is set in the options returned by	For such patterns, the PCRE_ANCHORED bit is set in the options returned by
\fBpcre_fullinfo()\fP.	\fBpcre_fullinfo()\fP.
.sp	.sp
	PCRE_INFO_RECURSIONLIMIT
	.sp
	If the pattern set a recursion limit by including an item of the form
	(*LIMIT_RECURSION=nnnn) at the start, the value is returned. The fourth
	argument should point to an unsigned 32-bit integer. If no such value has been
	set, the call to \fBpcre_fullinfo()\fP returns the error PCRE_ERROR_UNSET.
	.sp
PCRE_INFO_SIZE	PCRE_INFO_SIZE
.sp	.sp
Return the size of the compiled pattern. The fourth argument should point to a	Return the size of the compiled pattern in bytes (for all three libraries). The
\fBsize_t\fP variable. This value does not include the size of the \fBpcre\fP	fourth argument should point to a \fBsize_t\fP variable. This value does not
structure that is returned by \fBpcre_compile()\fP. The value that is passed as	include the size of the \fBpcre\fP structure that is returned by
the argument to \fBpcre_malloc()\fP when \fBpcre_compile()\fP is getting memory	\fBpcre_compile()\fP. The value that is passed as the argument to
in which to place the compiled data is the value returned by this option plus	\fBpcre_malloc()\fP when \fBpcre_compile()\fP is getting memory in which to
the size of the \fBpcre\fP structure. Studying a compiled pattern, with or	place the compiled data is the value returned by this option plus the size of
without JIT, does not alter the value returned by this option.	the \fBpcre\fP structure. Studying a compiled pattern, with or without JIT,
	does not alter the value returned by this option.
.sp	.sp
PCRE_INFO_STUDYSIZE	PCRE_INFO_STUDYSIZE
.sp	.sp
Return the size of the data block pointed to by the \fIstudy_data\fP field in a	Return the size in bytes (for all three libraries) of the data block pointed to
\fBpcre_extra\fP block. If \fBpcre_extra\fP is NULL, or there is no study data,	by the \fIstudy_data\fP field in a \fBpcre_extra\fP block. If \fBpcre_extra\fP
zero is returned. The fourth argument should point to a \fBsize_t\fP variable.	is NULL, or there is no study data, zero is returned. The fourth argument
The \fIstudy_data\fP field is set by \fBpcre_study()\fP to record information	should point to a \fBsize_t\fP variable. The \fIstudy_data\fP field is set by
that will speed up matching (see the section entitled	\fBpcre_study()\fP to record information that will speed up matching (see the
	section entitled
.\" HTML <a href="#studyingapattern">	.\" HTML <a href="#studyingapattern">
.\" </a>	.\" </a>
"Studying a pattern"	"Studying a pattern"
Line 1293 is made available via this option so that it can be sa	Line 1498 is made available via this option so that it can be sa
\fBpcreprecompile\fP	\fBpcreprecompile\fP
.\"	.\"
documentation for details).	documentation for details).
.
.
.SH "OBSOLETE INFO FUNCTION"
.rs
.sp	.sp
.B int pcre_info(const pcre \fIcode\fP, int \fIoptptr\fP, int	PCRE_INFO_FIRSTCHARACTERFLAGS
.B *\fIfirstcharptr\fP);
.PP
The \fBpcre_info()\fP function is now obsolete because its interface is too
restrictive to return all the available data about a compiled pattern. New
programs should use \fBpcre_fullinfo()\fP instead. The yield of
\fBpcre_info()\fP is the number of capturing subpatterns, or one of the
following negative numbers:
.sp	.sp
PCRE_ERROR_NULL the argument \fIcode\fP was NULL	Return information about the first data unit of any matched string, for a
PCRE_ERROR_BADMAGIC the "magic number" was not found	non-anchored pattern. The fourth argument should point to an \fBint\fP
	variable.
	.P
	If there is a fixed first value, for example, the letter "c" from a pattern
	such as (cat\|cow\|coyote), 1 is returned, and the character value can be
	retrieved using PCRE_INFO_FIRSTCHARACTER.
	.P
	If there is no fixed first value, and if either
.sp	.sp
If the \fIoptptr\fP argument is not NULL, a copy of the options with which the	(a) the pattern was compiled with the PCRE_MULTILINE option, and every branch
pattern was compiled is placed in the integer it points to (see	starts with "^", or
PCRE_INFO_OPTIONS above).	.sp
	(b) every branch of the pattern starts with ".*" and PCRE_DOTALL is not set
	(if it were set, the pattern would be anchored),
	.sp
	2 is returned, indicating that the pattern matches only at the start of a
	subject string or after any newline within the string. Otherwise 0 is
	returned. For anchored patterns, 0 is returned.
	.sp
	PCRE_INFO_FIRSTCHARACTER
	.sp
	Return the fixed first character value in the situation where
	PCRE_INFO_FIRSTCHARACTERFLAGS returns 1; otherwise return 0. The fourth
	argument should point to an \fBuint_t\fP variable.
.P	.P
If the pattern is not anchored and the \fIfirstcharptr\fP argument is not NULL,	In the 8-bit library, the value is always less than 256. In the 16-bit library
it is used to pass back information about the first character of any matched	the value can be up to 0xffff. In the 32-bit library in UTF-32 mode the value
string (see PCRE_INFO_FIRSTBYTE above).	can be up to 0x10ffff, and up to 0xffffffff when not using UTF-32 mode.
	.sp
	PCRE_INFO_REQUIREDCHARFLAGS
	.sp
	Returns 1 if there is a rightmost literal data unit that must exist in any
	matched string, other than at its start. The fourth argument should point to
	an \fBint\fP variable. If there is no such value, 0 is returned. If returning
	1, the character value itself can be retrieved using PCRE_INFO_REQUIREDCHAR.
	.P
	For anchored patterns, a last literal value is recorded only if it follows
	something of variable length. For example, for the pattern /^a\ed+z\ed+/ the
	returned value 1 (with "z" returned from PCRE_INFO_REQUIREDCHAR), but for
	/^a\edz\ed/ the returned value is 0.
	.sp
	PCRE_INFO_REQUIREDCHAR
	.sp
	Return the value of the rightmost literal data unit that must exist in any
	matched string, other than at its start, if such a value has been recorded. The
	fourth argument should point to an \fBuint32_t\fP variable. If there is no such
	value, 0 is returned.
.	.
.	.
.SH "REFERENCE COUNTS"	.SH "REFERENCE COUNTS"
Line 1345 is different. (This seems a highly unlikely scenario.)	Line 1577 is different. (This seems a highly unlikely scenario.)
.SH "MATCHING A PATTERN: THE TRADITIONAL FUNCTION"	.SH "MATCHING A PATTERN: THE TRADITIONAL FUNCTION"
.rs	.rs
.sp	.sp
	.nf
.B int pcre_exec(const pcre \fIcode\fP, "const pcre_extra \fIextra\fP,"	.B int pcre_exec(const pcre \fIcode\fP, "const pcre_extra \fIextra\fP,"
.ti +5n	.B " const char *\fIsubject\fP," int \fIlength\fP, int \fIstartoffset\fP,
.B "const char *\fIsubject\fP," int \fIlength\fP, int \fIstartoffset\fP,	.B " int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP);"
.ti +5n	.fi
.B int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP);
.P	.P
The function \fBpcre_exec()\fP is called to match a subject string against a	The function \fBpcre_exec()\fP is called to match a subject string against a
compiled pattern, which is passed in the \fIcode\fP argument. If the	compiled pattern, which is passed in the \fIcode\fP argument. If the
Line 1411 fields (not necessarily in this order):	Line 1643 fields (not necessarily in this order):
const unsigned char *\fItables\fP;	const unsigned char *\fItables\fP;
unsigned char **\fImark\fP;	unsigned char **\fImark\fP;
.sp	.sp
The \fIflags\fP field is a bitmap that specifies which of the other fields	In the 16-bit version of this structure, the \fImark\fP field has type
are set. The flag bits are:	"PCRE_UCHAR16 **".
.sp	.sp
PCRE_EXTRA_STUDY_DATA	In the 32-bit version of this structure, the \fImark\fP field has type
	"PCRE_UCHAR32 **".
	.P
	The \fIflags\fP field is used to specify which of the other fields are set. The
	flag bits are:
	.sp
	PCRE_EXTRA_CALLOUT_DATA
PCRE_EXTRA_EXECUTABLE_JIT	PCRE_EXTRA_EXECUTABLE_JIT
	PCRE_EXTRA_MARK
PCRE_EXTRA_MATCH_LIMIT	PCRE_EXTRA_MATCH_LIMIT
PCRE_EXTRA_MATCH_LIMIT_RECURSION	PCRE_EXTRA_MATCH_LIMIT_RECURSION
PCRE_EXTRA_CALLOUT_DATA	PCRE_EXTRA_STUDY_DATA
PCRE_EXTRA_TABLES	PCRE_EXTRA_TABLES
PCRE_EXTRA_MARK
.sp	.sp
Other flag bits should be set to zero. The \fIstudy_data\fP field and sometimes	Other flag bits should be set to zero. The \fIstudy_data\fP field and sometimes
the \fIexecutable_jit\fP field are set in the \fBpcre_extra\fP block that is	the \fIexecutable_jit\fP field are set in the \fBpcre_extra\fP block that is
returned by \fBpcre_study()\fP, together with the appropriate flag bits. You	returned by \fBpcre_study()\fP, together with the appropriate flag bits. You
should not set these yourself, but you may add to the block by setting the	should not set these yourself, but you may add to the block by setting other
other fields and their corresponding flag bits.	fields and their corresponding flag bits.
.P	.P
The \fImatch_limit\fP field provides a means of preventing PCRE from using up a	The \fImatch_limit\fP field provides a means of preventing PCRE from using up a
vast amount of resources when running patterns that are not going to match,	vast amount of resources when running patterns that are not going to match,
Line 1441 patterns that are not anchored, the count restarts fro	Line 1679 patterns that are not anchored, the count restarts fro
in the subject string.	in the subject string.
.P	.P
When \fBpcre_exec()\fP is called with a pattern that was successfully studied	When \fBpcre_exec()\fP is called with a pattern that was successfully studied
with the PCRE_STUDY_JIT_COMPILE option, the way that the matching is executed	with a JIT option, the way that the matching is executed is entirely different.
is entirely different. However, there is still the possibility of runaway	However, there is still the possibility of runaway matching that goes on for a
matching that goes on for a very long time, and so the \fImatch_limit\fP value	very long time, and so the \fImatch_limit\fP value is also used in this case
is also used in this case (but in a different way) to limit how long the	(but in a different way) to limit how long the matching can continue.
matching can continue.
.P	.P
The default value for the limit can be set when PCRE is built; the default	The default value for the limit can be set when PCRE is built; the default
default is 10 million, which handles all but the most extreme cases. You can	default is 10 million, which handles all but the most extreme cases. You can
Line 1454 block in which \fImatch_limit\fP is set, and PCRE_EXTR	Line 1691 block in which \fImatch_limit\fP is set, and PCRE_EXTR
the \fIflags\fP field. If the limit is exceeded, \fBpcre_exec()\fP returns	the \fIflags\fP field. If the limit is exceeded, \fBpcre_exec()\fP returns
PCRE_ERROR_MATCHLIMIT.	PCRE_ERROR_MATCHLIMIT.
.P	.P
	A value for the match limit may also be supplied by an item at the start of a
	pattern of the form
	.sp
	(*LIMIT_MATCH=d)
	.sp
	where d is a decimal number. However, such a setting is ignored unless d is
	less than the limit set by the caller of \fBpcre_exec()\fP or, if no such limit
	is set, less than the default.
	.P
The \fImatch_limit_recursion\fP field is similar to \fImatch_limit\fP, but	The \fImatch_limit_recursion\fP field is similar to \fImatch_limit\fP, but
instead of limiting the total number of times that \fBmatch()\fP is called, it	instead of limiting the total number of times that \fBmatch()\fP is called, it
limits the depth of recursion. The recursion depth is a smaller number than the	limits the depth of recursion. The recursion depth is a smaller number than the
Line 1463 This limit is of use only if it is set smaller than \f	Line 1709 This limit is of use only if it is set smaller than \f
Limiting the recursion depth limits the amount of machine stack that can be	Limiting the recursion depth limits the amount of machine stack that can be
used, or, when PCRE has been compiled to use memory on the heap instead of the	used, or, when PCRE has been compiled to use memory on the heap instead of the
stack, the amount of heap memory that can be used. This limit is not relevant,	stack, the amount of heap memory that can be used. This limit is not relevant,
and is ignored, if the pattern was successfully studied with	and is ignored, when matching is done using JIT compiled code.
PCRE_STUDY_JIT_COMPILE.
.P	.P
The default value for \fImatch_limit_recursion\fP can be set when PCRE is	The default value for \fImatch_limit_recursion\fP can be set when PCRE is
built; the default default is the same value as the default for	built; the default default is the same value as the default for
Line 1473 with a \fBpcre_extra\fP block in which \fImatch_limit_	Line 1718 with a \fBpcre_extra\fP block in which \fImatch_limit_
PCRE_EXTRA_MATCH_LIMIT_RECURSION is set in the \fIflags\fP field. If the limit	PCRE_EXTRA_MATCH_LIMIT_RECURSION is set in the \fIflags\fP field. If the limit
is exceeded, \fBpcre_exec()\fP returns PCRE_ERROR_RECURSIONLIMIT.	is exceeded, \fBpcre_exec()\fP returns PCRE_ERROR_RECURSIONLIMIT.
.P	.P
	A value for the recursion limit may also be supplied by an item at the start of
	a pattern of the form
	.sp
	(*LIMIT_RECURSION=d)
	.sp
	where d is a decimal number. However, such a setting is ignored unless d is
	less than the limit set by the caller of \fBpcre_exec()\fP or, if no such limit
	is set, less than the default.
	.P
The \fIcallout_data\fP field is used in conjunction with the "callout" feature,	The \fIcallout_data\fP field is used in conjunction with the "callout" feature,
and is described in the	and is described in the
.\" HREF	.\" HREF
Line 1480 and is described in the	Line 1734 and is described in the
.\"	.\"
documentation.	documentation.
.P	.P
The \fItables\fP field is used to pass a character tables pointer to	The \fItables\fP field is provided for use with patterns that have been
\fBpcre_exec()\fP; this overrides the value that is stored with the compiled	pre-compiled using custom character tables, saved to disc or elsewhere, and
pattern. A non-NULL value is stored with the compiled pattern only if custom	then reloaded, because the tables that were used to compile a pattern are not
tables were supplied to \fBpcre_compile()\fP via its \fItableptr\fP argument.	saved with it. See the
If NULL is passed to \fBpcre_exec()\fP using this mechanism, it forces PCRE's
internal tables to be used. This facility is helpful when re-using patterns
that have been saved after compiling with an external set of tables, because
the external tables might be at a different address when \fBpcre_exec()\fP is
called. See the
.\" HREF	.\" HREF
\fBpcreprecompile\fP	\fBpcreprecompile\fP
.\"	.\"
documentation for a discussion of saving compiled patterns for later use.	documentation for a discussion of saving compiled patterns for later use. If
	NULL is passed using this mechanism, it forces PCRE's internal tables to be
	used.
.P	.P
	\fBWarning:\fP The tables that \fBpcre_exec()\fP uses must be the same as those
	that were used when the pattern was compiled. If this is not the case, the
	behaviour of \fBpcre_exec()\fP is undefined. Therefore, when a pattern is
	compiled and matched in the same process, this field should never be set. In
	this (the most common) case, the correct table pointer is automatically passed
	with the compiled pattern from \fBpcre_compile()\fP to \fBpcre_exec()\fP.
	.P
If PCRE_EXTRA_MARK is set in the \fIflags\fP field, the \fImark\fP field must	If PCRE_EXTRA_MARK is set in the \fIflags\fP field, the \fImark\fP field must
be set to point to a \fBchar *\fP variable. If the pattern contains any	be set to point to a suitable variable. If the pattern contains any
backtracking control verbs such as (*MARK:NAME), and the execution ends up with	backtracking control verbs such as (*MARK:NAME), and the execution ends up with
a name to pass back, a pointer to the name string (zero terminated) is placed	a name to pass back, a pointer to the name string (zero terminated) is placed
in the variable pointed to by the \fImark\fP field. The names are within the	in the variable pointed to by the \fImark\fP field. The names are within the
compiled pattern; if you wish to retain such a name you must copy it before	compiled pattern; if you wish to retain such a name you must copy it before
freeing the memory of a compiled pattern. If there is no name to pass back, the	freeing the memory of a compiled pattern. If there is no name to pass back, the
variable pointed to by the \fImark\fP field set to NULL. For details of the	variable pointed to by the \fImark\fP field is set to NULL. For details of the
backtracking control verbs, see the section entitled	backtracking control verbs, see the section entitled
.\" HTML <a href="pcrepattern#backtrackcontrol">	.\" HTML <a href="pcrepattern#backtrackcontrol">
.\" </a>	.\" </a>
Line 1521 documentation.	Line 1779 documentation.
The unused bits of the \fIoptions\fP argument for \fBpcre_exec()\fP must be	The unused bits of the \fIoptions\fP argument for \fBpcre_exec()\fP must be
zero. The only bits that may be set are PCRE_ANCHORED, PCRE_NEWLINE_\fIxxx\fP,	zero. The only bits that may be set are PCRE_ANCHORED, PCRE_NEWLINE_\fIxxx\fP,
PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, PCRE_NOTEMPTY_ATSTART,	PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, PCRE_NOTEMPTY_ATSTART,
PCRE_NO_START_OPTIMIZE, PCRE_NO_UTF8_CHECK, PCRE_PARTIAL_SOFT, and	PCRE_NO_START_OPTIMIZE, PCRE_NO_UTF8_CHECK, PCRE_PARTIAL_HARD, and
PCRE_PARTIAL_HARD.	PCRE_PARTIAL_SOFT.
.P	.P
If the pattern was successfully studied with the PCRE_STUDY_JIT_COMPILE option,	If the pattern was successfully studied with one of the just-in-time (JIT)
the only supported options for JIT execution are PCRE_NO_UTF8_CHECK,	compile options, the only supported options for JIT execution are
PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, and PCRE_NOTEMPTY_ATSTART. Note in	PCRE_NO_UTF8_CHECK, PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY,
particular that partial matching is not supported. If an unsupported option is	PCRE_NOTEMPTY_ATSTART, PCRE_PARTIAL_HARD, and PCRE_PARTIAL_SOFT. If an
used, JIT execution is disabled and the normal interpretive code in	unsupported option is used, JIT execution is disabled and the normal
\fBpcre_exec()\fP is run.	interpretive code in \fBpcre_exec()\fP is run.
.sp	.sp
PCRE_ANCHORED	PCRE_ANCHORED
.sp	.sp
Line 1638 unanchored match must start with a specific character,	Line 1896 unanchored match must start with a specific character,
for that character, and fails immediately if it cannot find it, without	for that character, and fails immediately if it cannot find it, without
actually running the main matching function. This means that a special item	actually running the main matching function. This means that a special item
such as (*COMMIT) at the start of a pattern is not considered until after a	such as (*COMMIT) at the start of a pattern is not considered until after a
suitable starting point for the match has been found. When callouts or (*MARK)	suitable starting point for the match has been found. Also, when callouts or
items are in use, these "start-up" optimizations can cause them to be skipped	(*MARK) items are in use, these "start-up" optimizations can cause them to be
if the pattern is never actually used. The start-up optimizations are in effect	skipped if the pattern is never actually used. The start-up optimizations are
a pre-scan of the subject that takes place before the pattern is run.	in effect a pre-scan of the subject that takes place before the pattern is run.
.P	.P
The PCRE_NO_START_OPTIMIZE option disables the start-up optimizations, possibly	The PCRE_NO_START_OPTIMIZE option disables the start-up optimizations, possibly
causing performance to suffer, but ensuring that in cases where the result is	causing performance to suffer, but ensuring that in cases where the result is
"no match", the callouts do occur, and that items such as (COMMIT) and (MARK)	"no match", the callouts do occur, and that items such as (COMMIT) and (MARK)
are considered at every possible starting position in the subject string. If	are considered at every possible starting position in the subject string. If
PCRE_NO_START_OPTIMIZE is set at compile time, it cannot be unset at matching	PCRE_NO_START_OPTIMIZE is set at compile time, it cannot be unset at matching
time.	time. The use of PCRE_NO_START_OPTIMIZE at matching time (that is, passing it
	to \fBpcre_exec()\fP) disables JIT execution; in this situation, matching is
	always done using interpretively.
.P	.P
Setting PCRE_NO_START_OPTIMIZE can change the outcome of a matching operation.	Setting PCRE_NO_START_OPTIMIZE can change the outcome of a matching operation.
Consider the pattern	Consider the pattern
Line 1681 returned.	Line 1941 returned.
.sp	.sp
When PCRE_UTF8 is set at compile time, the validity of the subject as a UTF-8	When PCRE_UTF8 is set at compile time, the validity of the subject as a UTF-8
string is automatically checked when \fBpcre_exec()\fP is subsequently called.	string is automatically checked when \fBpcre_exec()\fP is subsequently called.
The value of \fIstartoffset\fP is also checked to ensure that it points to the	The entire string is checked before any other processing takes place. The value
start of a UTF-8 character. There is a discussion about the validity of UTF-8	of \fIstartoffset\fP is also checked to ensure that it points to the start of a
strings in the	UTF-8 character. There is a discussion about the
.\" HTML <a href="pcre.html#utf8strings">	.\" HTML <a href="pcreunicode.html#utf8strings">
.\" </a>	.\" </a>
section on UTF-8 support	validity of UTF-8 strings
.\"	.\"
in the main	in the
.\" HREF	.\" HREF
\fBpcre\fP	\fBpcreunicode\fP
.\"	.\"
page. If an invalid UTF-8 sequence of bytes is found, \fBpcre_exec()\fP returns	page. If an invalid sequence of bytes is found, \fBpcre_exec()\fP returns the
the error PCRE_ERROR_BADUTF8 or, if PCRE_PARTIAL_HARD is set and the problem is	error PCRE_ERROR_BADUTF8 or, if PCRE_PARTIAL_HARD is set and the problem is a
a truncated UTF-8 character at the end of the subject, PCRE_ERROR_SHORTUTF8. In	truncated character at the end of the subject, PCRE_ERROR_SHORTUTF8. In both
both cases, information about the precise nature of the error may also be	cases, information about the precise nature of the error may also be returned
returned (see the descriptions of these errors in the section entitled \fIError	(see the descriptions of these errors in the section entitled \fIError return
return values from\fP \fBpcre_exec()\fP	values from\fP \fBpcre_exec()\fP
.\" HTML <a href="#errorlist">	.\" HTML <a href="#errorlist">
.\" </a>	.\" </a>
below).	below).
Line 1711 checks for performance reasons, you can set the PCRE_N	Line 1971 checks for performance reasons, you can set the PCRE_N
calling \fBpcre_exec()\fP. You might want to do this for the second and	calling \fBpcre_exec()\fP. You might want to do this for the second and
subsequent calls to \fBpcre_exec()\fP if you are making repeated calls to find	subsequent calls to \fBpcre_exec()\fP if you are making repeated calls to find
all the matches in a single subject string. However, you should be sure that	all the matches in a single subject string. However, you should be sure that
the value of \fIstartoffset\fP points to the start of a UTF-8 character (or the	the value of \fIstartoffset\fP points to the start of a character (or the end
end of the subject). When PCRE_NO_UTF8_CHECK is set, the effect of passing an	of the subject). When PCRE_NO_UTF8_CHECK is set, the effect of passing an
invalid UTF-8 string as a subject or an invalid value of \fIstartoffset\fP is	invalid string as a subject or an invalid value of \fIstartoffset\fP is
undefined. Your program may crash.	undefined. Your program may crash or loop.
.sp	.sp
PCRE_PARTIAL_HARD	PCRE_PARTIAL_HARD
PCRE_PARTIAL_SOFT	PCRE_PARTIAL_SOFT
Line 1748 documentation.	Line 2008 documentation.
.rs	.rs
.sp	.sp
The subject string is passed to \fBpcre_exec()\fP as a pointer in	The subject string is passed to \fBpcre_exec()\fP as a pointer in
\fIsubject\fP, a length (in bytes) in \fIlength\fP, and a starting byte offset	\fIsubject\fP, a length in \fIlength\fP, and a starting offset in
in \fIstartoffset\fP. If this is negative or greater than the length of the	\fIstartoffset\fP. The units for \fIlength\fP and \fIstartoffset\fP are bytes
subject, \fBpcre_exec()\fP returns PCRE_ERROR_BADOFFSET. When the starting	for the 8-bit library, 16-bit data items for the 16-bit library, and 32-bit
offset is zero, the search for a match starts at the beginning of the subject,	data items for the 32-bit library.
and this is by far the most common case. In UTF-8 mode, the byte offset must
point to the start of a UTF-8 character (or the end of the subject). Unlike the
pattern string, the subject may contain binary zero bytes.
.P	.P
	If \fIstartoffset\fP is negative or greater than the length of the subject,
	\fBpcre_exec()\fP returns PCRE_ERROR_BADOFFSET. When the starting offset is
	zero, the search for a match starts at the beginning of the subject, and this
	is by far the most common case. In UTF-8 or UTF-16 mode, the offset must point
	to the start of a character, or the end of the subject (in UTF-32 mode, one
	data unit equals one character, so all offsets are valid). Unlike the pattern
	string, the subject may contain binary zeroes.
	.P
A non-zero starting offset is useful when searching for another match in the	A non-zero starting offset is useful when searching for another match in the
same subject by calling \fBpcre_exec()\fP again after a previous success.	same subject by calling \fBpcre_exec()\fP again after a previous success.
Setting \fIstartoffset\fP differs from just passing over a shortened string and	Setting \fIstartoffset\fP differs from just passing over a shortened string and
Line 1818 rounded down.	Line 2083 rounded down.
When a match is successful, information about captured substrings is returned	When a match is successful, information about captured substrings is returned
in pairs of integers, starting at the beginning of \fIovector\fP, and	in pairs of integers, starting at the beginning of \fIovector\fP, and
continuing up to two-thirds of its length at the most. The first element of	continuing up to two-thirds of its length at the most. The first element of
each pair is set to the byte offset of the first character in a substring, and	each pair is set to the offset of the first character in a substring, and the
the second is set to the byte offset of the first character after the end of a	second is set to the offset of the first character after the end of a
substring. \fBNote\fP: these values are always byte offsets, even in UTF-8	substring. These values are always data unit offsets, even in UTF mode. They
mode. They are not character counts.	are byte offsets in the 8-bit library, 16-bit data item offsets in the 16-bit
	library, and 32-bit data item offsets in the 32-bit library. \fBNote\fP: they
	are not character counts.
.P	.P
The first pair of integers, \fIovector[0]\fP and \fIovector[1]\fP, identify the	The first pair of integers, \fIovector[0]\fP and \fIovector[1]\fP, identify the
portion of the subject string matched by the entire pattern. The next pair is	portion of the subject string matched by the entire pattern. The next pair is
Line 1836 string that it matched that is returned.	Line 2103 string that it matched that is returned.
.P	.P
If the vector is too small to hold all the captured substring offsets, it is	If the vector is too small to hold all the captured substring offsets, it is
used as far as possible (up to two-thirds of its length), and the function	used as far as possible (up to two-thirds of its length), and the function
returns a value of zero. If neither the actual string matched not any captured	returns a value of zero. If neither the actual string matched nor any captured
substrings are of interest, \fBpcre_exec()\fP may be called with \fIovector\fP	substrings are of interest, \fBpcre_exec()\fP may be called with \fIovector\fP
passed as NULL and \fIovecsize\fP as zero. However, if the pattern contains	passed as NULL and \fIovecsize\fP as zero. However, if the pattern contains
back references and the \fIovector\fP is not big enough to remember the related	back references and the \fIovector\fP is not big enough to remember the related
Line 2036 time.	Line 2303 time.
.sp	.sp
PCRE_ERROR_JIT_STACKLIMIT (-27)	PCRE_ERROR_JIT_STACKLIMIT (-27)
.sp	.sp
This error is returned when a pattern that was successfully studied using the	This error is returned when a pattern that was successfully studied using a
PCRE_STUDY_JIT_COMPILE option is being matched, but the memory available for	JIT compile option is being matched, but the memory available for the
the just-in-time processing stack is not large enough. See the	just-in-time processing stack is not large enough. See the
.\" HREF	.\" HREF
\fBpcrejit\fP	\fBpcrejit\fP
.\"	.\"
documentation for more details.	documentation for more details.
	.sp
	PCRE_ERROR_BADMODE (-28)
	.sp
	This error is given if a pattern that was compiled by the 8-bit library is
	passed to a 16-bit or 32-bit library function, or vice versa.
	.sp
	PCRE_ERROR_BADENDIANNESS (-29)
	.sp
	This error is given if a pattern that was compiled and saved is reloaded on a
	host with different endianness. The utility function
	\fBpcre_pattern_to_host_byte_order()\fP can be used to convert such a pattern
	so that it runs on the new host.
	.sp
	PCRE_ERROR_JIT_BADOPTION
	.sp
	This error is returned when a pattern that was successfully studied using a JIT
	compile option is being matched, but the matching mode (partial or complete
	match) does not correspond to any JIT compilation mode. When the JIT fast path
	function is used, this error may be also given for invalid options. See the
	.\" HREF
	\fBpcrejit\fP
	.\"
	documentation for more details.
	.sp
	PCRE_ERROR_BADLENGTH (-32)
	.sp
	This error is given if \fBpcre_exec()\fP is called with a negative value for
	the \fIlength\fP argument.
.P	.P
Error numbers -16 to -20 and -22 are not used by \fBpcre_exec()\fP.	Error numbers -16 to -20, -22, and 30 are not used by \fBpcre_exec()\fP.
.	.
.	.
.\" HTML <a name="badutf8reasons"></a>	.\" HTML <a name="badutf8reasons"></a>
.SS "Reason codes for invalid UTF-8 strings"	.SS "Reason codes for invalid UTF-8 strings"
.rs	.rs
.sp	.sp
	This section applies only to the 8-bit library. The corresponding information
	for the 16-bit and 32-bit libraries is given in the
	.\" HREF
	\fBpcre16\fP
	.\"
	and
	.\" HREF
	\fBpcre32\fP
	.\"
	pages.
	.P
When \fBpcre_exec()\fP returns either PCRE_ERROR_BADUTF8 or	When \fBpcre_exec()\fP returns either PCRE_ERROR_BADUTF8 or
PCRE_ERROR_SHORTUTF8, and the size of the output vector (\fIovecsize\fP) is at	PCRE_ERROR_SHORTUTF8, and the size of the output vector (\fIovecsize\fP) is at
least 2, the offset of the start of the invalid UTF-8 character is placed in	least 2, the offset of the start of the invalid UTF-8 character is placed in
Line 2119 character.	Line 2425 character.
.sp	.sp
The first byte of a character has the value 0xfe or 0xff. These values can	The first byte of a character has the value 0xfe or 0xff. These values can
never occur in a valid UTF-8 string.	never occur in a valid UTF-8 string.
	.sp
	PCRE_UTF8_ERR22
	.sp
	This error code was formerly used when the presence of a so-called
	"non-character" caused an error. Unicode corrigendum #9 makes it clear that
	such characters should not cause a string to be rejected, and so this code is
	no longer in use and is never returned.
.	.
.	.
.SH "EXTRACTING CAPTURED SUBSTRINGS BY NUMBER"	.SH "EXTRACTING CAPTURED SUBSTRINGS BY NUMBER"
.rs	.rs
.sp	.sp
	.nf
.B int pcre_copy_substring(const char \fIsubject\fP, int \fIovector\fP,	.B int pcre_copy_substring(const char \fIsubject\fP, int \fIovector\fP,
.ti +5n	.B " int \fIstringcount\fP, int \fIstringnumber\fP, char *\fIbuffer\fP,"
.B int \fIstringcount\fP, int \fIstringnumber\fP, char *\fIbuffer\fP,	.B " int \fIbuffersize\fP);"
.ti +5n	.sp
.B int \fIbuffersize\fP);
.PP
.B int pcre_get_substring(const char \fIsubject\fP, int \fIovector\fP,	.B int pcre_get_substring(const char \fIsubject\fP, int \fIovector\fP,
.ti +5n	.B " int \fIstringcount\fP, int \fIstringnumber\fP,"
.B int \fIstringcount\fP, int \fIstringnumber\fP,	.B " const char **\fIstringptr\fP);"
.ti +5n	.sp
.B const char **\fIstringptr\fP);
.PP
.B int pcre_get_substring_list(const char *\fIsubject\fP,	.B int pcre_get_substring_list(const char *\fIsubject\fP,
.ti +5n	.B " int \fIovector\fP, int \fIstringcount\fP, const char **\fIlistptr\fP);"
.B int \fIovector\fP, int \fIstringcount\fP, "const char **\fIlistptr\fP);"	.PP
.PP	.PP
Captured substrings can be accessed directly by using the offsets returned by	Captured substrings can be accessed directly by using the offsets returned by
\fBpcre_exec()\fP in \fIovector\fP. For convenience, the functions	\fBpcre_exec()\fP in \fIovector\fP. For convenience, the functions
Line 2217 provided.	Line 2527 provided.
.SH "EXTRACTING CAPTURED SUBSTRINGS BY NAME"	.SH "EXTRACTING CAPTURED SUBSTRINGS BY NAME"
.rs	.rs
.sp	.sp
	.nf
.B int pcre_get_stringnumber(const pcre *\fIcode\fP,	.B int pcre_get_stringnumber(const pcre *\fIcode\fP,
.ti +5n	.B " const char *\fIname\fP);"
.B const char *\fIname\fP);	.B int pcre_copy_named_substring(const pcre *\fIcode\fP,
.PP
.B int pcre_copy_named_substring(const pcre *\fIcode\fP,	.B int pcre_copy_named_substring(const pcre *\fIcode\fP,
.ti +5n	.B " const char \fIsubject\fP, int \fIovector\fP,"
.B const char \fIsubject\fP, int \fIovector\fP,	.B " int \fIstringcount\fP, const char *\fIstringname\fP,"
.ti +5n	.B " char *\fIbuffer\fP, int \fIbuffersize\fP);"
.B int \fIstringcount\fP, const char *\fIstringname\fP,	.sp
.ti +5n
.B char *\fIbuffer\fP, int \fIbuffersize\fP);
.PP
.B int pcre_get_named_substring(const pcre *\fIcode\fP,	.B int pcre_get_named_substring(const pcre *\fIcode\fP,
.ti +5n	.B " const char \fIsubject\fP, int \fIovector\fP,"
.B const char \fIsubject\fP, int \fIovector\fP,	.B " int \fIstringcount\fP, const char *\fIstringname\fP,"
.ti +5n	.B " const char **\fIstringptr\fP);"
.B int \fIstringcount\fP, const char *\fIstringname\fP,	.fi
.ti +5n
.B const char **\fIstringptr\fP);
.PP	.PP
To extract a substring by name, you first have to find associated number.	To extract a substring by name, you first have to find associated number.
For example, for this pattern	For example, for this pattern
Line 2287 same number causes an error at compile time.	Line 2592 same number causes an error at compile time.
.SH "DUPLICATE SUBPATTERN NAMES"	.SH "DUPLICATE SUBPATTERN NAMES"
.rs	.rs
.sp	.sp
	.nf
.B int pcre_get_stringtable_entries(const pcre *\fIcode\fP,	.B int pcre_get_stringtable_entries(const pcre *\fIcode\fP,
.ti +5n	.B " const char \fIname\fP, char \fIfirst\fP, char *\fIlast\fP);"
.B const char \fIname\fP, char \fIfirst\fP, char *\fIlast\fP);	.PP
.PP	.PP
When a pattern is compiled with the PCRE_DUPNAMES option, names for subpatterns	When a pattern is compiled with the PCRE_DUPNAMES option, names for subpatterns
are not required to be unique. (Duplicate names are always allowed for	are not required to be unique. (Duplicate names are always allowed for
Line 2348 other alternatives. Ultimately, when it runs out of ma	Line 2654 other alternatives. Ultimately, when it runs out of ma
will yield PCRE_ERROR_NOMATCH.	will yield PCRE_ERROR_NOMATCH.
.	.
.	.
	.SH "OBTAINING AN ESTIMATE OF STACK USAGE"
	.rs
	.sp
	Matching certain patterns using \fBpcre_exec()\fP can use a lot of process
	stack, which in certain environments can be rather limited in size. Some users
	find it helpful to have an estimate of the amount of stack that is used by
	\fBpcre_exec()\fP, to help them set recursion limits, as described in the
	.\" HREF
	\fBpcrestack\fP
	.\"
	documentation. The estimate that is output by \fBpcretest\fP when called with
	the \fB-m\fP and \fB-C\fP options is obtained by calling \fBpcre_exec\fP with
	the values NULL, NULL, NULL, -999, and -999 for its first five arguments.
	.P
	Normally, if its first argument is NULL, \fBpcre_exec()\fP immediately returns
	the negative error code PCRE_ERROR_NULL, but with this special combination of
	arguments, it returns instead a negative number whose absolute value is the
	approximate stack frame size in bytes. (A negative number is used so that it is
	clear that no match has happened.) The value is approximate because in some
	cases, recursive calls to \fBpcre_exec()\fP occur when there are one or two
	additional variables on the stack.
	.P
	If PCRE has been compiled to use the heap instead of the stack for recursion,
	the value returned is the size of each block that is obtained from the heap.
	.
	.
.\" HTML <a name="dfamatch"></a>	.\" HTML <a name="dfamatch"></a>
.SH "MATCHING A PATTERN: THE ALTERNATIVE FUNCTION"	.SH "MATCHING A PATTERN: THE ALTERNATIVE FUNCTION"
.rs	.rs
.sp	.sp
	.nf
.B int pcre_dfa_exec(const pcre \fIcode\fP, "const pcre_extra \fIextra\fP,"	.B int pcre_dfa_exec(const pcre \fIcode\fP, "const pcre_extra \fIextra\fP,"
.ti +5n	.B " const char *\fIsubject\fP, int \fIlength\fP, int \fIstartoffset\fP,"
.B "const char *\fIsubject\fP," int \fIlength\fP, int \fIstartoffset\fP,	.B " int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP,"
.ti +5n	.B " int *\fIworkspace\fP, int \fIwscount\fP);"
.B int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP,	.fi
.ti +5n
.B int *\fIworkspace\fP, int \fIwscount\fP);
.P	.P
The function \fBpcre_dfa_exec()\fP is called to match a subject string against	The function \fBpcre_dfa_exec()\fP is called to match a subject string against
a compiled pattern, using a matching algorithm that scans the subject string	a compiled pattern, using a matching algorithm that scans the subject string
Line 2485 matching string is given first. If there were too many	Line 2816 matching string is given first. If there were too many
\fIovector\fP, the yield of the function is zero, and the vector is filled with	\fIovector\fP, the yield of the function is zero, and the vector is filled with
the longest matches. Unlike \fBpcre_exec()\fP, \fBpcre_dfa_exec()\fP can use	the longest matches. Unlike \fBpcre_exec()\fP, \fBpcre_dfa_exec()\fP can use
the entire \fIovector\fP for returning matched strings.	the entire \fIovector\fP for returning matched strings.
	.P
	NOTE: PCRE's "auto-possessification" optimization usually applies to character
	repeats at the end of a pattern (as well as internally). For example, the
	pattern "a\ed+" is compiled as if it were "a\ed++" because there is no point
	even considering the possibility of backtracking into the repeated digits. For
	DFA matching, this means that only one possible match is found. If you really
	do want multiple matches in such cases, either use an ungreedy repeat
	("a\ed+?") or set the PCRE_NO_AUTO_POSSESS option when compiling.
.	.
.	.
.SS "Error returns from \fBpcre_dfa_exec()\fP"	.SS "Error returns from \fBpcre_dfa_exec()\fP"
Line 2529 When a recursive subpattern is processed, the matching	Line 2868 When a recursive subpattern is processed, the matching
recursively, using private vectors for \fIovector\fP and \fIworkspace\fP. This	recursively, using private vectors for \fIovector\fP and \fIworkspace\fP. This
error is given if the output vector is not large enough. This should be	error is given if the output vector is not large enough. This should be
extremely rare, as a vector of size 1000 is used.	extremely rare, as a vector of size 1000 is used.
	.sp
	PCRE_ERROR_DFA_BADRESTART (-30)
	.sp
	When \fBpcre_dfa_exec()\fP is called with the \fBPCRE_DFA_RESTART\fP option,
	some plausibility checks are made on the contents of the workspace, which
	should contain data about the previous partial match. If any of these checks
	fail, this error is given.
.	.
.	.
.SH "SEE ALSO"	.SH "SEE ALSO"
.rs	.rs
.sp	.sp
\fBpcrebuild\fP(3), \fBpcrecallout\fP(3), \fBpcrecpp(3)\fP(3),	\fBpcre16\fP(3), \fBpcre32\fP(3), \fBpcrebuild\fP(3), \fBpcrecallout\fP(3),
\fBpcrematching\fP(3), \fBpcrepartial\fP(3), \fBpcreposix\fP(3),	\fBpcrecpp(3)\fP(3), \fBpcrematching\fP(3), \fBpcrepartial\fP(3),
\fBpcreprecompile\fP(3), \fBpcresample\fP(3), \fBpcrestack\fP(3).	\fBpcreposix\fP(3), \fBpcreprecompile\fP(3), \fBpcresample\fP(3),
	\fBpcrestack\fP(3).
.	.
.	.
.SH AUTHOR	.SH AUTHOR
Line 2553 Cambridge CB2 3QH, England.	Line 2900 Cambridge CB2 3QH, England.
.rs	.rs
.sp	.sp
.nf	.nf
Last updated: 02 December 2011	Last updated: 12 November 2013
Copyright (c) 1997-2011 University of Cambridge.	Copyright (c) 1997-2013 University of Cambridge.
.fi	.fi

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>

Removed from v.1.1
changed lines
	Added in v.1.1.1.5