Merge branch 'merge-pcre' into 10.1
This commit is contained in:
commit
d233fd14a3
@ -8,7 +8,7 @@ Email domain: cam.ac.uk
|
|||||||
University of Cambridge Computing Service,
|
University of Cambridge Computing Service,
|
||||||
Cambridge, England.
|
Cambridge, England.
|
||||||
|
|
||||||
Copyright (c) 1997-2019 University of Cambridge
|
Copyright (c) 1997-2020 University of Cambridge
|
||||||
All rights reserved
|
All rights reserved
|
||||||
|
|
||||||
|
|
||||||
@ -19,7 +19,7 @@ Written by: Zoltan Herczeg
|
|||||||
Email local part: hzmester
|
Email local part: hzmester
|
||||||
Emain domain: freemail.hu
|
Emain domain: freemail.hu
|
||||||
|
|
||||||
Copyright(c) 2010-2019 Zoltan Herczeg
|
Copyright(c) 2010-2020 Zoltan Herczeg
|
||||||
All rights reserved.
|
All rights reserved.
|
||||||
|
|
||||||
|
|
||||||
@ -30,7 +30,7 @@ Written by: Zoltan Herczeg
|
|||||||
Email local part: hzmester
|
Email local part: hzmester
|
||||||
Emain domain: freemail.hu
|
Emain domain: freemail.hu
|
||||||
|
|
||||||
Copyright(c) 2009-2019 Zoltan Herczeg
|
Copyright(c) 2009-2020 Zoltan Herczeg
|
||||||
All rights reserved.
|
All rights reserved.
|
||||||
|
|
||||||
|
|
||||||
|
@ -5,6 +5,35 @@ Note that the PCRE 8.xx series (PCRE1) is now in a bugfix-only state. All
|
|||||||
development is happening in the PCRE2 10.xx series.
|
development is happening in the PCRE2 10.xx series.
|
||||||
|
|
||||||
|
|
||||||
|
Version 8.44 12 February-2020
|
||||||
|
-----------------------------
|
||||||
|
|
||||||
|
1. Setting --enable-jit=auto for an out-of-tree build failed because the
|
||||||
|
source directory wasn't in the search path for AC_TRY_COMPILE always. Patch
|
||||||
|
from Ross Burton.
|
||||||
|
|
||||||
|
2. Applied a patch from Michael Shigorin to fix 8.43 build on e2k arch
|
||||||
|
with lcc compiler (EDG frontend based); the problem it fixes is:
|
||||||
|
|
||||||
|
lcc: "pcrecpp.cc", line 74: error: declaration aliased to undefined entity
|
||||||
|
"_ZN7pcrecpp2RE6no_argE" [-Werror]
|
||||||
|
|
||||||
|
3. Change 2 for 8.43 omitted (*LF) from the list of start-of-pattern items. Now
|
||||||
|
added.
|
||||||
|
|
||||||
|
4. Fix ARMv5 JIT improper handling of labels right after a constant pool.
|
||||||
|
|
||||||
|
5. Small patch to pcreposix.c to set the erroroffset field to -1 immediately
|
||||||
|
after a successful compile, instead of at the start of matching to avoid a
|
||||||
|
sanitizer complaint (regexec is supposed to be thread safe).
|
||||||
|
|
||||||
|
6. Check the size of the number after (?C as it is read, in order to avoid
|
||||||
|
integer overflow.
|
||||||
|
|
||||||
|
7. Tidy up left shifts to avoid sanitize warnings; also fix one NULL deference
|
||||||
|
in pcretest.
|
||||||
|
|
||||||
|
|
||||||
Version 8.43 23-February-2019
|
Version 8.43 23-February-2019
|
||||||
-----------------------------
|
-----------------------------
|
||||||
|
|
||||||
|
@ -25,7 +25,7 @@ Email domain: cam.ac.uk
|
|||||||
University of Cambridge Computing Service,
|
University of Cambridge Computing Service,
|
||||||
Cambridge, England.
|
Cambridge, England.
|
||||||
|
|
||||||
Copyright (c) 1997-2019 University of Cambridge
|
Copyright (c) 1997-2020 University of Cambridge
|
||||||
All rights reserved.
|
All rights reserved.
|
||||||
|
|
||||||
|
|
||||||
@ -36,7 +36,7 @@ Written by: Zoltan Herczeg
|
|||||||
Email local part: hzmester
|
Email local part: hzmester
|
||||||
Email domain: freemail.hu
|
Email domain: freemail.hu
|
||||||
|
|
||||||
Copyright(c) 2010-2019 Zoltan Herczeg
|
Copyright(c) 2010-2020 Zoltan Herczeg
|
||||||
All rights reserved.
|
All rights reserved.
|
||||||
|
|
||||||
|
|
||||||
@ -47,7 +47,7 @@ Written by: Zoltan Herczeg
|
|||||||
Email local part: hzmester
|
Email local part: hzmester
|
||||||
Email domain: freemail.hu
|
Email domain: freemail.hu
|
||||||
|
|
||||||
Copyright(c) 2009-2019 Zoltan Herczeg
|
Copyright(c) 2009-2020 Zoltan Herczeg
|
||||||
All rights reserved.
|
All rights reserved.
|
||||||
|
|
||||||
|
|
||||||
|
@ -5,6 +5,12 @@ Note that this library (now called PCRE1) is now being maintained for bug fixes
|
|||||||
only. New projects are advised to use the new PCRE2 libraries.
|
only. New projects are advised to use the new PCRE2 libraries.
|
||||||
|
|
||||||
|
|
||||||
|
Release 8.44 12-February-2020
|
||||||
|
-----------------------------
|
||||||
|
|
||||||
|
This is a bug-fix release.
|
||||||
|
|
||||||
|
|
||||||
Release 8.43 23-February-2019
|
Release 8.43 23-February-2019
|
||||||
-----------------------------
|
-----------------------------
|
||||||
|
|
||||||
|
@ -13,9 +13,10 @@ libraries.
|
|||||||
The latest release of PCRE1 is always available in three alternative formats
|
The latest release of PCRE1 is always available in three alternative formats
|
||||||
from:
|
from:
|
||||||
|
|
||||||
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-xxx.tar.gz
|
https://ftp.pcre.org/pub/pcre/pcre-x.xx.tar.gz
|
||||||
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-xxx.tar.bz2
|
https://ftp.pcre.org/pub/pcre/pcre-x.xx.tar.bz2
|
||||||
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-xxx.zip
|
https://ftp.pcre.org/pub/pcre/pcre-x.xx.tar.zip
|
||||||
|
|
||||||
|
|
||||||
There is a mailing list for discussion about the development of PCRE at
|
There is a mailing list for discussion about the development of PCRE at
|
||||||
pcre-dev@exim.org. You can access the archives and subscribe or manage your
|
pcre-dev@exim.org. You can access the archives and subscribe or manage your
|
||||||
@ -999,4 +1000,4 @@ pcre_xxx, one with the name pcre16_xx, and a third with the name pcre32_xxx.
|
|||||||
Philip Hazel
|
Philip Hazel
|
||||||
Email local part: ph10
|
Email local part: ph10
|
||||||
Email domain: cam.ac.uk
|
Email domain: cam.ac.uk
|
||||||
Last updated: 10 February 2015
|
Last updated: 12 February 2020
|
||||||
|
@ -9,19 +9,19 @@ dnl The PCRE_PRERELEASE feature is for identifying release candidates. It might
|
|||||||
dnl be defined as -RC2, for example. For real releases, it should be empty.
|
dnl be defined as -RC2, for example. For real releases, it should be empty.
|
||||||
|
|
||||||
m4_define(pcre_major, [8])
|
m4_define(pcre_major, [8])
|
||||||
m4_define(pcre_minor, [43])
|
m4_define(pcre_minor, [44])
|
||||||
m4_define(pcre_prerelease, [])
|
m4_define(pcre_prerelease, [])
|
||||||
m4_define(pcre_date, [2019-02-23])
|
m4_define(pcre_date, [2020-02-12])
|
||||||
|
|
||||||
# NOTE: The CMakeLists.txt file searches for the above variables in the first
|
# NOTE: The CMakeLists.txt file searches for the above variables in the first
|
||||||
# 50 lines of this file. Please update that if the variables above are moved.
|
# 50 lines of this file. Please update that if the variables above are moved.
|
||||||
|
|
||||||
# Libtool shared library interface versions (current:revision:age)
|
# Libtool shared library interface versions (current:revision:age)
|
||||||
m4_define(libpcre_version, [3:11:2])
|
m4_define(libpcre_version, [3:12:2])
|
||||||
m4_define(libpcre16_version, [2:11:2])
|
m4_define(libpcre16_version, [2:12:2])
|
||||||
m4_define(libpcre32_version, [0:11:0])
|
m4_define(libpcre32_version, [0:12:0])
|
||||||
m4_define(libpcreposix_version, [0:6:0])
|
m4_define(libpcreposix_version, [0:7:0])
|
||||||
m4_define(libpcrecpp_version, [0:1:0])
|
m4_define(libpcrecpp_version, [0:2:0])
|
||||||
|
|
||||||
AC_PREREQ(2.57)
|
AC_PREREQ(2.57)
|
||||||
AC_INIT(PCRE, pcre_major.pcre_minor[]pcre_prerelease, , pcre)
|
AC_INIT(PCRE, pcre_major.pcre_minor[]pcre_prerelease, , pcre)
|
||||||
@ -159,12 +159,15 @@ AC_ARG_ENABLE(jit,
|
|||||||
|
|
||||||
if test "$enable_jit" = "auto"; then
|
if test "$enable_jit" = "auto"; then
|
||||||
AC_LANG(C)
|
AC_LANG(C)
|
||||||
|
SAVE_CPPFLAGS=$CPPFLAGS
|
||||||
|
CPPFLAGS=-I$srcdir
|
||||||
AC_COMPILE_IFELSE([AC_LANG_SOURCE([[
|
AC_COMPILE_IFELSE([AC_LANG_SOURCE([[
|
||||||
#define SLJIT_CONFIG_AUTO 1
|
#define SLJIT_CONFIG_AUTO 1
|
||||||
#include "sljit/sljitConfigInternal.h"
|
#include "sljit/sljitConfigInternal.h"
|
||||||
#if (defined SLJIT_CONFIG_UNSUPPORTED && SLJIT_CONFIG_UNSUPPORTED)
|
#if (defined SLJIT_CONFIG_UNSUPPORTED && SLJIT_CONFIG_UNSUPPORTED)
|
||||||
#error unsupported
|
#error unsupported
|
||||||
#endif]])], enable_jit=yes, enable_jit=no)
|
#endif]])], enable_jit=yes, enable_jit=no)
|
||||||
|
CPPFLAGS=$SAVE_CPPFLAGS
|
||||||
fi
|
fi
|
||||||
|
|
||||||
# Handle --disable-pcregrep-jit (enabled by default)
|
# Handle --disable-pcregrep-jit (enabled by default)
|
||||||
|
@ -13,9 +13,10 @@ libraries.
|
|||||||
The latest release of PCRE1 is always available in three alternative formats
|
The latest release of PCRE1 is always available in three alternative formats
|
||||||
from:
|
from:
|
||||||
|
|
||||||
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-xxx.tar.gz
|
https://ftp.pcre.org/pub/pcre/pcre-x.xx.tar.gz
|
||||||
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-xxx.tar.bz2
|
https://ftp.pcre.org/pub/pcre/pcre-x.xx.tar.bz2
|
||||||
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-xxx.zip
|
https://ftp.pcre.org/pub/pcre/pcre-x.xx.tar.zip
|
||||||
|
|
||||||
|
|
||||||
There is a mailing list for discussion about the development of PCRE at
|
There is a mailing list for discussion about the development of PCRE at
|
||||||
pcre-dev@exim.org. You can access the archives and subscribe or manage your
|
pcre-dev@exim.org. You can access the archives and subscribe or manage your
|
||||||
@ -999,4 +1000,4 @@ pcre_xxx, one with the name pcre16_xx, and a third with the name pcre32_xxx.
|
|||||||
Philip Hazel
|
Philip Hazel
|
||||||
Email local part: ph10
|
Email local part: ph10
|
||||||
Email domain: cam.ac.uk
|
Email domain: cam.ac.uk
|
||||||
Last updated: 10 February 2015
|
Last updated: 12 February 2020
|
||||||
|
@ -143,7 +143,7 @@ performance.
|
|||||||
One way of guarding against this possibility is to use the
|
One way of guarding against this possibility is to use the
|
||||||
<b>pcre_fullinfo()</b> function to check the compiled pattern's options for UTF.
|
<b>pcre_fullinfo()</b> function to check the compiled pattern's options for UTF.
|
||||||
Alternatively, from release 8.33, you can set the PCRE_NEVER_UTF option at
|
Alternatively, from release 8.33, you can set the PCRE_NEVER_UTF option at
|
||||||
compile time. This causes an compile time error if a pattern contains a
|
compile time. This causes a compile time error if a pattern contains a
|
||||||
UTF-setting sequence.
|
UTF-setting sequence.
|
||||||
</P>
|
</P>
|
||||||
<P>
|
<P>
|
||||||
|
@ -1246,7 +1246,7 @@ the following negative numbers:
|
|||||||
PCRE_ERROR_BADOPTION the value of <i>what</i> was invalid
|
PCRE_ERROR_BADOPTION the value of <i>what</i> was invalid
|
||||||
PCRE_ERROR_UNSET the requested field is not set
|
PCRE_ERROR_UNSET the requested field is not set
|
||||||
</pre>
|
</pre>
|
||||||
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 a simple
|
||||||
check against passing an arbitrary memory pointer. The endianness error can
|
check against passing an arbitrary memory pointer. The endianness error can
|
||||||
occur if a compiled pattern is saved and reloaded on a different host. Here is
|
occur if a compiled pattern is saved and reloaded on a different host. Here is
|
||||||
a typical call of <b>pcre_fullinfo()</b>, to obtain the length of the compiled
|
a typical call of <b>pcre_fullinfo()</b>, to obtain the length of the compiled
|
||||||
@ -1318,7 +1318,7 @@ returned. For anchored patterns, -2 is returned.
|
|||||||
</pre>
|
</pre>
|
||||||
Return the value of the first data unit (non-UTF character) of any matched
|
Return the value of the first data unit (non-UTF character) of any matched
|
||||||
string in the situation where PCRE_INFO_FIRSTCHARACTERFLAGS returns 1;
|
string in the situation where PCRE_INFO_FIRSTCHARACTERFLAGS returns 1;
|
||||||
otherwise return 0. The fourth argument should point to an <b>uint_t</b>
|
otherwise return 0. The fourth argument should point to a <b>uint_t</b>
|
||||||
variable.
|
variable.
|
||||||
</P>
|
</P>
|
||||||
<P>
|
<P>
|
||||||
@ -1577,7 +1577,7 @@ returned value 1 (with "z" returned from PCRE_INFO_REQUIREDCHAR), but for
|
|||||||
</pre>
|
</pre>
|
||||||
Return the value of the rightmost literal data unit that must exist in any
|
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
|
matched string, other than at its start, if such a value has been recorded. The
|
||||||
fourth argument should point to an <b>uint32_t</b> variable. If there is no such
|
fourth argument should point to a <b>uint32_t</b> variable. If there is no such
|
||||||
value, 0 is returned.
|
value, 0 is returned.
|
||||||
</P>
|
</P>
|
||||||
<br><a name="SEC16" href="#TOC1">REFERENCE COUNTS</a><br>
|
<br><a name="SEC16" href="#TOC1">REFERENCE COUNTS</a><br>
|
||||||
|
@ -99,23 +99,21 @@ the 16-bit library, or <b>pcre32_xx</b> when using the 32-bit library".
|
|||||||
<br><a name="SEC4" href="#TOC1">COMMAND LINE OPTIONS</a><br>
|
<br><a name="SEC4" href="#TOC1">COMMAND LINE OPTIONS</a><br>
|
||||||
<P>
|
<P>
|
||||||
<b>-8</b>
|
<b>-8</b>
|
||||||
If both the 8-bit library has been built, this option causes the 8-bit library
|
If the 8-bit library has been built, this option causes it to be used (this is
|
||||||
to be used (which is the default); if the 8-bit library has not been built,
|
the default). If the 8-bit library has not been built, this option causes an
|
||||||
this option causes an error.
|
error.
|
||||||
</P>
|
</P>
|
||||||
<P>
|
<P>
|
||||||
<b>-16</b>
|
<b>-16</b>
|
||||||
If both the 8-bit or the 32-bit, and the 16-bit libraries have been built, this
|
If the 16-bit library has been built, this option causes it to be used. If only
|
||||||
option causes the 16-bit library to be used. If only the 16-bit library has been
|
the 16-bit library has been built, this is the default. If the 16-bit library
|
||||||
built, this is the default (so has no effect). If only the 8-bit or the 32-bit
|
has not been built, this option causes an error.
|
||||||
library has been built, this option causes an error.
|
|
||||||
</P>
|
</P>
|
||||||
<P>
|
<P>
|
||||||
<b>-32</b>
|
<b>-32</b>
|
||||||
If both the 8-bit or the 16-bit, and the 32-bit libraries have been built, this
|
If the 32-bit library has been built, this option causes it to be used. If only
|
||||||
option causes the 32-bit library to be used. If only the 32-bit library has been
|
the 32-bit library has been built, this is the default. If the 32-bit library
|
||||||
built, this is the default (so has no effect). If only the 8-bit or the 16-bit
|
has not been built, this option causes an error.
|
||||||
library has been built, this option causes an error.
|
|
||||||
</P>
|
</P>
|
||||||
<P>
|
<P>
|
||||||
<b>-b</b>
|
<b>-b</b>
|
||||||
@ -1154,9 +1152,9 @@ Cambridge CB2 3QH, England.
|
|||||||
</P>
|
</P>
|
||||||
<br><a name="SEC17" href="#TOC1">REVISION</a><br>
|
<br><a name="SEC17" href="#TOC1">REVISION</a><br>
|
||||||
<P>
|
<P>
|
||||||
Last updated: 23 February 2017
|
Last updated: 10 February 2020
|
||||||
<br>
|
<br>
|
||||||
Copyright © 1997-2017 University of Cambridge.
|
Copyright © 1997-2020 University of Cambridge.
|
||||||
<br>
|
<br>
|
||||||
<p>
|
<p>
|
||||||
Return to the <a href="index.html">PCRE index page</a>.
|
Return to the <a href="index.html">PCRE index page</a>.
|
||||||
|
@ -16,8 +16,8 @@ DESCRIPTION
|
|||||||
|
|
||||||
pcre-config returns the configuration of the installed PCRE libraries
|
pcre-config returns the configuration of the installed PCRE libraries
|
||||||
and the options required to compile a program to use them. Some of the
|
and the options required to compile a program to use them. Some of the
|
||||||
options apply only to the 8-bit, or 16-bit, or 32-bit libraries,
|
options apply only to the 8-bit, or 16-bit, or 32-bit libraries, re-
|
||||||
respectively, and are not available if only one of those libraries has
|
spectively, and are not available if only one of those libraries has
|
||||||
been built. If an unavailable option is encountered, the "usage" infor-
|
been built. If an unavailable option is encountered, the "usage" infor-
|
||||||
mation is output.
|
mation is output.
|
||||||
|
|
||||||
@ -36,37 +36,37 @@ OPTIONS
|
|||||||
--version Writes the version number of the installed PCRE libraries to
|
--version Writes the version number of the installed PCRE libraries to
|
||||||
the standard output.
|
the standard output.
|
||||||
|
|
||||||
--libs Writes to the standard output the command line options
|
--libs Writes to the standard output the command line options re-
|
||||||
required to link with the 8-bit PCRE library (-lpcre on many
|
quired to link with the 8-bit PCRE library (-lpcre on many
|
||||||
systems).
|
systems).
|
||||||
|
|
||||||
--libs16 Writes to the standard output the command line options
|
--libs16 Writes to the standard output the command line options re-
|
||||||
required to link with the 16-bit PCRE library (-lpcre16 on
|
quired to link with the 16-bit PCRE library (-lpcre16 on many
|
||||||
many systems).
|
systems).
|
||||||
|
|
||||||
--libs32 Writes to the standard output the command line options
|
--libs32 Writes to the standard output the command line options re-
|
||||||
required to link with the 32-bit PCRE library (-lpcre32 on
|
quired to link with the 32-bit PCRE library (-lpcre32 on many
|
||||||
many systems).
|
systems).
|
||||||
|
|
||||||
--libs-cpp
|
--libs-cpp
|
||||||
Writes to the standard output the command line options
|
Writes to the standard output the command line options re-
|
||||||
required to link with PCRE's C++ wrapper library (-lpcrecpp
|
quired to link with PCRE's C++ wrapper library (-lpcrecpp
|
||||||
-lpcre on many systems).
|
-lpcre on many systems).
|
||||||
|
|
||||||
--libs-posix
|
--libs-posix
|
||||||
Writes to the standard output the command line options
|
Writes to the standard output the command line options re-
|
||||||
required to link with PCRE's POSIX API wrapper library
|
quired to link with PCRE's POSIX API wrapper library
|
||||||
(-lpcreposix -lpcre on many systems).
|
(-lpcreposix -lpcre on many systems).
|
||||||
|
|
||||||
--cflags Writes to the standard output the command line options
|
--cflags Writes to the standard output the command line options re-
|
||||||
required to compile files that use PCRE (this may include
|
quired to compile files that use PCRE (this may include some
|
||||||
some -I options, but is blank on many systems).
|
-I options, but is blank on many systems).
|
||||||
|
|
||||||
--cflags-posix
|
--cflags-posix
|
||||||
Writes to the standard output the command line options
|
Writes to the standard output the command line options re-
|
||||||
required to compile files that use PCRE's POSIX API wrapper
|
quired to compile files that use PCRE's POSIX API wrapper li-
|
||||||
library (this may include some -I options, but is blank on
|
brary (this may include some -I options, but is blank on many
|
||||||
many systems).
|
systems).
|
||||||
|
|
||||||
|
|
||||||
SEE ALSO
|
SEE ALSO
|
||||||
|
@ -146,7 +146,7 @@ performance.
|
|||||||
One way of guarding against this possibility is to use the
|
One way of guarding against this possibility is to use the
|
||||||
\fBpcre_fullinfo()\fP function to check the compiled pattern's options for UTF.
|
\fBpcre_fullinfo()\fP function to check the compiled pattern's options for UTF.
|
||||||
Alternatively, from release 8.33, you can set the PCRE_NEVER_UTF option at
|
Alternatively, from release 8.33, you can set the PCRE_NEVER_UTF option at
|
||||||
compile time. This causes an compile time error if a pattern contains a
|
compile time. This causes a compile time error if a pattern contains a
|
||||||
UTF-setting sequence.
|
UTF-setting sequence.
|
||||||
.P
|
.P
|
||||||
If your application is one that supports UTF, be aware that validity checking
|
If your application is one that supports UTF, be aware that validity checking
|
||||||
|
3893
pcre/doc/pcre.txt
3893
pcre/doc/pcre.txt
File diff suppressed because it is too large
Load Diff
@ -1227,7 +1227,7 @@ the following negative numbers:
|
|||||||
PCRE_ERROR_BADOPTION the value of \fIwhat\fP was invalid
|
PCRE_ERROR_BADOPTION the value of \fIwhat\fP was invalid
|
||||||
PCRE_ERROR_UNSET the requested field is not set
|
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 a simple
|
||||||
check against passing an arbitrary memory pointer. The endianness error can
|
check against passing an arbitrary memory pointer. The endianness error can
|
||||||
occur if a compiled pattern is saved and reloaded on a different host. Here is
|
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
|
a typical call of \fBpcre_fullinfo()\fP, to obtain the length of the compiled
|
||||||
@ -1294,7 +1294,7 @@ returned. For anchored patterns, -2 is returned.
|
|||||||
.sp
|
.sp
|
||||||
Return the value of the first data unit (non-UTF character) of any matched
|
Return the value of the first data unit (non-UTF character) of any matched
|
||||||
string in the situation where PCRE_INFO_FIRSTCHARACTERFLAGS returns 1;
|
string in the situation where PCRE_INFO_FIRSTCHARACTERFLAGS returns 1;
|
||||||
otherwise return 0. The fourth argument should point to an \fBuint_t\fP
|
otherwise return 0. The fourth argument should point to a \fBuint_t\fP
|
||||||
variable.
|
variable.
|
||||||
.P
|
.P
|
||||||
In the 8-bit library, the value is always less than 256. In the 16-bit library
|
In the 8-bit library, the value is always less than 256. In the 16-bit library
|
||||||
@ -1560,7 +1560,7 @@ returned value 1 (with "z" returned from PCRE_INFO_REQUIREDCHAR), but for
|
|||||||
.sp
|
.sp
|
||||||
Return the value of the rightmost literal data unit that must exist in any
|
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
|
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
|
fourth argument should point to a \fBuint32_t\fP variable. If there is no such
|
||||||
value, 0 is returned.
|
value, 0 is returned.
|
||||||
.
|
.
|
||||||
.
|
.
|
||||||
|
@ -26,8 +26,8 @@ DESCRIPTION
|
|||||||
If you attempt to use delimiters (for example, by surrounding a pattern
|
If you attempt to use delimiters (for example, by surrounding a pattern
|
||||||
with slashes, as is common in Perl scripts), they are interpreted as
|
with slashes, as is common in Perl scripts), they are interpreted as
|
||||||
part of the pattern. Quotes can of course be used to delimit patterns
|
part of the pattern. Quotes can of course be used to delimit patterns
|
||||||
on the command line because they are interpreted by the shell, and
|
on the command line because they are interpreted by the shell, and in-
|
||||||
indeed quotes are required if a pattern contains white space or shell
|
deed quotes are required if a pattern contains white space or shell
|
||||||
metacharacters.
|
metacharacters.
|
||||||
|
|
||||||
The first argument that follows any option settings is treated as the
|
The first argument that follows any option settings is treated as the
|
||||||
@ -37,8 +37,8 @@ DESCRIPTION
|
|||||||
or an argument pattern must be provided.
|
or an argument pattern must be provided.
|
||||||
|
|
||||||
If no files are specified, pcregrep reads the standard input. The stan-
|
If no files are specified, pcregrep reads the standard input. The stan-
|
||||||
dard input can also be referenced by a name consisting of a single
|
dard input can also be referenced by a name consisting of a single hy-
|
||||||
hyphen. For example:
|
phen. For example:
|
||||||
|
|
||||||
pcregrep some-pattern /file1 - /file3
|
pcregrep some-pattern /file1 - /file3
|
||||||
|
|
||||||
@ -47,8 +47,8 @@ DESCRIPTION
|
|||||||
the start of each line, followed by a colon. However, there are options
|
the start of each line, followed by a colon. However, there are options
|
||||||
that can change how pcregrep behaves. In particular, the -M option
|
that can change how pcregrep behaves. In particular, the -M option
|
||||||
makes it possible to search for patterns that span line boundaries.
|
makes it possible to search for patterns that span line boundaries.
|
||||||
What defines a line boundary is controlled by the -N (--newline)
|
What defines a line boundary is controlled by the -N (--newline) op-
|
||||||
option.
|
tion.
|
||||||
|
|
||||||
The amount of memory used for buffering files that are being scanned is
|
The amount of memory used for buffering files that are being scanned is
|
||||||
controlled by a parameter that can be set by the --buffer-size option.
|
controlled by a parameter that can be set by the --buffer-size option.
|
||||||
@ -66,12 +66,12 @@ DESCRIPTION
|
|||||||
By default, as soon as one pattern matches a line, no further patterns
|
By default, as soon as one pattern matches a line, no further patterns
|
||||||
are considered. However, if --colour (or --color) is used to colour the
|
are considered. However, if --colour (or --color) is used to colour the
|
||||||
matching substrings, or if --only-matching, --file-offsets, or --line-
|
matching substrings, or if --only-matching, --file-offsets, or --line-
|
||||||
offsets is used to output only the part of the line that matched
|
offsets is used to output only the part of the line that matched (ei-
|
||||||
(either shown literally, or as an offset), scanning resumes immediately
|
ther shown literally, or as an offset), scanning resumes immediately
|
||||||
following the match, so that further matches on the same line can be
|
following the match, so that further matches on the same line can be
|
||||||
found. If there are multiple patterns, they are all tried on the
|
found. If there are multiple patterns, they are all tried on the re-
|
||||||
remainder of the line, but patterns that follow the one that matched
|
mainder of the line, but patterns that follow the one that matched are
|
||||||
are not tried on the earlier part of the line.
|
not tried on the earlier part of the line.
|
||||||
|
|
||||||
This behaviour means that the order in which multiple patterns are
|
This behaviour means that the order in which multiple patterns are
|
||||||
specified can affect the output when one of the above options is used.
|
specified can affect the output when one of the above options is used.
|
||||||
@ -80,11 +80,11 @@ DESCRIPTION
|
|||||||
overlap).
|
overlap).
|
||||||
|
|
||||||
Patterns that can match an empty string are accepted, but empty string
|
Patterns that can match an empty string are accepted, but empty string
|
||||||
matches are never recognized. An example is the pattern
|
matches are never recognized. An example is the pattern "(su-
|
||||||
"(super)?(man)?", in which all components are optional. This pattern
|
per)?(man)?", in which all components are optional. This pattern finds
|
||||||
finds all occurrences of both "super" and "man"; the output differs
|
all occurrences of both "super" and "man"; the output differs from
|
||||||
from matching with "super|man" when only the matching substrings are
|
matching with "super|man" when only the matching substrings are being
|
||||||
being shown.
|
shown.
|
||||||
|
|
||||||
If the LC_ALL or LC_CTYPE environment variable is set, pcregrep uses
|
If the LC_ALL or LC_CTYPE environment variable is set, pcregrep uses
|
||||||
the value to set a locale when calling the PCRE library. The --locale
|
the value to set a locale when calling the PCRE library. The --locale
|
||||||
@ -105,9 +105,9 @@ BINARY FILES
|
|||||||
|
|
||||||
By default, a file that contains a binary zero byte within the first
|
By default, a file that contains a binary zero byte within the first
|
||||||
1024 bytes is identified as a binary file, and is processed specially.
|
1024 bytes is identified as a binary file, and is processed specially.
|
||||||
(GNU grep also identifies binary files in this manner.) See the
|
(GNU grep also identifies binary files in this manner.) See the --bi-
|
||||||
--binary-files option for a means of changing the way binary files are
|
nary-files option for a means of changing the way binary files are han-
|
||||||
handled.
|
dled.
|
||||||
|
|
||||||
|
|
||||||
OPTIONS
|
OPTIONS
|
||||||
@ -151,16 +151,16 @@ OPTIONS
|
|||||||
|
|
||||||
--binary-files=word
|
--binary-files=word
|
||||||
Specify how binary files are to be processed. If the word is
|
Specify how binary files are to be processed. If the word is
|
||||||
"binary" (the default), pattern matching is performed on
|
"binary" (the default), pattern matching is performed on bi-
|
||||||
binary files, but the only output is "Binary file <name>
|
nary files, but the only output is "Binary file <name>
|
||||||
matches" when a match succeeds. If the word is "text", which
|
matches" when a match succeeds. If the word is "text", which
|
||||||
is equivalent to the -a or --text option, binary files are
|
is equivalent to the -a or --text option, binary files are
|
||||||
processed in the same way as any other file. In this case,
|
processed in the same way as any other file. In this case,
|
||||||
when a match succeeds, the output may be binary garbage,
|
when a match succeeds, the output may be binary garbage,
|
||||||
which can have nasty effects if sent to a terminal. If the
|
which can have nasty effects if sent to a terminal. If the
|
||||||
word is "without-match", which is equivalent to the -I
|
word is "without-match", which is equivalent to the -I op-
|
||||||
option, binary files are not processed at all; they are
|
tion, binary files are not processed at all; they are assumed
|
||||||
assumed not to be of interest.
|
not to be of interest.
|
||||||
|
|
||||||
--buffer-size=number
|
--buffer-size=number
|
||||||
Set the parameter that controls how much memory is used for
|
Set the parameter that controls how much memory is used for
|
||||||
@ -201,15 +201,15 @@ OPTIONS
|
|||||||
ronment variable PCREGREP_COLOUR or PCREGREP_COLOR. The value
|
ronment variable PCREGREP_COLOUR or PCREGREP_COLOR. The value
|
||||||
of this variable should be a string of two numbers, separated
|
of this variable should be a string of two numbers, separated
|
||||||
by a semicolon. They are copied directly into the control
|
by a semicolon. They are copied directly into the control
|
||||||
string for setting colour on a terminal, so it is your
|
string for setting colour on a terminal, so it is your re-
|
||||||
responsibility to ensure that they make sense. If neither of
|
sponsibility to ensure that they make sense. If neither of
|
||||||
the environment variables is set, the default is "1;31",
|
the environment variables is set, the default is "1;31",
|
||||||
which gives red.
|
which gives red.
|
||||||
|
|
||||||
-D action, --devices=action
|
-D action, --devices=action
|
||||||
If an input path is not a regular file or a directory,
|
If an input path is not a regular file or a directory, "ac-
|
||||||
"action" specifies how it is to be processed. Valid values
|
tion" specifies how it is to be processed. Valid values are
|
||||||
are "read" (the default) or "skip" (silently skip the path).
|
"read" (the default) or "skip" (silently skip the path).
|
||||||
|
|
||||||
-d action, --directories=action
|
-d action, --directories=action
|
||||||
If an input path is a directory, "action" specifies how it is
|
If an input path is a directory, "action" specifies how it is
|
||||||
@ -218,8 +218,8 @@ OPTIONS
|
|||||||
"recurse" (equivalent to the -r option), or "skip" (silently
|
"recurse" (equivalent to the -r option), or "skip" (silently
|
||||||
skip the path, the default in Windows environments). In the
|
skip the path, the default in Windows environments). In the
|
||||||
"read" case, directories are read as if they were ordinary
|
"read" case, directories are read as if they were ordinary
|
||||||
files. In some operating systems the effect of reading a
|
files. In some operating systems the effect of reading a di-
|
||||||
directory like this is an immediate end-of-file; in others it
|
rectory like this is an immediate end-of-file; in others it
|
||||||
may provoke an error.
|
may provoke an error.
|
||||||
|
|
||||||
-e pattern, --regex=pattern, --regexp=pattern
|
-e pattern, --regex=pattern, --regexp=pattern
|
||||||
@ -249,8 +249,8 @@ OPTIONS
|
|||||||
whether listed on the command line, obtained from --file-
|
whether listed on the command line, obtained from --file-
|
||||||
list, or by scanning a directory. The pattern is a PCRE regu-
|
list, or by scanning a directory. The pattern is a PCRE regu-
|
||||||
lar expression, and is matched against the final component of
|
lar expression, and is matched against the final component of
|
||||||
the file name, not the entire path. The -F, -w, and -x
|
the file name, not the entire path. The -F, -w, and -x op-
|
||||||
options do not apply to this pattern. The option may be given
|
tions do not apply to this pattern. The option may be given
|
||||||
any number of times in order to specify multiple patterns. If
|
any number of times in order to specify multiple patterns. If
|
||||||
a file name matches both an --include and an --exclude pat-
|
a file name matches both an --include and an --exclude pat-
|
||||||
tern, it is excluded. There is no short form for this option.
|
tern, it is excluded. There is no short form for this option.
|
||||||
@ -264,29 +264,29 @@ OPTIONS
|
|||||||
|
|
||||||
--exclude-dir=pattern
|
--exclude-dir=pattern
|
||||||
Directories whose names match the pattern are skipped without
|
Directories whose names match the pattern are skipped without
|
||||||
being processed, whatever the setting of the --recursive
|
being processed, whatever the setting of the --recursive op-
|
||||||
option. This applies to all directories, whether listed on
|
tion. This applies to all directories, whether listed on the
|
||||||
the command line, obtained from --file-list, or by scanning a
|
command line, obtained from --file-list, or by scanning a
|
||||||
parent directory. The pattern is a PCRE regular expression,
|
parent directory. The pattern is a PCRE regular expression,
|
||||||
and is matched against the final component of the directory
|
and is matched against the final component of the directory
|
||||||
name, not the entire path. The -F, -w, and -x options do not
|
name, not the entire path. The -F, -w, and -x options do not
|
||||||
apply to this pattern. The option may be given any number of
|
apply to this pattern. The option may be given any number of
|
||||||
times in order to specify more than one pattern. If a direc-
|
times in order to specify more than one pattern. If a direc-
|
||||||
tory matches both --include-dir and --exclude-dir, it is
|
tory matches both --include-dir and --exclude-dir, it is ex-
|
||||||
excluded. There is no short form for this option.
|
cluded. There is no short form for this option.
|
||||||
|
|
||||||
-F, --fixed-strings
|
-F, --fixed-strings
|
||||||
Interpret each data-matching pattern as a list of fixed
|
Interpret each data-matching pattern as a list of fixed
|
||||||
strings, separated by newlines, instead of as a regular
|
strings, separated by newlines, instead of as a regular ex-
|
||||||
expression. What constitutes a newline for this purpose is
|
pression. What constitutes a newline for this purpose is con-
|
||||||
controlled by the --newline option. The -w (match as a word)
|
trolled by the --newline option. The -w (match as a word) and
|
||||||
and -x (match whole line) options can be used with -F. They
|
-x (match whole line) options can be used with -F. They ap-
|
||||||
apply to each of the fixed strings. A line is selected if any
|
ply to each of the fixed strings. A line is selected if any
|
||||||
of the fixed strings are found in it (subject to -w or -x, if
|
of the fixed strings are found in it (subject to -w or -x, if
|
||||||
present). This option applies only to the patterns that are
|
present). This option applies only to the patterns that are
|
||||||
matched against the contents of files; it does not apply to
|
matched against the contents of files; it does not apply to
|
||||||
patterns specified by any of the --include or --exclude
|
patterns specified by any of the --include or --exclude op-
|
||||||
options.
|
tions.
|
||||||
|
|
||||||
-f filename, --file=filename
|
-f filename, --file=filename
|
||||||
Read patterns from the file, one per line, and match them
|
Read patterns from the file, one per line, and match them
|
||||||
@ -358,16 +358,16 @@ OPTIONS
|
|||||||
--include=pattern
|
--include=pattern
|
||||||
If any --include patterns are specified, the only files that
|
If any --include patterns are specified, the only files that
|
||||||
are processed are those that match one of the patterns (and
|
are processed are those that match one of the patterns (and
|
||||||
do not match an --exclude pattern). This option does not
|
do not match an --exclude pattern). This option does not af-
|
||||||
affect directories, but it applies to all files, whether
|
fect directories, but it applies to all files, whether listed
|
||||||
listed on the command line, obtained from --file-list, or by
|
on the command line, obtained from --file-list, or by scan-
|
||||||
scanning a directory. The pattern is a PCRE regular expres-
|
ning a directory. The pattern is a PCRE regular expression,
|
||||||
sion, and is matched against the final component of the file
|
and is matched against the final component of the file name,
|
||||||
name, not the entire path. The -F, -w, and -x options do not
|
not the entire path. The -F, -w, and -x options do not apply
|
||||||
apply to this pattern. The option may be given any number of
|
to this pattern. The option may be given any number of times.
|
||||||
times. If a file name matches both an --include and an
|
If a file name matches both an --include and an --exclude
|
||||||
--exclude pattern, it is excluded. There is no short form
|
pattern, it is excluded. There is no short form for this op-
|
||||||
for this option.
|
tion.
|
||||||
|
|
||||||
--include-from=filename
|
--include-from=filename
|
||||||
Treat each non-empty line of the file as the data for an
|
Treat each non-empty line of the file as the data for an
|
||||||
@ -381,8 +381,8 @@ OPTIONS
|
|||||||
tories that are processed are those that match one of the
|
tories that are processed are those that match one of the
|
||||||
patterns (and do not match an --exclude-dir pattern). This
|
patterns (and do not match an --exclude-dir pattern). This
|
||||||
applies to all directories, whether listed on the command
|
applies to all directories, whether listed on the command
|
||||||
line, obtained from --file-list, or by scanning a parent
|
line, obtained from --file-list, or by scanning a parent di-
|
||||||
directory. The pattern is a PCRE regular expression, and is
|
rectory. The pattern is a PCRE regular expression, and is
|
||||||
matched against the final component of the directory name,
|
matched against the final component of the directory name,
|
||||||
not the entire path. The -F, -w, and -x options do not apply
|
not the entire path. The -F, -w, and -x options do not apply
|
||||||
to this pattern. The option may be given any number of times.
|
to this pattern. The option may be given any number of times.
|
||||||
@ -413,9 +413,9 @@ OPTIONS
|
|||||||
|
|
||||||
--line-buffered
|
--line-buffered
|
||||||
When this option is given, input is read and processed line
|
When this option is given, input is read and processed line
|
||||||
by line, and the output is flushed after each write. By
|
by line, and the output is flushed after each write. By de-
|
||||||
default, input is read in large chunks, unless pcregrep can
|
fault, input is read in large chunks, unless pcregrep can de-
|
||||||
determine that it is reading from a terminal (which is cur-
|
termine that it is reading from a terminal (which is cur-
|
||||||
rently possible only in Unix-like environments). Output to
|
rently possible only in Unix-like environments). Output to
|
||||||
terminal is normally automatically flushed by the operating
|
terminal is normally automatically flushed by the operating
|
||||||
system. This option can be useful when the input or output is
|
system. This option can be useful when the input or output is
|
||||||
@ -437,9 +437,9 @@ OPTIONS
|
|||||||
--locale=locale-name
|
--locale=locale-name
|
||||||
This option specifies a locale to be used for pattern match-
|
This option specifies a locale to be used for pattern match-
|
||||||
ing. It overrides the value in the LC_ALL or LC_CTYPE envi-
|
ing. It overrides the value in the LC_ALL or LC_CTYPE envi-
|
||||||
ronment variables. If no locale is specified, the PCRE
|
ronment variables. If no locale is specified, the PCRE li-
|
||||||
library's default (usually the "C" locale) is used. There is
|
brary's default (usually the "C" locale) is used. There is no
|
||||||
no short form for this option.
|
short form for this option.
|
||||||
|
|
||||||
--match-limit=number
|
--match-limit=number
|
||||||
Processing some regular expression patterns can require a
|
Processing some regular expression patterns can require a
|
||||||
@ -447,26 +447,26 @@ OPTIONS
|
|||||||
gram crash if not enough is available. Other patterns may
|
gram crash if not enough is available. Other patterns may
|
||||||
take a very long time to search for all possible matching
|
take a very long time to search for all possible matching
|
||||||
strings. The pcre_exec() function that is called by pcregrep
|
strings. The pcre_exec() function that is called by pcregrep
|
||||||
to do the matching has two parameters that can limit the
|
to do the matching has two parameters that can limit the re-
|
||||||
resources that it uses.
|
sources that it uses.
|
||||||
|
|
||||||
The --match-limit option provides a means of limiting
|
The --match-limit option provides a means of limiting re-
|
||||||
resource usage when processing patterns that are not going to
|
source usage when processing patterns that are not going to
|
||||||
match, but which have a very large number of possibilities in
|
match, but which have a very large number of possibilities in
|
||||||
their search trees. The classic example is a pattern that
|
their search trees. The classic example is a pattern that
|
||||||
uses nested unlimited repeats. Internally, PCRE uses a func-
|
uses nested unlimited repeats. Internally, PCRE uses a func-
|
||||||
tion called match() which it calls repeatedly (sometimes
|
tion called match() which it calls repeatedly (sometimes re-
|
||||||
recursively). The limit set by --match-limit is imposed on
|
cursively). The limit set by --match-limit is imposed on the
|
||||||
the number of times this function is called during a match,
|
number of times this function is called during a match, which
|
||||||
which has the effect of limiting the amount of backtracking
|
has the effect of limiting the amount of backtracking that
|
||||||
that can take place.
|
can take place.
|
||||||
|
|
||||||
The --recursion-limit option is similar to --match-limit, but
|
The --recursion-limit option is similar to --match-limit, but
|
||||||
instead of limiting the total number of times that match() is
|
instead of limiting the total number of times that match() is
|
||||||
called, it limits the depth of recursive calls, which in turn
|
called, it limits the depth of recursive calls, which in turn
|
||||||
limits the amount of memory that can be used. The recursion
|
limits the amount of memory that can be used. The recursion
|
||||||
depth is a smaller number than the total number of calls,
|
depth is a smaller number than the total number of calls, be-
|
||||||
because not all calls to match() are recursive. This limit is
|
cause not all calls to match() are recursive. This limit is
|
||||||
of use only if it is set smaller than --match-limit.
|
of use only if it is set smaller than --match-limit.
|
||||||
|
|
||||||
There are no short forms for these options. The default set-
|
There are no short forms for these options. The default set-
|
||||||
@ -494,30 +494,30 @@ OPTIONS
|
|||||||
is read line by line (see --line-buffered.)
|
is read line by line (see --line-buffered.)
|
||||||
|
|
||||||
-N newline-type, --newline=newline-type
|
-N newline-type, --newline=newline-type
|
||||||
The PCRE library supports five different conventions for
|
The PCRE library supports five different conventions for in-
|
||||||
indicating the ends of lines. They are the single-character
|
dicating the ends of lines. They are the single-character se-
|
||||||
sequences CR (carriage return) and LF (linefeed), the two-
|
quences CR (carriage return) and LF (linefeed), the two-char-
|
||||||
character sequence CRLF, an "anycrlf" convention, which rec-
|
acter sequence CRLF, an "anycrlf" convention, which recog-
|
||||||
ognizes any of the preceding three types, and an "any" con-
|
nizes any of the preceding three types, and an "any" conven-
|
||||||
vention, in which any Unicode line ending sequence is assumed
|
tion, in which any Unicode line ending sequence is assumed to
|
||||||
to end a line. The Unicode sequences are the three just men-
|
end a line. The Unicode sequences are the three just men-
|
||||||
tioned, plus VT (vertical tab, U+000B), FF (form feed,
|
tioned, plus VT (vertical tab, U+000B), FF (form feed,
|
||||||
U+000C), NEL (next line, U+0085), LS (line separator,
|
U+000C), NEL (next line, U+0085), LS (line separator,
|
||||||
U+2028), and PS (paragraph separator, U+2029).
|
U+2028), and PS (paragraph separator, U+2029).
|
||||||
|
|
||||||
When the PCRE library is built, a default line-ending
|
When the PCRE library is built, a default line-ending se-
|
||||||
sequence is specified. This is normally the standard
|
quence is specified. This is normally the standard sequence
|
||||||
sequence for the operating system. Unless otherwise specified
|
for the operating system. Unless otherwise specified by this
|
||||||
by this option, pcregrep uses the library's default. The
|
option, pcregrep uses the library's default. The possible
|
||||||
possible values for this option are CR, LF, CRLF, ANYCRLF, or
|
values for this option are CR, LF, CRLF, ANYCRLF, or ANY.
|
||||||
ANY. This makes it possible to use pcregrep to scan files
|
This makes it possible to use pcregrep to scan files that
|
||||||
that have come from other environments without having to mod-
|
have come from other environments without having to modify
|
||||||
ify their line endings. If the data that is being scanned
|
their line endings. If the data that is being scanned does
|
||||||
does not agree with the convention set by this option, pcre-
|
not agree with the convention set by this option, pcregrep
|
||||||
grep may behave in strange ways. Note that this option does
|
may behave in strange ways. Note that this option does not
|
||||||
not apply to files specified by the -f, --exclude-from, or
|
apply to files specified by the -f, --exclude-from, or --in-
|
||||||
--include-from options, which are expected to use the operat-
|
clude-from options, which are expected to use the operating
|
||||||
ing system's standard newline sequence.
|
system's standard newline sequence.
|
||||||
|
|
||||||
-n, --line-number
|
-n, --line-number
|
||||||
Precede each output line by its line number in the file, fol-
|
Precede each output line by its line number in the file, fol-
|
||||||
@ -538,12 +538,12 @@ OPTIONS
|
|||||||
is, the -A, -B, and -C options are ignored. If there is more
|
is, the -A, -B, and -C options are ignored. If there is more
|
||||||
than one match in a line, each of them is shown separately.
|
than one match in a line, each of them is shown separately.
|
||||||
If -o is combined with -v (invert the sense of the match to
|
If -o is combined with -v (invert the sense of the match to
|
||||||
find non-matching lines), no output is generated, but the
|
find non-matching lines), no output is generated, but the re-
|
||||||
return code is set appropriately. If the matched portion of
|
turn code is set appropriately. If the matched portion of the
|
||||||
the line is empty, nothing is output unless the file name or
|
line is empty, nothing is output unless the file name or line
|
||||||
line number are being printed, in which case they are shown
|
number are being printed, in which case they are shown on an
|
||||||
on an otherwise empty line. This option is mutually exclusive
|
otherwise empty line. This option is mutually exclusive with
|
||||||
with --file-offsets and --line-offsets.
|
--file-offsets and --line-offsets.
|
||||||
|
|
||||||
-onumber, --only-matching=number
|
-onumber, --only-matching=number
|
||||||
Show only the part of the line that matched the capturing
|
Show only the part of the line that matched the capturing
|
||||||
@ -579,8 +579,8 @@ OPTIONS
|
|||||||
it contains, taking note of any --include and --exclude set-
|
it contains, taking note of any --include and --exclude set-
|
||||||
tings. By default, a directory is read as a normal file; in
|
tings. By default, a directory is read as a normal file; in
|
||||||
some operating systems this gives an immediate end-of-file.
|
some operating systems this gives an immediate end-of-file.
|
||||||
This option is a shorthand for setting the -d option to
|
This option is a shorthand for setting the -d option to "re-
|
||||||
"recurse".
|
curse".
|
||||||
|
|
||||||
--recursion-limit=number
|
--recursion-limit=number
|
||||||
See --match-limit above.
|
See --match-limit above.
|
||||||
@ -626,10 +626,10 @@ OPTIONS
|
|||||||
|
|
||||||
ENVIRONMENT VARIABLES
|
ENVIRONMENT VARIABLES
|
||||||
|
|
||||||
The environment variables LC_ALL and LC_CTYPE are examined, in that
|
The environment variables LC_ALL and LC_CTYPE are examined, in that or-
|
||||||
order, for a locale. The first one that is set is used. This can be
|
der, for a locale. The first one that is set is used. This can be over-
|
||||||
overridden by the --locale option. If no locale is set, the PCRE
|
ridden by the --locale option. If no locale is set, the PCRE library's
|
||||||
library's default (usually the "C" locale) is used.
|
default (usually the "C" locale) is used.
|
||||||
|
|
||||||
|
|
||||||
NEWLINES
|
NEWLINES
|
||||||
@ -640,8 +640,8 @@ NEWLINES
|
|||||||
ever newline sequences they have in the input. However, the setting of
|
ever newline sequences they have in the input. However, the setting of
|
||||||
this option does not affect the interpretation of files specified by
|
this option does not affect the interpretation of files specified by
|
||||||
the -f, --exclude-from, or --include-from options, which are assumed to
|
the -f, --exclude-from, or --include-from options, which are assumed to
|
||||||
use the operating system's standard newline sequence, nor does it
|
use the operating system's standard newline sequence, nor does it af-
|
||||||
affect the way in which pcregrep writes informational messages to the
|
fect the way in which pcregrep writes informational messages to the
|
||||||
standard error and output streams. For these it uses the string "\n" to
|
standard error and output streams. For these it uses the string "\n" to
|
||||||
indicate newlines, relying on the C I/O library to convert this to an
|
indicate newlines, relying on the C I/O library to convert this to an
|
||||||
appropriate sequence.
|
appropriate sequence.
|
||||||
@ -687,13 +687,13 @@ OPTIONS WITH DATA
|
|||||||
--file /some/file
|
--file /some/file
|
||||||
|
|
||||||
Note, however, that if you want to supply a file name beginning with ~
|
Note, however, that if you want to supply a file name beginning with ~
|
||||||
as data in a shell command, and have the shell expand ~ to a home
|
as data in a shell command, and have the shell expand ~ to a home di-
|
||||||
directory, you must separate the file name from the option, because the
|
rectory, you must separate the file name from the option, because the
|
||||||
shell does not treat ~ specially unless it is at the start of an item.
|
shell does not treat ~ specially unless it is at the start of an item.
|
||||||
|
|
||||||
The exceptions to the above are the --colour (or --color) and --only-
|
The exceptions to the above are the --colour (or --color) and --only-
|
||||||
matching options, for which the data is optional. If one of these
|
matching options, for which the data is optional. If one of these op-
|
||||||
options does have data, it must be given in the first form, using an
|
tions does have data, it must be given in the first form, using an
|
||||||
equals character. Otherwise pcregrep will assume that it has no data.
|
equals character. Otherwise pcregrep will assume that it has no data.
|
||||||
|
|
||||||
|
|
||||||
@ -702,14 +702,14 @@ MATCHING ERRORS
|
|||||||
It is possible to supply a regular expression that takes a very long
|
It is possible to supply a regular expression that takes a very long
|
||||||
time to fail to match certain lines. Such patterns normally involve
|
time to fail to match certain lines. Such patterns normally involve
|
||||||
nested indefinite repeats, for example: (a+)*\d when matched against a
|
nested indefinite repeats, for example: (a+)*\d when matched against a
|
||||||
line of a's with no final digit. The PCRE matching function has a
|
line of a's with no final digit. The PCRE matching function has a re-
|
||||||
resource limit that causes it to abort in these circumstances. If this
|
source limit that causes it to abort in these circumstances. If this
|
||||||
happens, pcregrep outputs an error message and the line that caused the
|
happens, pcregrep outputs an error message and the line that caused the
|
||||||
problem to the standard error stream. If there are more than 20 such
|
problem to the standard error stream. If there are more than 20 such
|
||||||
errors, pcregrep gives up.
|
errors, pcregrep gives up.
|
||||||
|
|
||||||
The --match-limit option of pcregrep can be used to set the overall
|
The --match-limit option of pcregrep can be used to set the overall re-
|
||||||
resource limit; there is a second option called --recursion-limit that
|
source limit; there is a second option called --recursion-limit that
|
||||||
sets a limit on the amount of memory (usually stack) that is used (see
|
sets a limit on the amount of memory (usually stack) that is used (see
|
||||||
the discussion of these options above).
|
the discussion of these options above).
|
||||||
|
|
||||||
|
@ -1,4 +1,4 @@
|
|||||||
.TH PCRETEST 1 "23 February 2017" "PCRE 8.41"
|
.TH PCRETEST 1 "10 February 2020" "PCRE 8.44"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
pcretest - a program for testing Perl-compatible regular expressions.
|
pcretest - a program for testing Perl-compatible regular expressions.
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
@ -78,21 +78,19 @@ the 16-bit library, or \fBpcre32_xx\fP when using the 32-bit library".
|
|||||||
.rs
|
.rs
|
||||||
.TP 10
|
.TP 10
|
||||||
\fB-8\fP
|
\fB-8\fP
|
||||||
If both the 8-bit library has been built, this option causes the 8-bit library
|
If the 8-bit library has been built, this option causes it to be used (this is
|
||||||
to be used (which is the default); if the 8-bit library has not been built,
|
the default). If the 8-bit library has not been built, this option causes an
|
||||||
this option causes an error.
|
error.
|
||||||
.TP 10
|
.TP 10
|
||||||
\fB-16\fP
|
\fB-16\fP
|
||||||
If both the 8-bit or the 32-bit, and the 16-bit libraries have been built, this
|
If the 16-bit library has been built, this option causes it to be used. If only
|
||||||
option causes the 16-bit library to be used. If only the 16-bit library has been
|
the 16-bit library has been built, this is the default. If the 16-bit library
|
||||||
built, this is the default (so has no effect). If only the 8-bit or the 32-bit
|
has not been built, this option causes an error.
|
||||||
library has been built, this option causes an error.
|
|
||||||
.TP 10
|
.TP 10
|
||||||
\fB-32\fP
|
\fB-32\fP
|
||||||
If both the 8-bit or the 16-bit, and the 32-bit libraries have been built, this
|
If the 32-bit library has been built, this option causes it to be used. If only
|
||||||
option causes the 32-bit library to be used. If only the 32-bit library has been
|
the 32-bit library has been built, this is the default. If the 32-bit library
|
||||||
built, this is the default (so has no effect). If only the 8-bit or the 16-bit
|
has not been built, this option causes an error.
|
||||||
library has been built, this option causes an error.
|
|
||||||
.TP 10
|
.TP 10
|
||||||
\fB-b\fP
|
\fB-b\fP
|
||||||
Behave as if each pattern has the \fB/B\fP (show byte code) modifier; the
|
Behave as if each pattern has the \fB/B\fP (show byte code) modifier; the
|
||||||
@ -1155,6 +1153,6 @@ Cambridge CB2 3QH, England.
|
|||||||
.rs
|
.rs
|
||||||
.sp
|
.sp
|
||||||
.nf
|
.nf
|
||||||
Last updated: 23 February 2017
|
Last updated: 10 February 2020
|
||||||
Copyright (c) 1997-2017 University of Cambridge.
|
Copyright (c) 1997-2020 University of Cambridge.
|
||||||
.fi
|
.fi
|
||||||
|
@ -47,15 +47,15 @@ INPUT DATA FORMAT
|
|||||||
PCRE's 8-BIT, 16-BIT AND 32-BIT LIBRARIES
|
PCRE's 8-BIT, 16-BIT AND 32-BIT LIBRARIES
|
||||||
|
|
||||||
From release 8.30, two separate PCRE libraries can be built. The origi-
|
From release 8.30, two separate PCRE libraries can be built. The origi-
|
||||||
nal one supports 8-bit character strings, whereas the newer 16-bit
|
nal one supports 8-bit character strings, whereas the newer 16-bit li-
|
||||||
library supports character strings encoded in 16-bit units. From
|
brary supports character strings encoded in 16-bit units. From release
|
||||||
release 8.32, a third library can be built, supporting character
|
8.32, a third library can be built, supporting character strings en-
|
||||||
strings encoded in 32-bit units. The pcretest program can be used to
|
coded in 32-bit units. The pcretest program can be used to test all
|
||||||
test all three libraries. However, it is itself still an 8-bit program,
|
three libraries. However, it is itself still an 8-bit program, reading
|
||||||
reading 8-bit input and writing 8-bit output. When testing the 16-bit
|
8-bit input and writing 8-bit output. When testing the 16-bit or
|
||||||
or 32-bit library, the patterns and data strings are converted to 16-
|
32-bit library, the patterns and data strings are converted to 16- or
|
||||||
or 32-bit format before being passed to the PCRE library functions.
|
32-bit format before being passed to the PCRE library functions. Re-
|
||||||
Results are converted to 8-bit for output.
|
sults are converted to 8-bit for output.
|
||||||
|
|
||||||
References to functions and structures of the form pcre[16|32]_xx below
|
References to functions and structures of the form pcre[16|32]_xx below
|
||||||
mean "pcre_xx when using the 8-bit library, pcre16_xx when using the
|
mean "pcre_xx when using the 8-bit library, pcre16_xx when using the
|
||||||
@ -64,34 +64,31 @@ PCRE's 8-BIT, 16-BIT AND 32-BIT LIBRARIES
|
|||||||
|
|
||||||
COMMAND LINE OPTIONS
|
COMMAND LINE OPTIONS
|
||||||
|
|
||||||
-8 If both the 8-bit library has been built, this option causes
|
-8 If the 8-bit library has been built, this option causes it to
|
||||||
the 8-bit library to be used (which is the default); if the
|
be used (this is the default). If the 8-bit library has not
|
||||||
8-bit library has not been built, this option causes an
|
been built, this option causes an error.
|
||||||
error.
|
|
||||||
|
|
||||||
-16 If both the 8-bit or the 32-bit, and the 16-bit libraries
|
-16 If the 16-bit library has been built, this option causes it
|
||||||
have been built, this option causes the 16-bit library to be
|
to be used. If only the 16-bit library has been built, this
|
||||||
used. If only the 16-bit library has been built, this is the
|
is the default. If the 16-bit library has not been built,
|
||||||
default (so has no effect). If only the 8-bit or the 32-bit
|
this option causes an error.
|
||||||
library has been built, this option causes an error.
|
|
||||||
|
|
||||||
-32 If both the 8-bit or the 16-bit, and the 32-bit libraries
|
-32 If the 32-bit library has been built, this option causes it
|
||||||
have been built, this option causes the 32-bit library to be
|
to be used. If only the 32-bit library has been built, this
|
||||||
used. If only the 32-bit library has been built, this is the
|
is the default. If the 32-bit library has not been built,
|
||||||
default (so has no effect). If only the 8-bit or the 16-bit
|
this option causes an error.
|
||||||
library has been built, this option causes an error.
|
|
||||||
|
|
||||||
-b Behave as if each pattern has the /B (show byte code) modi-
|
-b Behave as if each pattern has the /B (show byte code) modi-
|
||||||
fier; the internal form is output after compilation.
|
fier; the internal form is output after compilation.
|
||||||
|
|
||||||
-C Output the version number of the PCRE library, and all avail-
|
-C Output the version number of the PCRE library, and all avail-
|
||||||
able information about the optional features that are
|
able information about the optional features that are in-
|
||||||
included, and then exit with zero exit code. All other
|
cluded, and then exit with zero exit code. All other options
|
||||||
options are ignored.
|
are ignored.
|
||||||
|
|
||||||
-C option Output information about a specific build-time option, then
|
-C option Output information about a specific build-time option, then
|
||||||
exit. This functionality is intended for use in scripts such
|
exit. This functionality is intended for use in scripts such
|
||||||
as RunTest. The following options output the value and set
|
as RunTest. The following options output the value and set
|
||||||
the exit code as indicated:
|
the exit code as indicated:
|
||||||
|
|
||||||
ebcdic-nl the code for LF (= NL) in an EBCDIC environment:
|
ebcdic-nl the code for LF (= NL) in an EBCDIC environment:
|
||||||
@ -107,7 +104,7 @@ COMMAND LINE OPTIONS
|
|||||||
ANYCRLF or ANY
|
ANYCRLF or ANY
|
||||||
exit code is always 0
|
exit code is always 0
|
||||||
|
|
||||||
The following options output 1 for true or 0 for false, and
|
The following options output 1 for true or 0 for false, and
|
||||||
set the exit code to the same value:
|
set the exit code to the same value:
|
||||||
|
|
||||||
ebcdic compiled for an EBCDIC environment
|
ebcdic compiled for an EBCDIC environment
|
||||||
@ -119,61 +116,61 @@ COMMAND LINE OPTIONS
|
|||||||
utf UTF-8 and/or UTF-16 and/or UTF-32 support
|
utf UTF-8 and/or UTF-16 and/or UTF-32 support
|
||||||
is available
|
is available
|
||||||
|
|
||||||
If an unknown option is given, an error message is output;
|
If an unknown option is given, an error message is output;
|
||||||
the exit code is 0.
|
the exit code is 0.
|
||||||
|
|
||||||
-d Behave as if each pattern has the /D (debug) modifier; the
|
-d Behave as if each pattern has the /D (debug) modifier; the
|
||||||
internal form and information about the compiled pattern is
|
internal form and information about the compiled pattern is
|
||||||
output after compilation; -d is equivalent to -b -i.
|
output after compilation; -d is equivalent to -b -i.
|
||||||
|
|
||||||
-dfa Behave as if each data line contains the \D escape sequence;
|
-dfa Behave as if each data line contains the \D escape sequence;
|
||||||
this causes the alternative matching function,
|
this causes the alternative matching function,
|
||||||
pcre[16|32]_dfa_exec(), to be used instead of the standard
|
pcre[16|32]_dfa_exec(), to be used instead of the standard
|
||||||
pcre[16|32]_exec() function (more detail is given below).
|
pcre[16|32]_exec() function (more detail is given below).
|
||||||
|
|
||||||
-help Output a brief summary these options and then exit.
|
-help Output a brief summary these options and then exit.
|
||||||
|
|
||||||
-i Behave as if each pattern has the /I modifier; information
|
-i Behave as if each pattern has the /I modifier; information
|
||||||
about the compiled pattern is given after compilation.
|
about the compiled pattern is given after compilation.
|
||||||
|
|
||||||
-M Behave as if each data line contains the \M escape sequence;
|
-M Behave as if each data line contains the \M escape sequence;
|
||||||
this causes PCRE to discover the minimum MATCH_LIMIT and
|
this causes PCRE to discover the minimum MATCH_LIMIT and
|
||||||
MATCH_LIMIT_RECURSION settings by calling pcre[16|32]_exec()
|
MATCH_LIMIT_RECURSION settings by calling pcre[16|32]_exec()
|
||||||
repeatedly with different limits.
|
repeatedly with different limits.
|
||||||
|
|
||||||
-m Output the size of each compiled pattern after it has been
|
-m Output the size of each compiled pattern after it has been
|
||||||
compiled. This is equivalent to adding /M to each regular
|
compiled. This is equivalent to adding /M to each regular ex-
|
||||||
expression. The size is given in bytes for both libraries.
|
pression. The size is given in bytes for both libraries.
|
||||||
|
|
||||||
-O Behave as if each pattern has the /O modifier, that is dis-
|
-O Behave as if each pattern has the /O modifier, that is dis-
|
||||||
able auto-possessification for all patterns.
|
able auto-possessification for all patterns.
|
||||||
|
|
||||||
-o osize Set the number of elements in the output vector that is used
|
-o osize Set the number of elements in the output vector that is used
|
||||||
when calling pcre[16|32]_exec() or pcre[16|32]_dfa_exec() to
|
when calling pcre[16|32]_exec() or pcre[16|32]_dfa_exec() to
|
||||||
be osize. The default value is 45, which is enough for 14
|
be osize. The default value is 45, which is enough for 14
|
||||||
capturing subexpressions for pcre[16|32]_exec() or 22 differ-
|
capturing subexpressions for pcre[16|32]_exec() or 22 differ-
|
||||||
ent matches for pcre[16|32]_dfa_exec(). The vector size can
|
ent matches for pcre[16|32]_dfa_exec(). The vector size can
|
||||||
be changed for individual matching calls by including \O in
|
be changed for individual matching calls by including \O in
|
||||||
the data line (see below).
|
the data line (see below).
|
||||||
|
|
||||||
-p Behave as if each pattern has the /P modifier; the POSIX
|
-p Behave as if each pattern has the /P modifier; the POSIX
|
||||||
wrapper API is used to call PCRE. None of the other options
|
wrapper API is used to call PCRE. None of the other options
|
||||||
has any effect when -p is set. This option can be used only
|
has any effect when -p is set. This option can be used only
|
||||||
with the 8-bit library.
|
with the 8-bit library.
|
||||||
|
|
||||||
-q Do not output the version number of pcretest at the start of
|
-q Do not output the version number of pcretest at the start of
|
||||||
execution.
|
execution.
|
||||||
|
|
||||||
-S size On Unix-like systems, set the size of the run-time stack to
|
-S size On Unix-like systems, set the size of the run-time stack to
|
||||||
size megabytes.
|
size megabytes.
|
||||||
|
|
||||||
-s or -s+ Behave as if each pattern has the /S modifier; in other
|
-s or -s+ Behave as if each pattern has the /S modifier; in other
|
||||||
words, force each pattern to be studied. If -s+ is used, all
|
words, force each pattern to be studied. If -s+ is used, all
|
||||||
the JIT compile options are passed to pcre[16|32]_study(),
|
the JIT compile options are passed to pcre[16|32]_study(),
|
||||||
causing just-in-time optimization to be set up if it is
|
causing just-in-time optimization to be set up if it is
|
||||||
available, for both full and partial matching. Specific JIT
|
available, for both full and partial matching. Specific JIT
|
||||||
compile options can be selected by following -s+ with a digit
|
compile options can be selected by following -s+ with a digit
|
||||||
in the range 1 to 7, which selects the JIT compile modes as
|
in the range 1 to 7, which selects the JIT compile modes as
|
||||||
follows:
|
follows:
|
||||||
|
|
||||||
1 normal match only
|
1 normal match only
|
||||||
@ -183,119 +180,119 @@ COMMAND LINE OPTIONS
|
|||||||
6 soft and hard partial match
|
6 soft and hard partial match
|
||||||
7 all three modes (default)
|
7 all three modes (default)
|
||||||
|
|
||||||
If -s++ is used instead of -s+ (with or without a following
|
If -s++ is used instead of -s+ (with or without a following
|
||||||
digit), the text "(JIT)" is added to the first output line
|
digit), the text "(JIT)" is added to the first output line
|
||||||
after a match or no match when JIT-compiled code was actually
|
after a match or no match when JIT-compiled code was actually
|
||||||
used.
|
used.
|
||||||
|
|
||||||
Note that there are pattern options that can override -s,
|
Note that there are pattern options that can override -s, ei-
|
||||||
either specifying no studying at all, or suppressing JIT com-
|
ther specifying no studying at all, or suppressing JIT compi-
|
||||||
pilation.
|
lation.
|
||||||
|
|
||||||
If the /I or /D option is present on a pattern (requesting
|
If the /I or /D option is present on a pattern (requesting
|
||||||
output about the compiled pattern), information about the
|
output about the compiled pattern), information about the re-
|
||||||
result of studying is not included when studying is caused
|
sult of studying is not included when studying is caused only
|
||||||
only by -s and neither -i nor -d is present on the command
|
by -s and neither -i nor -d is present on the command line.
|
||||||
line. This behaviour means that the output from tests that
|
This behaviour means that the output from tests that are run
|
||||||
are run with and without -s should be identical, except when
|
with and without -s should be identical, except when options
|
||||||
options that output information about the actual running of a
|
that output information about the actual running of a match
|
||||||
match are set.
|
are set.
|
||||||
|
|
||||||
The -M, -t, and -tm options, which give information about
|
The -M, -t, and -tm options, which give information about re-
|
||||||
resources used, are likely to produce different output with
|
sources used, are likely to produce different output with and
|
||||||
and without -s. Output may also differ if the /C option is
|
without -s. Output may also differ if the /C option is
|
||||||
present on an individual pattern. This uses callouts to trace
|
present on an individual pattern. This uses callouts to trace
|
||||||
the the matching process, and this may be different between
|
the the matching process, and this may be different between
|
||||||
studied and non-studied patterns. If the pattern contains
|
studied and non-studied patterns. If the pattern contains
|
||||||
(*MARK) items there may also be differences, for the same
|
(*MARK) items there may also be differences, for the same
|
||||||
reason. The -s command line option can be overridden for spe-
|
reason. The -s command line option can be overridden for spe-
|
||||||
cific patterns that should never be studied (see the /S pat-
|
cific patterns that should never be studied (see the /S pat-
|
||||||
tern modifier below).
|
tern modifier below).
|
||||||
|
|
||||||
-t Run each compile, study, and match many times with a timer,
|
-t Run each compile, study, and match many times with a timer,
|
||||||
and output the resulting times per compile, study, or match
|
and output the resulting times per compile, study, or match
|
||||||
(in milliseconds). Do not set -m with -t, because you will
|
(in milliseconds). Do not set -m with -t, because you will
|
||||||
then get the size output a zillion times, and the timing will
|
then get the size output a zillion times, and the timing will
|
||||||
be distorted. You can control the number of iterations that
|
be distorted. You can control the number of iterations that
|
||||||
are used for timing by following -t with a number (as a sepa-
|
are used for timing by following -t with a number (as a sepa-
|
||||||
rate item on the command line). For example, "-t 1000" iter-
|
rate item on the command line). For example, "-t 1000" iter-
|
||||||
ates 1000 times. The default is to iterate 500000 times.
|
ates 1000 times. The default is to iterate 500000 times.
|
||||||
|
|
||||||
-tm This is like -t except that it times only the matching phase,
|
-tm This is like -t except that it times only the matching phase,
|
||||||
not the compile or study phases.
|
not the compile or study phases.
|
||||||
|
|
||||||
-T -TM These behave like -t and -tm, but in addition, at the end of
|
-T -TM These behave like -t and -tm, but in addition, at the end of
|
||||||
a run, the total times for all compiles, studies, and matches
|
a run, the total times for all compiles, studies, and matches
|
||||||
are output.
|
are output.
|
||||||
|
|
||||||
|
|
||||||
DESCRIPTION
|
DESCRIPTION
|
||||||
|
|
||||||
If pcretest is given two filename arguments, it reads from the first
|
If pcretest is given two filename arguments, it reads from the first
|
||||||
and writes to the second. If it is given only one filename argument, it
|
and writes to the second. If it is given only one filename argument, it
|
||||||
reads from that file and writes to stdout. Otherwise, it reads from
|
reads from that file and writes to stdout. Otherwise, it reads from
|
||||||
stdin and writes to stdout, and prompts for each line of input, using
|
stdin and writes to stdout, and prompts for each line of input, using
|
||||||
"re>" to prompt for regular expressions, and "data>" to prompt for data
|
"re>" to prompt for regular expressions, and "data>" to prompt for data
|
||||||
lines.
|
lines.
|
||||||
|
|
||||||
When pcretest is built, a configuration option can specify that it
|
When pcretest is built, a configuration option can specify that it
|
||||||
should be linked with the libreadline library. When this is done, if
|
should be linked with the libreadline library. When this is done, if
|
||||||
the input is from a terminal, it is read using the readline() function.
|
the input is from a terminal, it is read using the readline() function.
|
||||||
This provides line-editing and history facilities. The output from the
|
This provides line-editing and history facilities. The output from the
|
||||||
-help option states whether or not readline() will be used.
|
-help option states whether or not readline() will be used.
|
||||||
|
|
||||||
The program handles any number of sets of input on a single input file.
|
The program handles any number of sets of input on a single input file.
|
||||||
Each set starts with a regular expression, and continues with any num-
|
Each set starts with a regular expression, and continues with any num-
|
||||||
ber of data lines to be matched against that pattern.
|
ber of data lines to be matched against that pattern.
|
||||||
|
|
||||||
Each data line is matched separately and independently. If you want to
|
Each data line is matched separately and independently. If you want to
|
||||||
do multi-line matches, you have to use the \n escape sequence (or \r or
|
do multi-line matches, you have to use the \n escape sequence (or \r or
|
||||||
\r\n, etc., depending on the newline setting) in a single line of input
|
\r\n, etc., depending on the newline setting) in a single line of input
|
||||||
to encode the newline sequences. There is no limit on the length of
|
to encode the newline sequences. There is no limit on the length of
|
||||||
data lines; the input buffer is automatically extended if it is too
|
data lines; the input buffer is automatically extended if it is too
|
||||||
small.
|
small.
|
||||||
|
|
||||||
An empty line signals the end of the data lines, at which point a new
|
An empty line signals the end of the data lines, at which point a new
|
||||||
regular expression is read. The regular expressions are given enclosed
|
regular expression is read. The regular expressions are given enclosed
|
||||||
in any non-alphanumeric delimiters other than backslash, for example:
|
in any non-alphanumeric delimiters other than backslash, for example:
|
||||||
|
|
||||||
/(a|bc)x+yz/
|
/(a|bc)x+yz/
|
||||||
|
|
||||||
White space before the initial delimiter is ignored. A regular expres-
|
White space before the initial delimiter is ignored. A regular expres-
|
||||||
sion may be continued over several input lines, in which case the new-
|
sion may be continued over several input lines, in which case the new-
|
||||||
line characters are included within it. It is possible to include the
|
line characters are included within it. It is possible to include the
|
||||||
delimiter within the pattern by escaping it, for example
|
delimiter within the pattern by escaping it, for example
|
||||||
|
|
||||||
/abc\/def/
|
/abc\/def/
|
||||||
|
|
||||||
If you do so, the escape and the delimiter form part of the pattern,
|
If you do so, the escape and the delimiter form part of the pattern,
|
||||||
but since delimiters are always non-alphanumeric, this does not affect
|
but since delimiters are always non-alphanumeric, this does not affect
|
||||||
its interpretation. If the terminating delimiter is immediately fol-
|
its interpretation. If the terminating delimiter is immediately fol-
|
||||||
lowed by a backslash, for example,
|
lowed by a backslash, for example,
|
||||||
|
|
||||||
/abc/\
|
/abc/\
|
||||||
|
|
||||||
then a backslash is added to the end of the pattern. This is done to
|
then a backslash is added to the end of the pattern. This is done to
|
||||||
provide a way of testing the error condition that arises if a pattern
|
provide a way of testing the error condition that arises if a pattern
|
||||||
finishes with a backslash, because
|
finishes with a backslash, because
|
||||||
|
|
||||||
/abc\/
|
/abc\/
|
||||||
|
|
||||||
is interpreted as the first line of a pattern that starts with "abc/",
|
is interpreted as the first line of a pattern that starts with "abc/",
|
||||||
causing pcretest to read the next line as a continuation of the regular
|
causing pcretest to read the next line as a continuation of the regular
|
||||||
expression.
|
expression.
|
||||||
|
|
||||||
|
|
||||||
PATTERN MODIFIERS
|
PATTERN MODIFIERS
|
||||||
|
|
||||||
A pattern may be followed by any number of modifiers, which are mostly
|
A pattern may be followed by any number of modifiers, which are mostly
|
||||||
single characters, though some of these can be qualified by further
|
single characters, though some of these can be qualified by further
|
||||||
characters. Following Perl usage, these are referred to below as, for
|
characters. Following Perl usage, these are referred to below as, for
|
||||||
example, "the /i modifier", even though the delimiter of the pattern
|
example, "the /i modifier", even though the delimiter of the pattern
|
||||||
need not always be a slash, and no slash is used when writing modi-
|
need not always be a slash, and no slash is used when writing modi-
|
||||||
fiers. White space may appear between the final pattern delimiter and
|
fiers. White space may appear between the final pattern delimiter and
|
||||||
the first modifier, and between the modifiers themselves. For refer-
|
the first modifier, and between the modifiers themselves. For refer-
|
||||||
ence, here is a complete list of modifiers. They fall into several
|
ence, here is a complete list of modifiers. They fall into several
|
||||||
groups that are described in detail in the following sections.
|
groups that are described in detail in the following sections.
|
||||||
|
|
||||||
/8 set UTF mode
|
/8 set UTF mode
|
||||||
@ -347,8 +344,8 @@ PATTERN MODIFIERS
|
|||||||
Perl-compatible modifiers
|
Perl-compatible modifiers
|
||||||
|
|
||||||
The /i, /m, /s, and /x modifiers set the PCRE_CASELESS, PCRE_MULTILINE,
|
The /i, /m, /s, and /x modifiers set the PCRE_CASELESS, PCRE_MULTILINE,
|
||||||
PCRE_DOTALL, or PCRE_EXTENDED options, respectively, when
|
PCRE_DOTALL, or PCRE_EXTENDED options, respectively, when
|
||||||
pcre[16|32]_compile() is called. These four modifier letters have the
|
pcre[16|32]_compile() is called. These four modifier letters have the
|
||||||
same effect as they do in Perl. For example:
|
same effect as they do in Perl. For example:
|
||||||
|
|
||||||
/caseless/i
|
/caseless/i
|
||||||
@ -356,7 +353,7 @@ PATTERN MODIFIERS
|
|||||||
|
|
||||||
Modifiers for other PCRE options
|
Modifiers for other PCRE options
|
||||||
|
|
||||||
The following table shows additional modifiers for setting PCRE com-
|
The following table shows additional modifiers for setting PCRE com-
|
||||||
pile-time options that do not correspond to anything in Perl:
|
pile-time options that do not correspond to anything in Perl:
|
||||||
|
|
||||||
/8 PCRE_UTF8 ) when using the 8-bit
|
/8 PCRE_UTF8 ) when using the 8-bit
|
||||||
@ -389,145 +386,145 @@ PATTERN MODIFIERS
|
|||||||
/<bsr_unicode> PCRE_BSR_UNICODE
|
/<bsr_unicode> PCRE_BSR_UNICODE
|
||||||
/<JS> PCRE_JAVASCRIPT_COMPAT
|
/<JS> PCRE_JAVASCRIPT_COMPAT
|
||||||
|
|
||||||
The modifiers that are enclosed in angle brackets are literal strings
|
The modifiers that are enclosed in angle brackets are literal strings
|
||||||
as shown, including the angle brackets, but the letters within can be
|
as shown, including the angle brackets, but the letters within can be
|
||||||
in either case. This example sets multiline matching with CRLF as the
|
in either case. This example sets multiline matching with CRLF as the
|
||||||
line ending sequence:
|
line ending sequence:
|
||||||
|
|
||||||
/^abc/m<CRLF>
|
/^abc/m<CRLF>
|
||||||
|
|
||||||
As well as turning on the PCRE_UTF8/16/32 option, the /8 modifier
|
As well as turning on the PCRE_UTF8/16/32 option, the /8 modifier
|
||||||
causes all non-printing characters in output strings to be printed
|
causes all non-printing characters in output strings to be printed us-
|
||||||
using the \x{hh...} notation. Otherwise, those less than 0x100 are out-
|
ing the \x{hh...} notation. Otherwise, those less than 0x100 are output
|
||||||
put in hex without the curly brackets.
|
in hex without the curly brackets.
|
||||||
|
|
||||||
Full details of the PCRE options are given in the pcreapi documenta-
|
Full details of the PCRE options are given in the pcreapi documenta-
|
||||||
tion.
|
tion.
|
||||||
|
|
||||||
Finding all matches in a string
|
Finding all matches in a string
|
||||||
|
|
||||||
Searching for all possible matches within each subject string can be
|
Searching for all possible matches within each subject string can be
|
||||||
requested by the /g or /G modifier. After finding a match, PCRE is
|
requested by the /g or /G modifier. After finding a match, PCRE is
|
||||||
called again to search the remainder of the subject string. The differ-
|
called again to search the remainder of the subject string. The differ-
|
||||||
ence between /g and /G is that the former uses the startoffset argument
|
ence between /g and /G is that the former uses the startoffset argument
|
||||||
to pcre[16|32]_exec() to start searching at a new point within the
|
to pcre[16|32]_exec() to start searching at a new point within the en-
|
||||||
entire string (which is in effect what Perl does), whereas the latter
|
tire string (which is in effect what Perl does), whereas the latter
|
||||||
passes over a shortened substring. This makes a difference to the
|
passes over a shortened substring. This makes a difference to the
|
||||||
matching process if the pattern begins with a lookbehind assertion
|
matching process if the pattern begins with a lookbehind assertion (in-
|
||||||
(including \b or \B).
|
cluding \b or \B).
|
||||||
|
|
||||||
If any call to pcre[16|32]_exec() in a /g or /G sequence matches an
|
If any call to pcre[16|32]_exec() in a /g or /G sequence matches an
|
||||||
empty string, the next call is done with the PCRE_NOTEMPTY_ATSTART and
|
empty string, the next call is done with the PCRE_NOTEMPTY_ATSTART and
|
||||||
PCRE_ANCHORED flags set in order to search for another, non-empty,
|
PCRE_ANCHORED flags set in order to search for another, non-empty,
|
||||||
match at the same point. If this second match fails, the start offset
|
match at the same point. If this second match fails, the start offset
|
||||||
is advanced, and the normal match is retried. This imitates the way
|
is advanced, and the normal match is retried. This imitates the way
|
||||||
Perl handles such cases when using the /g modifier or the split() func-
|
Perl handles such cases when using the /g modifier or the split() func-
|
||||||
tion. Normally, the start offset is advanced by one character, but if
|
tion. Normally, the start offset is advanced by one character, but if
|
||||||
the newline convention recognizes CRLF as a newline, and the current
|
the newline convention recognizes CRLF as a newline, and the current
|
||||||
character is CR followed by LF, an advance of two is used.
|
character is CR followed by LF, an advance of two is used.
|
||||||
|
|
||||||
Other modifiers
|
Other modifiers
|
||||||
|
|
||||||
There are yet more modifiers for controlling the way pcretest operates.
|
There are yet more modifiers for controlling the way pcretest operates.
|
||||||
|
|
||||||
The /+ modifier requests that as well as outputting the substring that
|
The /+ modifier requests that as well as outputting the substring that
|
||||||
matched the entire pattern, pcretest should in addition output the
|
matched the entire pattern, pcretest should in addition output the re-
|
||||||
remainder of the subject string. This is useful for tests where the
|
mainder of the subject string. This is useful for tests where the sub-
|
||||||
subject contains multiple copies of the same substring. If the + modi-
|
ject contains multiple copies of the same substring. If the + modifier
|
||||||
fier appears twice, the same action is taken for captured substrings.
|
appears twice, the same action is taken for captured substrings. In
|
||||||
In each case the remainder is output on the following line with a plus
|
each case the remainder is output on the following line with a plus
|
||||||
character following the capture number. Note that this modifier must
|
character following the capture number. Note that this modifier must
|
||||||
not immediately follow the /S modifier because /S+ and /S++ have other
|
not immediately follow the /S modifier because /S+ and /S++ have other
|
||||||
meanings.
|
meanings.
|
||||||
|
|
||||||
The /= modifier requests that the values of all potential captured
|
The /= modifier requests that the values of all potential captured
|
||||||
parentheses be output after a match. By default, only those up to the
|
parentheses be output after a match. By default, only those up to the
|
||||||
highest one actually used in the match are output (corresponding to the
|
highest one actually used in the match are output (corresponding to the
|
||||||
return code from pcre[16|32]_exec()). Values in the offsets vector cor-
|
return code from pcre[16|32]_exec()). Values in the offsets vector cor-
|
||||||
responding to higher numbers should be set to -1, and these are output
|
responding to higher numbers should be set to -1, and these are output
|
||||||
as "<unset>". This modifier gives a way of checking that this is hap-
|
as "<unset>". This modifier gives a way of checking that this is hap-
|
||||||
pening.
|
pening.
|
||||||
|
|
||||||
The /B modifier is a debugging feature. It requests that pcretest out-
|
The /B modifier is a debugging feature. It requests that pcretest out-
|
||||||
put a representation of the compiled code after compilation. Normally
|
put a representation of the compiled code after compilation. Normally
|
||||||
this information contains length and offset values; however, if /Z is
|
this information contains length and offset values; however, if /Z is
|
||||||
also present, this data is replaced by spaces. This is a special fea-
|
also present, this data is replaced by spaces. This is a special fea-
|
||||||
ture for use in the automatic test scripts; it ensures that the same
|
ture for use in the automatic test scripts; it ensures that the same
|
||||||
output is generated for different internal link sizes.
|
output is generated for different internal link sizes.
|
||||||
|
|
||||||
The /D modifier is a PCRE debugging feature, and is equivalent to /BI,
|
The /D modifier is a PCRE debugging feature, and is equivalent to /BI,
|
||||||
that is, both the /B and the /I modifiers.
|
that is, both the /B and the /I modifiers.
|
||||||
|
|
||||||
The /F modifier causes pcretest to flip the byte order of the 2-byte
|
The /F modifier causes pcretest to flip the byte order of the 2-byte
|
||||||
and 4-byte fields in the compiled pattern. This facility is for testing
|
and 4-byte fields in the compiled pattern. This facility is for testing
|
||||||
the feature in PCRE that allows it to execute patterns that were com-
|
the feature in PCRE that allows it to execute patterns that were com-
|
||||||
piled on a host with a different endianness. This feature is not avail-
|
piled on a host with a different endianness. This feature is not avail-
|
||||||
able when the POSIX interface to PCRE is being used, that is, when the
|
able when the POSIX interface to PCRE is being used, that is, when the
|
||||||
/P pattern modifier is specified. See also the section about saving and
|
/P pattern modifier is specified. See also the section about saving and
|
||||||
reloading compiled patterns below.
|
reloading compiled patterns below.
|
||||||
|
|
||||||
The /I modifier requests that pcretest output information about the
|
The /I modifier requests that pcretest output information about the
|
||||||
compiled pattern (whether it is anchored, has a fixed first character,
|
compiled pattern (whether it is anchored, has a fixed first character,
|
||||||
and so on). It does this by calling pcre[16|32]_fullinfo() after com-
|
and so on). It does this by calling pcre[16|32]_fullinfo() after com-
|
||||||
piling a pattern. If the pattern is studied, the results of that are
|
piling a pattern. If the pattern is studied, the results of that are
|
||||||
also output. In this output, the word "char" means a non-UTF character,
|
also output. In this output, the word "char" means a non-UTF character,
|
||||||
that is, the value of a single data item (8-bit, 16-bit, or 32-bit,
|
that is, the value of a single data item (8-bit, 16-bit, or 32-bit, de-
|
||||||
depending on the library that is being tested).
|
pending on the library that is being tested).
|
||||||
|
|
||||||
The /K modifier requests pcretest to show names from backtracking con-
|
The /K modifier requests pcretest to show names from backtracking con-
|
||||||
trol verbs that are returned from calls to pcre[16|32]_exec(). It
|
trol verbs that are returned from calls to pcre[16|32]_exec(). It
|
||||||
causes pcretest to create a pcre[16|32]_extra block if one has not
|
causes pcretest to create a pcre[16|32]_extra block if one has not al-
|
||||||
already been created by a call to pcre[16|32]_study(), and to set the
|
ready been created by a call to pcre[16|32]_study(), and to set the
|
||||||
PCRE_EXTRA_MARK flag and the mark field within it, every time that
|
PCRE_EXTRA_MARK flag and the mark field within it, every time that
|
||||||
pcre[16|32]_exec() is called. If the variable that the mark field
|
pcre[16|32]_exec() is called. If the variable that the mark field
|
||||||
points to is non-NULL for a match, non-match, or partial match,
|
points to is non-NULL for a match, non-match, or partial match,
|
||||||
pcretest prints the string to which it points. For a match, this is
|
pcretest prints the string to which it points. For a match, this is
|
||||||
shown on a line by itself, tagged with "MK:". For a non-match it is
|
shown on a line by itself, tagged with "MK:". For a non-match it is
|
||||||
added to the message.
|
added to the message.
|
||||||
|
|
||||||
The /L modifier must be followed directly by the name of a locale, for
|
The /L modifier must be followed directly by the name of a locale, for
|
||||||
example,
|
example,
|
||||||
|
|
||||||
/pattern/Lfr_FR
|
/pattern/Lfr_FR
|
||||||
|
|
||||||
For this reason, it must be the last modifier. The given locale is set,
|
For this reason, it must be the last modifier. The given locale is set,
|
||||||
pcre[16|32]_maketables() is called to build a set of character tables
|
pcre[16|32]_maketables() is called to build a set of character tables
|
||||||
for the locale, and this is then passed to pcre[16|32]_compile() when
|
for the locale, and this is then passed to pcre[16|32]_compile() when
|
||||||
compiling the regular expression. Without an /L (or /T) modifier, NULL
|
compiling the regular expression. Without an /L (or /T) modifier, NULL
|
||||||
is passed as the tables pointer; that is, /L applies only to the
|
is passed as the tables pointer; that is, /L applies only to the ex-
|
||||||
expression on which it appears.
|
pression on which it appears.
|
||||||
|
|
||||||
The /M modifier causes the size in bytes of the memory block used to
|
The /M modifier causes the size in bytes of the memory block used to
|
||||||
hold the compiled pattern to be output. This does not include the size
|
hold the compiled pattern to be output. This does not include the size
|
||||||
of the pcre[16|32] block; it is just the actual compiled data. If the
|
of the pcre[16|32] block; it is just the actual compiled data. If the
|
||||||
pattern is successfully studied with the PCRE_STUDY_JIT_COMPILE option,
|
pattern is successfully studied with the PCRE_STUDY_JIT_COMPILE option,
|
||||||
the size of the JIT compiled code is also output.
|
the size of the JIT compiled code is also output.
|
||||||
|
|
||||||
The /Q modifier is used to test the use of pcre_stack_guard. It must be
|
The /Q modifier is used to test the use of pcre_stack_guard. It must be
|
||||||
followed by '0' or '1', specifying the return code to be given from an
|
followed by '0' or '1', specifying the return code to be given from an
|
||||||
external function that is passed to PCRE and used for stack checking
|
external function that is passed to PCRE and used for stack checking
|
||||||
during compilation (see the pcreapi documentation for details).
|
during compilation (see the pcreapi documentation for details).
|
||||||
|
|
||||||
The /S modifier causes pcre[16|32]_study() to be called after the
|
The /S modifier causes pcre[16|32]_study() to be called after the ex-
|
||||||
expression has been compiled, and the results used when the expression
|
pression has been compiled, and the results used when the expression is
|
||||||
is matched. There are a number of qualifying characters that may follow
|
matched. There are a number of qualifying characters that may follow
|
||||||
/S. They may appear in any order.
|
/S. They may appear in any order.
|
||||||
|
|
||||||
If /S is followed by an exclamation mark, pcre[16|32]_study() is called
|
If /S is followed by an exclamation mark, pcre[16|32]_study() is called
|
||||||
with the PCRE_STUDY_EXTRA_NEEDED option, causing it always to return a
|
with the PCRE_STUDY_EXTRA_NEEDED option, causing it always to return a
|
||||||
pcre_extra block, even when studying discovers no useful information.
|
pcre_extra block, even when studying discovers no useful information.
|
||||||
|
|
||||||
If /S is followed by a second S character, it suppresses studying, even
|
If /S is followed by a second S character, it suppresses studying, even
|
||||||
if it was requested externally by the -s command line option. This
|
if it was requested externally by the -s command line option. This
|
||||||
makes it possible to specify that certain patterns are always studied,
|
makes it possible to specify that certain patterns are always studied,
|
||||||
and others are never studied, independently of -s. This feature is used
|
and others are never studied, independently of -s. This feature is used
|
||||||
in the test files in a few cases where the output is different when the
|
in the test files in a few cases where the output is different when the
|
||||||
pattern is studied.
|
pattern is studied.
|
||||||
|
|
||||||
If the /S modifier is followed by a + character, the call to
|
If the /S modifier is followed by a + character, the call to
|
||||||
pcre[16|32]_study() is made with all the JIT study options, requesting
|
pcre[16|32]_study() is made with all the JIT study options, requesting
|
||||||
just-in-time optimization support if it is available, for both normal
|
just-in-time optimization support if it is available, for both normal
|
||||||
and partial matching. If you want to restrict the JIT compiling modes,
|
and partial matching. If you want to restrict the JIT compiling modes,
|
||||||
you can follow /S+ with a digit in the range 1 to 7:
|
you can follow /S+ with a digit in the range 1 to 7:
|
||||||
|
|
||||||
1 normal match only
|
1 normal match only
|
||||||
@ -538,40 +535,40 @@ PATTERN MODIFIERS
|
|||||||
7 all three modes (default)
|
7 all three modes (default)
|
||||||
|
|
||||||
If /S++ is used instead of /S+ (with or without a following digit), the
|
If /S++ is used instead of /S+ (with or without a following digit), the
|
||||||
text "(JIT)" is added to the first output line after a match or no
|
text "(JIT)" is added to the first output line after a match or no
|
||||||
match when JIT-compiled code was actually used.
|
match when JIT-compiled code was actually used.
|
||||||
|
|
||||||
Note that there is also an independent /+ modifier; it must not be
|
Note that there is also an independent /+ modifier; it must not be
|
||||||
given immediately after /S or /S+ because this will be misinterpreted.
|
given immediately after /S or /S+ because this will be misinterpreted.
|
||||||
|
|
||||||
If JIT studying is successful, the compiled JIT code will automatically
|
If JIT studying is successful, the compiled JIT code will automatically
|
||||||
be used when pcre[16|32]_exec() is run, except when incompatible run-
|
be used when pcre[16|32]_exec() is run, except when incompatible run-
|
||||||
time options are specified. For more details, see the pcrejit documen-
|
time options are specified. For more details, see the pcrejit documen-
|
||||||
tation. See also the \J escape sequence below for a way of setting the
|
tation. See also the \J escape sequence below for a way of setting the
|
||||||
size of the JIT stack.
|
size of the JIT stack.
|
||||||
|
|
||||||
Finally, if /S is followed by a minus character, JIT compilation is
|
Finally, if /S is followed by a minus character, JIT compilation is
|
||||||
suppressed, even if it was requested externally by the -s command line
|
suppressed, even if it was requested externally by the -s command line
|
||||||
option. This makes it possible to specify that JIT is never to be used
|
option. This makes it possible to specify that JIT is never to be used
|
||||||
for certain patterns.
|
for certain patterns.
|
||||||
|
|
||||||
The /T modifier must be followed by a single digit. It causes a spe-
|
The /T modifier must be followed by a single digit. It causes a spe-
|
||||||
cific set of built-in character tables to be passed to pcre[16|32]_com-
|
cific set of built-in character tables to be passed to pcre[16|32]_com-
|
||||||
pile(). It is used in the standard PCRE tests to check behaviour with
|
pile(). It is used in the standard PCRE tests to check behaviour with
|
||||||
different character tables. The digit specifies the tables as follows:
|
different character tables. The digit specifies the tables as follows:
|
||||||
|
|
||||||
0 the default ASCII tables, as distributed in
|
0 the default ASCII tables, as distributed in
|
||||||
pcre_chartables.c.dist
|
pcre_chartables.c.dist
|
||||||
1 a set of tables defining ISO 8859 characters
|
1 a set of tables defining ISO 8859 characters
|
||||||
|
|
||||||
In table 1, some characters whose codes are greater than 128 are iden-
|
In table 1, some characters whose codes are greater than 128 are iden-
|
||||||
tified as letters, digits, spaces, etc.
|
tified as letters, digits, spaces, etc.
|
||||||
|
|
||||||
Using the POSIX wrapper API
|
Using the POSIX wrapper API
|
||||||
|
|
||||||
The /P modifier causes pcretest to call PCRE via the POSIX wrapper API
|
The /P modifier causes pcretest to call PCRE via the POSIX wrapper API
|
||||||
rather than its native API. This supports only the 8-bit library. When
|
rather than its native API. This supports only the 8-bit library. When
|
||||||
/P is set, the following modifiers set options for the regcomp() func-
|
/P is set, the following modifiers set options for the regcomp() func-
|
||||||
tion:
|
tion:
|
||||||
|
|
||||||
/i REG_ICASE
|
/i REG_ICASE
|
||||||
@ -582,48 +579,48 @@ PATTERN MODIFIERS
|
|||||||
/W REG_UCP ) the POSIX standard
|
/W REG_UCP ) the POSIX standard
|
||||||
/8 REG_UTF8 )
|
/8 REG_UTF8 )
|
||||||
|
|
||||||
The /+ modifier works as described above. All other modifiers are
|
The /+ modifier works as described above. All other modifiers are ig-
|
||||||
ignored.
|
nored.
|
||||||
|
|
||||||
Locking out certain modifiers
|
Locking out certain modifiers
|
||||||
|
|
||||||
PCRE can be compiled with or without support for certain features such
|
PCRE can be compiled with or without support for certain features such
|
||||||
as UTF-8/16/32 or Unicode properties. Accordingly, the standard tests
|
as UTF-8/16/32 or Unicode properties. Accordingly, the standard tests
|
||||||
are split up into a number of different files that are selected for
|
are split up into a number of different files that are selected for
|
||||||
running depending on which features are available. When updating the
|
running depending on which features are available. When updating the
|
||||||
tests, it is all too easy to put a new test into the wrong file by mis-
|
tests, it is all too easy to put a new test into the wrong file by mis-
|
||||||
take; for example, to put a test that requires UTF support into a file
|
take; for example, to put a test that requires UTF support into a file
|
||||||
that is used when it is not available. To help detect such mistakes as
|
that is used when it is not available. To help detect such mistakes as
|
||||||
early as possible, there is a facility for locking out specific modi-
|
early as possible, there is a facility for locking out specific modi-
|
||||||
fiers. If an input line for pcretest starts with the string "< forbid "
|
fiers. If an input line for pcretest starts with the string "< forbid "
|
||||||
the following sequence of characters is taken as a list of forbidden
|
the following sequence of characters is taken as a list of forbidden
|
||||||
modifiers. For example, in the test files that must not use UTF or Uni-
|
modifiers. For example, in the test files that must not use UTF or Uni-
|
||||||
code property support, this line appears:
|
code property support, this line appears:
|
||||||
|
|
||||||
< forbid 8W
|
< forbid 8W
|
||||||
|
|
||||||
This locks out the /8 and /W modifiers. An immediate error is given if
|
This locks out the /8 and /W modifiers. An immediate error is given if
|
||||||
they are subsequently encountered. If the character string contains <
|
they are subsequently encountered. If the character string contains <
|
||||||
but not >, all the multi-character modifiers that begin with < are
|
but not >, all the multi-character modifiers that begin with < are
|
||||||
locked out. Otherwise, such modifiers must be explicitly listed, for
|
locked out. Otherwise, such modifiers must be explicitly listed, for
|
||||||
example:
|
example:
|
||||||
|
|
||||||
< forbid <JS><cr>
|
< forbid <JS><cr>
|
||||||
|
|
||||||
There must be a single space between < and "forbid" for this feature to
|
There must be a single space between < and "forbid" for this feature to
|
||||||
be recognised. If there is not, the line is interpreted either as a
|
be recognised. If there is not, the line is interpreted either as a re-
|
||||||
request to re-load a pre-compiled pattern (see "SAVING AND RELOADING
|
quest to re-load a pre-compiled pattern (see "SAVING AND RELOADING COM-
|
||||||
COMPILED PATTERNS" below) or, if there is a another < character, as a
|
PILED PATTERNS" below) or, if there is a another < character, as a pat-
|
||||||
pattern that uses < as its delimiter.
|
tern that uses < as its delimiter.
|
||||||
|
|
||||||
|
|
||||||
DATA LINES
|
DATA LINES
|
||||||
|
|
||||||
Before each data line is passed to pcre[16|32]_exec(), leading and
|
Before each data line is passed to pcre[16|32]_exec(), leading and
|
||||||
trailing white space is removed, and it is then scanned for \ escapes.
|
trailing white space is removed, and it is then scanned for \ escapes.
|
||||||
Some of these are pretty esoteric features, intended for checking out
|
Some of these are pretty esoteric features, intended for checking out
|
||||||
some of the more complicated features of PCRE. If you are just testing
|
some of the more complicated features of PCRE. If you are just testing
|
||||||
"ordinary" regular expressions, you probably don't need any of these.
|
"ordinary" regular expressions, you probably don't need any of these.
|
||||||
The following escapes are recognized:
|
The following escapes are recognized:
|
||||||
|
|
||||||
\a alarm (BEL, \x07)
|
\a alarm (BEL, \x07)
|
||||||
@ -684,7 +681,7 @@ DATA LINES
|
|||||||
(any number of digits)
|
(any number of digits)
|
||||||
\R pass the PCRE_DFA_RESTART option to pcre[16|32]_dfa_exec()
|
\R pass the PCRE_DFA_RESTART option to pcre[16|32]_dfa_exec()
|
||||||
\S output details of memory get/free calls during matching
|
\S output details of memory get/free calls during matching
|
||||||
\Y pass the PCRE_NO_START_OPTIMIZE option to
|
\Y pass the PCRE_NO_START_OPTIMIZE option to
|
||||||
pcre[16|32]_exec()
|
pcre[16|32]_exec()
|
||||||
or pcre[16|32]_dfa_exec()
|
or pcre[16|32]_dfa_exec()
|
||||||
\Z pass the PCRE_NOTEOL option to pcre[16|32]_exec()
|
\Z pass the PCRE_NOTEOL option to pcre[16|32]_exec()
|
||||||
@ -693,7 +690,7 @@ DATA LINES
|
|||||||
pcre[16|32]_exec() or pcre[16|32]_dfa_exec()
|
pcre[16|32]_exec() or pcre[16|32]_dfa_exec()
|
||||||
\>dd start the match at offset dd (optional "-"; then
|
\>dd start the match at offset dd (optional "-"; then
|
||||||
any number of digits); this sets the startoffset
|
any number of digits); this sets the startoffset
|
||||||
argument for pcre[16|32]_exec() or
|
argument for pcre[16|32]_exec() or
|
||||||
pcre[16|32]_dfa_exec()
|
pcre[16|32]_dfa_exec()
|
||||||
\<cr> pass the PCRE_NEWLINE_CR option to pcre[16|32]_exec()
|
\<cr> pass the PCRE_NEWLINE_CR option to pcre[16|32]_exec()
|
||||||
or pcre[16|32]_dfa_exec()
|
or pcre[16|32]_dfa_exec()
|
||||||
@ -706,103 +703,102 @@ DATA LINES
|
|||||||
\<any> pass the PCRE_NEWLINE_ANY option to pcre[16|32]_exec()
|
\<any> pass the PCRE_NEWLINE_ANY option to pcre[16|32]_exec()
|
||||||
or pcre[16|32]_dfa_exec()
|
or pcre[16|32]_dfa_exec()
|
||||||
|
|
||||||
The use of \x{hh...} is not dependent on the use of the /8 modifier on
|
The use of \x{hh...} is not dependent on the use of the /8 modifier on
|
||||||
the pattern. It is recognized always. There may be any number of hexa-
|
the pattern. It is recognized always. There may be any number of hexa-
|
||||||
decimal digits inside the braces; invalid values provoke error mes-
|
decimal digits inside the braces; invalid values provoke error mes-
|
||||||
sages.
|
sages.
|
||||||
|
|
||||||
Note that \xhh specifies one byte rather than one character in UTF-8
|
Note that \xhh specifies one byte rather than one character in UTF-8
|
||||||
mode; this makes it possible to construct invalid UTF-8 sequences for
|
mode; this makes it possible to construct invalid UTF-8 sequences for
|
||||||
testing purposes. On the other hand, \x{hh} is interpreted as a UTF-8
|
testing purposes. On the other hand, \x{hh} is interpreted as a UTF-8
|
||||||
character in UTF-8 mode, generating more than one byte if the value is
|
character in UTF-8 mode, generating more than one byte if the value is
|
||||||
greater than 127. When testing the 8-bit library not in UTF-8 mode,
|
greater than 127. When testing the 8-bit library not in UTF-8 mode,
|
||||||
\x{hh} generates one byte for values less than 256, and causes an error
|
\x{hh} generates one byte for values less than 256, and causes an error
|
||||||
for greater values.
|
for greater values.
|
||||||
|
|
||||||
In UTF-16 mode, all 4-digit \x{hhhh} values are accepted. This makes it
|
In UTF-16 mode, all 4-digit \x{hhhh} values are accepted. This makes it
|
||||||
possible to construct invalid UTF-16 sequences for testing purposes.
|
possible to construct invalid UTF-16 sequences for testing purposes.
|
||||||
|
|
||||||
In UTF-32 mode, all 4- to 8-digit \x{...} values are accepted. This
|
In UTF-32 mode, all 4- to 8-digit \x{...} values are accepted. This
|
||||||
makes it possible to construct invalid UTF-32 sequences for testing
|
makes it possible to construct invalid UTF-32 sequences for testing
|
||||||
purposes.
|
purposes.
|
||||||
|
|
||||||
The escapes that specify line ending sequences are literal strings,
|
The escapes that specify line ending sequences are literal strings, ex-
|
||||||
exactly as shown. No more than one newline setting should be present in
|
actly as shown. No more than one newline setting should be present in
|
||||||
any data line.
|
any data line.
|
||||||
|
|
||||||
A backslash followed by anything else just escapes the anything else.
|
A backslash followed by anything else just escapes the anything else.
|
||||||
If the very last character is a backslash, it is ignored. This gives a
|
If the very last character is a backslash, it is ignored. This gives a
|
||||||
way of passing an empty line as data, since a real empty line termi-
|
way of passing an empty line as data, since a real empty line termi-
|
||||||
nates the data input.
|
nates the data input.
|
||||||
|
|
||||||
The \J escape provides a way of setting the maximum stack size that is
|
The \J escape provides a way of setting the maximum stack size that is
|
||||||
used by the just-in-time optimization code. It is ignored if JIT opti-
|
used by the just-in-time optimization code. It is ignored if JIT opti-
|
||||||
mization is not being used. Providing a stack that is larger than the
|
mization is not being used. Providing a stack that is larger than the
|
||||||
default 32K is necessary only for very complicated patterns.
|
default 32K is necessary only for very complicated patterns.
|
||||||
|
|
||||||
If \M is present, pcretest calls pcre[16|32]_exec() several times, with
|
If \M is present, pcretest calls pcre[16|32]_exec() several times, with
|
||||||
different values in the match_limit and match_limit_recursion fields of
|
different values in the match_limit and match_limit_recursion fields of
|
||||||
the pcre[16|32]_extra data structure, until it finds the minimum num-
|
the pcre[16|32]_extra data structure, until it finds the minimum num-
|
||||||
bers for each parameter that allow pcre[16|32]_exec() to complete with-
|
bers for each parameter that allow pcre[16|32]_exec() to complete with-
|
||||||
out error. Because this is testing a specific feature of the normal
|
out error. Because this is testing a specific feature of the normal in-
|
||||||
interpretive pcre[16|32]_exec() execution, the use of any JIT optimiza-
|
terpretive pcre[16|32]_exec() execution, the use of any JIT optimiza-
|
||||||
tion that might have been set up by the /S+ qualifier of -s+ option is
|
tion that might have been set up by the /S+ qualifier of -s+ option is
|
||||||
disabled.
|
disabled.
|
||||||
|
|
||||||
The match_limit number is a measure of the amount of backtracking that
|
The match_limit number is a measure of the amount of backtracking that
|
||||||
takes place, and checking it out can be instructive. For most simple
|
takes place, and checking it out can be instructive. For most simple
|
||||||
matches, the number is quite small, but for patterns with very large
|
matches, the number is quite small, but for patterns with very large
|
||||||
numbers of matching possibilities, it can become large very quickly
|
numbers of matching possibilities, it can become large very quickly
|
||||||
with increasing length of subject string. The match_limit_recursion
|
with increasing length of subject string. The match_limit_recursion
|
||||||
number is a measure of how much stack (or, if PCRE is compiled with
|
number is a measure of how much stack (or, if PCRE is compiled with
|
||||||
NO_RECURSE, how much heap) memory is needed to complete the match
|
NO_RECURSE, how much heap) memory is needed to complete the match at-
|
||||||
attempt.
|
tempt.
|
||||||
|
|
||||||
When \O is used, the value specified may be higher or lower than the
|
When \O is used, the value specified may be higher or lower than the
|
||||||
size set by the -O command line option (or defaulted to 45); \O applies
|
size set by the -O command line option (or defaulted to 45); \O applies
|
||||||
only to the call of pcre[16|32]_exec() for the line in which it
|
only to the call of pcre[16|32]_exec() for the line in which it ap-
|
||||||
appears.
|
pears.
|
||||||
|
|
||||||
If the /P modifier was present on the pattern, causing the POSIX wrap-
|
If the /P modifier was present on the pattern, causing the POSIX wrap-
|
||||||
per API to be used, the only option-setting sequences that have any
|
per API to be used, the only option-setting sequences that have any ef-
|
||||||
effect are \B, \N, and \Z, causing REG_NOTBOL, REG_NOTEMPTY, and
|
fect are \B, \N, and \Z, causing REG_NOTBOL, REG_NOTEMPTY, and REG_NO-
|
||||||
REG_NOTEOL, respectively, to be passed to regexec().
|
TEOL, respectively, to be passed to regexec().
|
||||||
|
|
||||||
|
|
||||||
THE ALTERNATIVE MATCHING FUNCTION
|
THE ALTERNATIVE MATCHING FUNCTION
|
||||||
|
|
||||||
By default, pcretest uses the standard PCRE matching function,
|
By default, pcretest uses the standard PCRE matching function,
|
||||||
pcre[16|32]_exec() to match each data line. PCRE also supports an
|
pcre[16|32]_exec() to match each data line. PCRE also supports an al-
|
||||||
alternative matching function, pcre[16|32]_dfa_test(), which operates
|
ternative matching function, pcre[16|32]_dfa_test(), which operates in
|
||||||
in a different way, and has some restrictions. The differences between
|
a different way, and has some restrictions. The differences between the
|
||||||
the two functions are described in the pcrematching documentation.
|
two functions are described in the pcrematching documentation.
|
||||||
|
|
||||||
If a data line contains the \D escape sequence, or if the command line
|
If a data line contains the \D escape sequence, or if the command line
|
||||||
contains the -dfa option, the alternative matching function is used.
|
contains the -dfa option, the alternative matching function is used.
|
||||||
This function finds all possible matches at a given point. If, however,
|
This function finds all possible matches at a given point. If, however,
|
||||||
the \F escape sequence is present in the data line, it stops after the
|
the \F escape sequence is present in the data line, it stops after the
|
||||||
first match is found. This is always the shortest possible match.
|
first match is found. This is always the shortest possible match.
|
||||||
|
|
||||||
|
|
||||||
DEFAULT OUTPUT FROM PCRETEST
|
DEFAULT OUTPUT FROM PCRETEST
|
||||||
|
|
||||||
This section describes the output when the normal matching function,
|
This section describes the output when the normal matching function,
|
||||||
pcre[16|32]_exec(), is being used.
|
pcre[16|32]_exec(), is being used.
|
||||||
|
|
||||||
When a match succeeds, pcretest outputs the list of captured substrings
|
When a match succeeds, pcretest outputs the list of captured substrings
|
||||||
that pcre[16|32]_exec() returns, starting with number 0 for the string
|
that pcre[16|32]_exec() returns, starting with number 0 for the string
|
||||||
that matched the whole pattern. Otherwise, it outputs "No match" when
|
that matched the whole pattern. Otherwise, it outputs "No match" when
|
||||||
the return is PCRE_ERROR_NOMATCH, and "Partial match:" followed by the
|
the return is PCRE_ERROR_NOMATCH, and "Partial match:" followed by the
|
||||||
partially matching substring when pcre[16|32]_exec() returns
|
partially matching substring when pcre[16|32]_exec() returns PCRE_ER-
|
||||||
PCRE_ERROR_PARTIAL. (Note that this is the entire substring that was
|
ROR_PARTIAL. (Note that this is the entire substring that was inspected
|
||||||
inspected during the partial match; it may include characters before
|
during the partial match; it may include characters before the actual
|
||||||
the actual match start if a lookbehind assertion, \K, \b, or \B was
|
match start if a lookbehind assertion, \K, \b, or \B was involved.) For
|
||||||
involved.) For any other return, pcretest outputs the PCRE negative
|
any other return, pcretest outputs the PCRE negative error number and a
|
||||||
error number and a short descriptive phrase. If the error is a failed
|
short descriptive phrase. If the error is a failed UTF string check,
|
||||||
UTF string check, the offset of the start of the failing character and
|
the offset of the start of the failing character and the reason code
|
||||||
the reason code are also output, provided that the size of the output
|
are also output, provided that the size of the output vector is at
|
||||||
vector is at least two. Here is an example of an interactive pcretest
|
least two. Here is an example of an interactive pcretest run.
|
||||||
run.
|
|
||||||
|
|
||||||
$ pcretest
|
$ pcretest
|
||||||
PCRE version 8.13 2011-04-30
|
PCRE version 8.13 2011-04-30
|
||||||
@ -892,9 +888,9 @@ OUTPUT FROM THE ALTERNATIVE MATCHING FUNCTION
|
|||||||
(Using the normal matching function on this data finds only "tang".)
|
(Using the normal matching function on this data finds only "tang".)
|
||||||
The longest matching string is always given first (and numbered zero).
|
The longest matching string is always given first (and numbered zero).
|
||||||
After a PCRE_ERROR_PARTIAL return, the output is "Partial match:", fol-
|
After a PCRE_ERROR_PARTIAL return, the output is "Partial match:", fol-
|
||||||
lowed by the partially matching substring. (Note that this is the
|
lowed by the partially matching substring. (Note that this is the en-
|
||||||
entire substring that was inspected during the partial match; it may
|
tire substring that was inspected during the partial match; it may in-
|
||||||
include characters before the actual match start if a lookbehind asser-
|
clude characters before the actual match start if a lookbehind asser-
|
||||||
tion, \K, \b, or \B was involved.)
|
tion, \K, \b, or \B was involved.)
|
||||||
|
|
||||||
If /g is present on the pattern, the search for further matches resumes
|
If /g is present on the pattern, the search for further matches resumes
|
||||||
@ -909,9 +905,9 @@ OUTPUT FROM THE ALTERNATIVE MATCHING FUNCTION
|
|||||||
1: tan
|
1: tan
|
||||||
0: tan
|
0: tan
|
||||||
|
|
||||||
Since the matching function does not support substring capture, the
|
Since the matching function does not support substring capture, the es-
|
||||||
escape sequences that are concerned with captured substrings are not
|
cape sequences that are concerned with captured substrings are not rel-
|
||||||
relevant.
|
evant.
|
||||||
|
|
||||||
|
|
||||||
RESTARTING AFTER A PARTIAL MATCH
|
RESTARTING AFTER A PARTIAL MATCH
|
||||||
@ -942,9 +938,9 @@ CALLOUTS
|
|||||||
--->pqrabcdef
|
--->pqrabcdef
|
||||||
0 ^ ^ \d
|
0 ^ ^ \d
|
||||||
|
|
||||||
This output indicates that callout number 0 occurred for a match
|
This output indicates that callout number 0 occurred for a match at-
|
||||||
attempt starting at the fourth character of the subject string, when
|
tempt starting at the fourth character of the subject string, when the
|
||||||
the pointer was at the seventh character of the data, and when the next
|
pointer was at the seventh character of the data, and when the next
|
||||||
pattern item was \d. Just one circumflex is output if the start and
|
pattern item was \d. Just one circumflex is output if the start and
|
||||||
current positions are the same.
|
current positions are the same.
|
||||||
|
|
||||||
@ -963,8 +959,8 @@ CALLOUTS
|
|||||||
0: E*
|
0: E*
|
||||||
|
|
||||||
If a pattern contains (*MARK) items, an additional line is output when-
|
If a pattern contains (*MARK) items, an additional line is output when-
|
||||||
ever a change of latest mark is passed to the callout function. For
|
ever a change of latest mark is passed to the callout function. For ex-
|
||||||
example:
|
ample:
|
||||||
|
|
||||||
re> /a(*MARK:X)bc/C
|
re> /a(*MARK:X)bc/C
|
||||||
data> abc
|
data> abc
|
||||||
@ -999,8 +995,8 @@ NON-PRINTING CHARACTERS
|
|||||||
|
|
||||||
When pcretest is outputting text that is a matched part of a subject
|
When pcretest is outputting text that is a matched part of a subject
|
||||||
string, it behaves in the same way, unless a different locale has been
|
string, it behaves in the same way, unless a different locale has been
|
||||||
set for the pattern (using the /L modifier). In this case, the
|
set for the pattern (using the /L modifier). In this case, the is-
|
||||||
isprint() function to distinguish printing and non-printing characters.
|
print() function to distinguish printing and non-printing characters.
|
||||||
|
|
||||||
|
|
||||||
SAVING AND RELOADING COMPILED PATTERNS
|
SAVING AND RELOADING COMPILED PATTERNS
|
||||||
@ -1020,14 +1016,14 @@ SAVING AND RELOADING COMPILED PATTERNS
|
|||||||
studied with JIT optimization, the JIT data cannot be saved.
|
studied with JIT optimization, the JIT data cannot be saved.
|
||||||
|
|
||||||
The data that is written is binary. The first eight bytes are the
|
The data that is written is binary. The first eight bytes are the
|
||||||
length of the compiled pattern data followed by the length of the
|
length of the compiled pattern data followed by the length of the op-
|
||||||
optional study data, each written as four bytes in big-endian order
|
tional study data, each written as four bytes in big-endian order (most
|
||||||
(most significant byte first). If there is no study data (either the
|
significant byte first). If there is no study data (either the pattern
|
||||||
pattern was not studied, or studying did not return any data), the sec-
|
was not studied, or studying did not return any data), the second
|
||||||
ond length is zero. The lengths are followed by an exact copy of the
|
length is zero. The lengths are followed by an exact copy of the com-
|
||||||
compiled pattern. If there is additional study data, this (excluding
|
piled pattern. If there is additional study data, this (excluding any
|
||||||
any JIT data) follows immediately after the compiled pattern. After
|
JIT data) follows immediately after the compiled pattern. After writing
|
||||||
writing the file, pcretest expects to read a new pattern.
|
the file, pcretest expects to read a new pattern.
|
||||||
|
|
||||||
A saved pattern can be reloaded into pcretest by specifying < and a
|
A saved pattern can be reloaded into pcretest by specifying < and a
|
||||||
file name instead of a pattern. There must be no space between < and
|
file name instead of a pattern. There must be no space between < and
|
||||||
@ -1066,10 +1062,10 @@ SAVING AND RELOADING COMPILED PATTERNS
|
|||||||
ing and experimentation. It is not intended for production use because
|
ing and experimentation. It is not intended for production use because
|
||||||
only a single pattern can be written to a file. Furthermore, there is
|
only a single pattern can be written to a file. Furthermore, there is
|
||||||
no facility for supplying custom character tables for use with a
|
no facility for supplying custom character tables for use with a
|
||||||
reloaded pattern. If the original pattern was compiled with custom
|
reloaded pattern. If the original pattern was compiled with custom ta-
|
||||||
tables, an attempt to match a subject string using a reloaded pattern
|
bles, an attempt to match a subject string using a reloaded pattern is
|
||||||
is likely to cause pcretest to crash. Finally, if you attempt to load
|
likely to cause pcretest to crash. Finally, if you attempt to load a
|
||||||
a file that is not in the correct format, the result is undefined.
|
file that is not in the correct format, the result is undefined.
|
||||||
|
|
||||||
|
|
||||||
SEE ALSO
|
SEE ALSO
|
||||||
@ -1087,5 +1083,5 @@ AUTHOR
|
|||||||
|
|
||||||
REVISION
|
REVISION
|
||||||
|
|
||||||
Last updated: 23 February 2017
|
Last updated: 10 February 2020
|
||||||
Copyright (c) 1997-2017 University of Cambridge.
|
Copyright (c) 1997-2020 University of Cambridge.
|
||||||
|
@ -6,7 +6,7 @@
|
|||||||
and semantics are as close as possible to those of the Perl 5 language.
|
and semantics are as close as possible to those of the Perl 5 language.
|
||||||
|
|
||||||
Written by Philip Hazel
|
Written by Philip Hazel
|
||||||
Copyright (c) 1997-2018 University of Cambridge
|
Copyright (c) 1997-2020 University of Cambridge
|
||||||
|
|
||||||
-----------------------------------------------------------------------------
|
-----------------------------------------------------------------------------
|
||||||
Redistribution and use in source and binary forms, with or without
|
Redistribution and use in source and binary forms, with or without
|
||||||
@ -68,7 +68,7 @@ COMPILE_PCREx macro will already be appropriately set. */
|
|||||||
|
|
||||||
/* Macro for setting individual bits in class bitmaps. */
|
/* Macro for setting individual bits in class bitmaps. */
|
||||||
|
|
||||||
#define SETBIT(a,b) a[(b)/8] |= (1 << ((b)&7))
|
#define SETBIT(a,b) a[(b)/8] |= (1U << ((b)&7))
|
||||||
|
|
||||||
/* Maximum length value to check against when making sure that the integer that
|
/* Maximum length value to check against when making sure that the integer that
|
||||||
holds the compiled pattern length does not overflow. We make it a bit less than
|
holds the compiled pattern length does not overflow. We make it a bit less than
|
||||||
@ -129,8 +129,8 @@ overrun before it actually does run off the end of the data block. */
|
|||||||
|
|
||||||
/* Private flags added to firstchar and reqchar. */
|
/* Private flags added to firstchar and reqchar. */
|
||||||
|
|
||||||
#define REQ_CASELESS (1 << 0) /* Indicates caselessness */
|
#define REQ_CASELESS (1U << 0) /* Indicates caselessness */
|
||||||
#define REQ_VARY (1 << 1) /* Reqchar followed non-literal item */
|
#define REQ_VARY (1U << 1) /* Reqchar followed non-literal item */
|
||||||
/* Negative values for the firstchar and reqchar flags */
|
/* Negative values for the firstchar and reqchar flags */
|
||||||
#define REQ_UNSET (-2)
|
#define REQ_UNSET (-2)
|
||||||
#define REQ_NONE (-1)
|
#define REQ_NONE (-1)
|
||||||
@ -3612,7 +3612,7 @@ for(;;)
|
|||||||
if (chr > 255) break;
|
if (chr > 255) break;
|
||||||
class_bitset = (pcre_uint8 *)
|
class_bitset = (pcre_uint8 *)
|
||||||
((list_ptr == list ? code : base_end) - list_ptr[2]);
|
((list_ptr == list ? code : base_end) - list_ptr[2]);
|
||||||
if ((class_bitset[chr >> 3] & (1 << (chr & 7))) != 0) return FALSE;
|
if ((class_bitset[chr >> 3] & (1U << (chr & 7))) != 0) return FALSE;
|
||||||
break;
|
break;
|
||||||
|
|
||||||
#if defined SUPPORT_UTF || !defined COMPILE_PCRE8
|
#if defined SUPPORT_UTF || !defined COMPILE_PCRE8
|
||||||
@ -7133,17 +7133,19 @@ for (;; ptr++)
|
|||||||
int n = 0;
|
int n = 0;
|
||||||
ptr++;
|
ptr++;
|
||||||
while(IS_DIGIT(*ptr))
|
while(IS_DIGIT(*ptr))
|
||||||
|
{
|
||||||
n = n * 10 + *ptr++ - CHAR_0;
|
n = n * 10 + *ptr++ - CHAR_0;
|
||||||
|
if (n > 255)
|
||||||
|
{
|
||||||
|
*errorcodeptr = ERR38;
|
||||||
|
goto FAILED;
|
||||||
|
}
|
||||||
|
}
|
||||||
if (*ptr != CHAR_RIGHT_PARENTHESIS)
|
if (*ptr != CHAR_RIGHT_PARENTHESIS)
|
||||||
{
|
{
|
||||||
*errorcodeptr = ERR39;
|
*errorcodeptr = ERR39;
|
||||||
goto FAILED;
|
goto FAILED;
|
||||||
}
|
}
|
||||||
if (n > 255)
|
|
||||||
{
|
|
||||||
*errorcodeptr = ERR38;
|
|
||||||
goto FAILED;
|
|
||||||
}
|
|
||||||
*code++ = n;
|
*code++ = n;
|
||||||
PUT(code, 0, (int)(ptr - cd->start_pattern + 1)); /* Pattern offset */
|
PUT(code, 0, (int)(ptr - cd->start_pattern + 1)); /* Pattern offset */
|
||||||
PUT(code, LINK_SIZE, 0); /* Default length */
|
PUT(code, LINK_SIZE, 0); /* Default length */
|
||||||
@ -7459,7 +7461,7 @@ for (;; ptr++)
|
|||||||
{
|
{
|
||||||
open_capitem *oc;
|
open_capitem *oc;
|
||||||
recno = GET2(slot, 0);
|
recno = GET2(slot, 0);
|
||||||
cd->backref_map |= (recno < 32)? (1 << recno) : 1;
|
cd->backref_map |= (recno < 32)? (1U << recno) : 1;
|
||||||
if (recno > cd->top_backref) cd->top_backref = recno;
|
if (recno > cd->top_backref) cd->top_backref = recno;
|
||||||
|
|
||||||
/* Check to see if this back reference is recursive, that it, it
|
/* Check to see if this back reference is recursive, that it, it
|
||||||
@ -8070,7 +8072,7 @@ for (;; ptr++)
|
|||||||
item_hwm_offset = cd->hwm - cd->start_workspace;
|
item_hwm_offset = cd->hwm - cd->start_workspace;
|
||||||
*code++ = ((options & PCRE_CASELESS) != 0)? OP_REFI : OP_REF;
|
*code++ = ((options & PCRE_CASELESS) != 0)? OP_REFI : OP_REF;
|
||||||
PUT2INC(code, 0, recno);
|
PUT2INC(code, 0, recno);
|
||||||
cd->backref_map |= (recno < 32)? (1 << recno) : 1;
|
cd->backref_map |= (recno < 32)? (1U << recno) : 1;
|
||||||
if (recno > cd->top_backref) cd->top_backref = recno;
|
if (recno > cd->top_backref) cd->top_backref = recno;
|
||||||
|
|
||||||
/* Check to see if this back reference is recursive, that it, it
|
/* Check to see if this back reference is recursive, that it, it
|
||||||
@ -8683,7 +8685,7 @@ do {
|
|||||||
op == OP_SCBRA || op == OP_SCBRAPOS)
|
op == OP_SCBRA || op == OP_SCBRAPOS)
|
||||||
{
|
{
|
||||||
int n = GET2(scode, 1+LINK_SIZE);
|
int n = GET2(scode, 1+LINK_SIZE);
|
||||||
int new_map = bracket_map | ((n < 32)? (1 << n) : 1);
|
int new_map = bracket_map | ((n < 32)? (1U << n) : 1);
|
||||||
if (!is_anchored(scode, new_map, cd, atomcount)) return FALSE;
|
if (!is_anchored(scode, new_map, cd, atomcount)) return FALSE;
|
||||||
}
|
}
|
||||||
|
|
||||||
@ -8811,7 +8813,7 @@ do {
|
|||||||
op == OP_SCBRA || op == OP_SCBRAPOS)
|
op == OP_SCBRA || op == OP_SCBRAPOS)
|
||||||
{
|
{
|
||||||
int n = GET2(scode, 1+LINK_SIZE);
|
int n = GET2(scode, 1+LINK_SIZE);
|
||||||
int new_map = bracket_map | ((n < 32)? (1 << n) : 1);
|
int new_map = bracket_map | ((n < 32)? (1U << n) : 1);
|
||||||
if (!is_startline(scode, new_map, cd, atomcount, inassert)) return FALSE;
|
if (!is_startline(scode, new_map, cd, atomcount, inassert)) return FALSE;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
@ -3938,10 +3938,10 @@ static sljit_s32 character_to_int32(pcre_uchar chr)
|
|||||||
sljit_s32 value = (sljit_s32)chr;
|
sljit_s32 value = (sljit_s32)chr;
|
||||||
#if defined COMPILE_PCRE8
|
#if defined COMPILE_PCRE8
|
||||||
#define SSE2_COMPARE_TYPE_INDEX 0
|
#define SSE2_COMPARE_TYPE_INDEX 0
|
||||||
return (value << 24) | (value << 16) | (value << 8) | value;
|
return ((unsigned int)value << 24) | ((unsigned int)value << 16) | ((unsigned int)value << 8) | (unsigned int)value;
|
||||||
#elif defined COMPILE_PCRE16
|
#elif defined COMPILE_PCRE16
|
||||||
#define SSE2_COMPARE_TYPE_INDEX 1
|
#define SSE2_COMPARE_TYPE_INDEX 1
|
||||||
return (value << 16) | value;
|
return ((unsigned int)value << 16) | value;
|
||||||
#elif defined COMPILE_PCRE32
|
#elif defined COMPILE_PCRE32
|
||||||
#define SSE2_COMPARE_TYPE_INDEX 2
|
#define SSE2_COMPARE_TYPE_INDEX 2
|
||||||
return value;
|
return value;
|
||||||
@ -8507,7 +8507,7 @@ if (opcode == OP_ONCE)
|
|||||||
/* We temporarily encode the needs_control_head in the lowest bit.
|
/* We temporarily encode the needs_control_head in the lowest bit.
|
||||||
Note: on the target architectures of SLJIT the ((x << 1) >> 1) returns
|
Note: on the target architectures of SLJIT the ((x << 1) >> 1) returns
|
||||||
the same value for small signed numbers (including negative numbers). */
|
the same value for small signed numbers (including negative numbers). */
|
||||||
BACKTRACK_AS(bracket_backtrack)->u.framesize = (BACKTRACK_AS(bracket_backtrack)->u.framesize << 1) | (needs_control_head ? 1 : 0);
|
BACKTRACK_AS(bracket_backtrack)->u.framesize = ((unsigned int)BACKTRACK_AS(bracket_backtrack)->u.framesize << 1) | (needs_control_head ? 1 : 0);
|
||||||
}
|
}
|
||||||
return cc + repeat_length;
|
return cc + repeat_length;
|
||||||
}
|
}
|
||||||
|
@ -66,7 +66,8 @@ Arg RE::no_arg((void*)NULL);
|
|||||||
// inclusive test if we ever needed it. (Note that not only the
|
// inclusive test if we ever needed it. (Note that not only the
|
||||||
// __attribute__ syntax, but also __USER_LABEL_PREFIX__, are
|
// __attribute__ syntax, but also __USER_LABEL_PREFIX__, are
|
||||||
// gnu-specific.)
|
// gnu-specific.)
|
||||||
#if defined(__GNUC__) && __GNUC__ >= 3 && defined(__ELF__) && !defined(__INTEL_COMPILER)
|
#if defined(__GNUC__) && __GNUC__ >= 3 && defined(__ELF__) \
|
||||||
|
&& !defined(__INTEL_COMPILER) && !defined(__LCC__)
|
||||||
# define ULP_AS_STRING(x) ULP_AS_STRING_INTERNAL(x)
|
# define ULP_AS_STRING(x) ULP_AS_STRING_INTERNAL(x)
|
||||||
# define ULP_AS_STRING_INTERNAL(x) #x
|
# define ULP_AS_STRING_INTERNAL(x) #x
|
||||||
# define USER_LABEL_PREFIX_STR ULP_AS_STRING(__USER_LABEL_PREFIX__)
|
# define USER_LABEL_PREFIX_STR ULP_AS_STRING(__USER_LABEL_PREFIX__)
|
||||||
@ -91,6 +92,7 @@ static const char *start_options[] = {
|
|||||||
"(*LIMIT_RECURSION=",
|
"(*LIMIT_RECURSION=",
|
||||||
"(*LIMIT_MATCH=",
|
"(*LIMIT_MATCH=",
|
||||||
"(*CRLF)",
|
"(*CRLF)",
|
||||||
|
"(*LF)",
|
||||||
"(*CR)",
|
"(*CR)",
|
||||||
"(*BSR_UNICODE)",
|
"(*BSR_UNICODE)",
|
||||||
"(*BSR_ANYCRLF)",
|
"(*BSR_ANYCRLF)",
|
||||||
|
@ -6,7 +6,7 @@
|
|||||||
and semantics are as close as possible to those of the Perl 5 language.
|
and semantics are as close as possible to those of the Perl 5 language.
|
||||||
|
|
||||||
Written by Philip Hazel
|
Written by Philip Hazel
|
||||||
Copyright (c) 1997-2018 University of Cambridge
|
Copyright (c) 1997-2020 University of Cambridge
|
||||||
|
|
||||||
-----------------------------------------------------------------------------
|
-----------------------------------------------------------------------------
|
||||||
Redistribution and use in source and binary forms, with or without
|
Redistribution and use in source and binary forms, with or without
|
||||||
@ -298,6 +298,7 @@ if (preg->re_pcre == NULL)
|
|||||||
(void)pcre_fullinfo((const pcre *)preg->re_pcre, NULL, PCRE_INFO_CAPTURECOUNT,
|
(void)pcre_fullinfo((const pcre *)preg->re_pcre, NULL, PCRE_INFO_CAPTURECOUNT,
|
||||||
&re_nsub);
|
&re_nsub);
|
||||||
preg->re_nsub = (size_t)re_nsub;
|
preg->re_nsub = (size_t)re_nsub;
|
||||||
|
preg->re_erroffset = (size_t)(-1); /* No meaning after successful compile */
|
||||||
return 0;
|
return 0;
|
||||||
}
|
}
|
||||||
|
|
||||||
@ -335,8 +336,6 @@ if ((eflags & REG_NOTBOL) != 0) options |= PCRE_NOTBOL;
|
|||||||
if ((eflags & REG_NOTEOL) != 0) options |= PCRE_NOTEOL;
|
if ((eflags & REG_NOTEOL) != 0) options |= PCRE_NOTEOL;
|
||||||
if ((eflags & REG_NOTEMPTY) != 0) options |= PCRE_NOTEMPTY;
|
if ((eflags & REG_NOTEMPTY) != 0) options |= PCRE_NOTEMPTY;
|
||||||
|
|
||||||
((regex_t *)preg)->re_erroffset = (size_t)(-1); /* Only has meaning after compile */
|
|
||||||
|
|
||||||
/* When no string data is being returned, or no vector has been passed in which
|
/* When no string data is being returned, or no vector has been passed in which
|
||||||
to put it, ensure that nmatch is zero. Otherwise, ensure the vector for holding
|
to put it, ensure that nmatch is zero. Otherwise, ensure the vector for holding
|
||||||
the return data is large enough. */
|
the return data is large enough. */
|
||||||
|
@ -500,7 +500,7 @@ enum {
|
|||||||
#if (defined (SUPPORT_PCRE8) + defined (SUPPORT_PCRE16) + \
|
#if (defined (SUPPORT_PCRE8) + defined (SUPPORT_PCRE16) + \
|
||||||
defined (SUPPORT_PCRE32)) >= 2
|
defined (SUPPORT_PCRE32)) >= 2
|
||||||
|
|
||||||
#define CHAR_SIZE (1 << pcre_mode)
|
#define CHAR_SIZE (1U << pcre_mode)
|
||||||
|
|
||||||
/* There doesn't seem to be an easy way of writing these macros that can cope
|
/* There doesn't seem to be an easy way of writing these macros that can cope
|
||||||
with the 3 pairs of bit sizes plus all three bit sizes. So just handle all the
|
with the 3 pairs of bit sizes plus all three bit sizes. So just handle all the
|
||||||
@ -4443,7 +4443,7 @@ while (!done)
|
|||||||
|
|
||||||
/* If there is study data, write it. */
|
/* If there is study data, write it. */
|
||||||
|
|
||||||
if (extra != NULL)
|
if (extra != NULL && (extra->flags & PCRE_EXTRA_STUDY_DATA) != 0)
|
||||||
{
|
{
|
||||||
if (fwrite(extra->study_data, 1, true_study_size, f) <
|
if (fwrite(extra->study_data, 1, true_study_size, f) <
|
||||||
true_study_size)
|
true_study_size)
|
||||||
@ -4735,7 +4735,7 @@ while (!done)
|
|||||||
if (isdigit(*p)) /* Set copy string */
|
if (isdigit(*p)) /* Set copy string */
|
||||||
{
|
{
|
||||||
while(isdigit(*p)) n = n * 10 + *p++ - '0';
|
while(isdigit(*p)) n = n * 10 + *p++ - '0';
|
||||||
copystrings |= 1 << n;
|
copystrings |= 1U << n;
|
||||||
}
|
}
|
||||||
else if (isalnum(*p))
|
else if (isalnum(*p))
|
||||||
{
|
{
|
||||||
@ -4798,7 +4798,7 @@ while (!done)
|
|||||||
if (isdigit(*p))
|
if (isdigit(*p))
|
||||||
{
|
{
|
||||||
while(isdigit(*p)) n = n * 10 + *p++ - '0';
|
while(isdigit(*p)) n = n * 10 + *p++ - '0';
|
||||||
getstrings |= 1 << n;
|
getstrings |= 1U << n;
|
||||||
}
|
}
|
||||||
else if (isalnum(*p))
|
else if (isalnum(*p))
|
||||||
{
|
{
|
||||||
@ -5335,7 +5335,7 @@ while (!done)
|
|||||||
|
|
||||||
for (i = 0; i < 32; i++)
|
for (i = 0; i < 32; i++)
|
||||||
{
|
{
|
||||||
if ((copystrings & (1 << i)) != 0)
|
if ((copystrings & (1U << i)) != 0)
|
||||||
{
|
{
|
||||||
int rc;
|
int rc;
|
||||||
char copybuffer[256];
|
char copybuffer[256];
|
||||||
@ -5400,7 +5400,7 @@ while (!done)
|
|||||||
|
|
||||||
for (i = 0; i < 32; i++)
|
for (i = 0; i < 32; i++)
|
||||||
{
|
{
|
||||||
if ((getstrings & (1 << i)) != 0)
|
if ((getstrings & (1U << i)) != 0)
|
||||||
{
|
{
|
||||||
int rc;
|
int rc;
|
||||||
const char *substring;
|
const char *substring;
|
||||||
|
2
pcre/testdata/testinput2
vendored
2
pcre/testdata/testinput2
vendored
@ -1380,7 +1380,7 @@
|
|||||||
1X
|
1X
|
||||||
123456\P
|
123456\P
|
||||||
|
|
||||||
//KF>testsavedregex
|
//S-KF>testsavedregex
|
||||||
|
|
||||||
/abc/IS>testsavedregex
|
/abc/IS>testsavedregex
|
||||||
<testsavedregex
|
<testsavedregex
|
||||||
|
3
pcre/testdata/testoutput2
vendored
3
pcre/testdata/testoutput2
vendored
@ -5614,9 +5614,8 @@ No match
|
|||||||
123456\P
|
123456\P
|
||||||
No match
|
No match
|
||||||
|
|
||||||
//KF>testsavedregex
|
//S-KF>testsavedregex
|
||||||
Compiled pattern written to testsavedregex
|
Compiled pattern written to testsavedregex
|
||||||
Study data written to testsavedregex
|
|
||||||
|
|
||||||
/abc/IS>testsavedregex
|
/abc/IS>testsavedregex
|
||||||
Capturing subpattern count = 0
|
Capturing subpattern count = 0
|
||||||
|
Loading…
x
Reference in New Issue
Block a user