Clarify delimiter handling in pcre2test documentation.

This commit is contained in:
Philip Hazel 2021-08-28 12:46:50 +01:00
parent f4beac6c1a
commit 5ff1daffa0
4 changed files with 485 additions and 477 deletions

View File

@ -6,7 +6,8 @@ API. Since its initial release in 2015, there has been further development of
the code and it now differs from PCRE1 in more than just the API. There are new
features, and the internals have been improved. The original PCRE1 library is
now obsolete and should not be used in new projects. The latest release of
PCRE2 is available in .tar.gz or .zip form from its GitHub repository:
PCRE2 is available in .tar.gz, tar.bz2, or .zip form from this GitHub
repository:
https://github.com/PhilipHazel/pcre2/releases
@ -905,4 +906,4 @@ The distribution should contain the files listed below.
Philip Hazel
Email local part: Philip.Hazel
Email domain: gmail.com
Last updated: 25 August 2021
Last updated: 27 August 2021

View File

@ -486,15 +486,17 @@ excluding pattern meta-characters):
</pre>
This is interpreted as the pattern's delimiter. A regular expression may be
continued over several input lines, in which case the newline characters are
included within it. It is possible to include the delimiter within the pattern
by escaping it with a backslash, for example
included within it. It is possible to include the delimiter as a literal within
the pattern by escaping it with a backslash, for example
<pre>
/abc\/def/
</pre>
If you do this, the escape and the delimiter form part of the pattern, but
since the delimiters are all non-alphanumeric, this does not affect its
interpretation. If the terminating delimiter is immediately followed by a
backslash, for example,
since the delimiters are all non-alphanumeric, the inclusion of the backslash
does not affect the pattern's interpretation. Note, however, that this trick
does not work within \Q...\E literal bracketing because the backslash will
itself be interpreted as a literal. If the terminating delimiter is immediately
followed by a backslash, for example,
<pre>
/abc/\
</pre>
@ -2117,14 +2119,14 @@ on the stack.
<P>
Philip Hazel
<br>
University Computing Service
Retired from University Computing Service
<br>
Cambridge, England.
<br>
</P>
<br><a name="SEC21" href="#TOC1">REVISION</a><br>
<P>
Last updated: 28 April 2021
Last updated: 28 August 2021
<br>
Copyright &copy; 1997-2021 University of Cambridge.
<br>

View File

@ -1,4 +1,4 @@
.TH PCRE2TEST 1 "28 April 2021" "PCRE 10.37"
.TH PCRE2TEST 1 "28 August 2021" "PCRE 10.38"
.SH NAME
pcre2test - a program for testing Perl-compatible regular expressions.
.SH SYNOPSIS
@ -443,15 +443,17 @@ excluding pattern meta-characters):
.sp
This is interpreted as the pattern's delimiter. A regular expression may be
continued over several input lines, in which case the newline characters are
included within it. It is possible to include the delimiter within the pattern
by escaping it with a backslash, for example
included within it. It is possible to include the delimiter as a literal within
the pattern by escaping it with a backslash, for example
.sp
/abc\e/def/
.sp
If you do this, the escape and the delimiter form part of the pattern, but
since the delimiters are all non-alphanumeric, this does not affect its
interpretation. If the terminating delimiter is immediately followed by a
backslash, for example,
since the delimiters are all non-alphanumeric, the inclusion of the backslash
does not affect the pattern's interpretation. Note, however, that this trick
does not work within \eQ...\eE literal bracketing because the backslash will
itself be interpreted as a literal. If the terminating delimiter is immediately
followed by a backslash, for example,
.sp
/abc/\e
.sp
@ -2096,7 +2098,7 @@ on the stack.
.sp
.nf
Philip Hazel
University Computing Service
Retired from University Computing Service
Cambridge, England.
.fi
.
@ -2105,6 +2107,6 @@ Cambridge, England.
.rs
.sp
.nf
Last updated: 28 April 2021
Last updated: 28 August 2021
Copyright (c) 1997-2021 University of Cambridge.
.fi

View File

@ -425,14 +425,17 @@ PATTERN SYNTAX
This is interpreted as the pattern's delimiter. A regular expression
may be continued over several input lines, in which case the newline
characters are included within it. It is possible to include the delim-
iter within the pattern by escaping it with a backslash, for example
iter as a literal within the pattern by escaping it with a backslash,
for example
/abc\/def/
If you do this, the escape and the delimiter form part of the pattern,
but since the delimiters are all non-alphanumeric, this does not affect
its interpretation. If the terminating delimiter is immediately fol-
lowed by a backslash, for example,
but since the delimiters are all non-alphanumeric, the inclusion of the
backslash does not affect the pattern's interpretation. Note, however,
that this trick does not work within \Q...\E literal bracketing because
the backslash will itself be interpreted as a literal. If the terminat-
ing delimiter is immediately followed by a backslash, for example,
/abc/\
@ -1929,11 +1932,11 @@ SEE ALSO
AUTHOR
Philip Hazel
University Computing Service
Retired from University Computing Service
Cambridge, England.
REVISION
Last updated: 28 April 2021
Last updated: 28 August 2021
Copyright (c) 1997-2021 University of Cambridge.