| 328 |
zero, because no more than three octal digits are ever read. |
zero, because no more than three octal digits are ever read. |
| 329 |
.P |
.P |
| 330 |
All the sequences that define a single character value can be used both inside |
All the sequences that define a single character value can be used both inside |
| 331 |
and outside character classes. In addition, inside a character class, the |
and outside character classes. In addition, inside a character class, \eb is |
| 332 |
sequence \eb is interpreted as the backspace character (hex 08). The sequences |
interpreted as the backspace character (hex 08). |
| 333 |
\eB, \eN, \eR, and \eX are not special inside a character class. Like any other |
.P |
| 334 |
unrecognized escape sequences, they are treated as the literal characters "B", |
\eN is not allowed in a character class. \eB, \eR, and \eX are not special |
| 335 |
"N", "R", and "X" by default, but cause an error if the PCRE_EXTRA option is |
inside a character class. Like other unrecognized escape sequences, they are |
| 336 |
set. Outside a character class, these sequences have different meanings. |
treated as the literal characters "B", "R", and "X" by default, but cause an |
| 337 |
|
error if the PCRE_EXTRA option is set. Outside a character class, these |
| 338 |
|
sequences have different meanings. |
| 339 |
. |
. |
| 340 |
. |
. |
| 341 |
.SS "Unsupported escape sequences" |
.SS "Unsupported escape sequences" |
| 1005 |
PCRE does not allow \eC to appear in lookbehind assertions |
PCRE does not allow \eC to appear in lookbehind assertions |
| 1006 |
.\" HTML <a href="#lookbehind"> |
.\" HTML <a href="#lookbehind"> |
| 1007 |
.\" </a> |
.\" </a> |
| 1008 |
(described below), |
(described below) |
| 1009 |
.\" |
.\" |
| 1010 |
because in UTF-8 mode this would make it impossible to calculate the length of |
in UTF-8 mode, because this would make it impossible to calculate the length of |
| 1011 |
the lookbehind. |
the lookbehind. |
| 1012 |
.P |
.P |
| 1013 |
In general, the \eC escape sequence is best avoided in UTF-8 mode. However, one |
In general, the \eC escape sequence is best avoided in UTF-8 mode. However, one |
| 1972 |
match. If there are insufficient characters before the current position, the |
match. If there are insufficient characters before the current position, the |
| 1973 |
assertion fails. |
assertion fails. |
| 1974 |
.P |
.P |
| 1975 |
PCRE does not allow the \eC escape (which matches a single byte in UTF-8 mode) |
In UTF-8 mode, PCRE does not allow the \eC escape (which matches a single byte, |
| 1976 |
to appear in lookbehind assertions, because it makes it impossible to calculate |
even in UTF-8 mode) to appear in lookbehind assertions, because it makes it |
| 1977 |
the length of the lookbehind. The \eX and \eR escapes, which can match |
impossible to calculate the length of the lookbehind. The \eX and \eR escapes, |
| 1978 |
different numbers of bytes, are also not permitted. |
which can match different numbers of bytes, are also not permitted. |
| 1979 |
.P |
.P |
| 1980 |
.\" HTML <a href="#subpatternsassubroutines"> |
.\" HTML <a href="#subpatternsassubroutines"> |
| 1981 |
.\" </a> |
.\" </a> |
| 2876 |
.rs |
.rs |
| 2877 |
.sp |
.sp |
| 2878 |
.nf |
.nf |
| 2879 |
Last updated: 14 November 2011 |
Last updated: 19 November 2011 |
| 2880 |
Copyright (c) 1997-2011 University of Cambridge. |
Copyright (c) 1997-2011 University of Cambridge. |
| 2881 |
.fi |
.fi |