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

Diff of /code/trunk/doc/pcrepattern.3

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 771 by ph10, Tue Nov 29 15:34:12 2011 UTC revision 788 by ph10, Tue Dec 6 15:38:01 2011 UTC
# Line 242  one of the following escape sequences th Line 242  one of the following escape sequences th
242    \eddd      character with octal code ddd, or back reference    \eddd      character with octal code ddd, or back reference
243    \exhh      character with hex code hh    \exhh      character with hex code hh
244    \ex{hhh..} character with hex code hhh.. (non-JavaScript mode)    \ex{hhh..} character with hex code hhh.. (non-JavaScript mode)
245    \euhhhh    character with hex code hhhh (JavaScript mode only)    \euhhhh    character with hex code hhhh (JavaScript mode only)
246  .sp  .sp
247  The precise effect of \ecx is as follows: if x is a lower case letter, it  The precise effect of \ecx is as follows: if x is a lower case letter, it
248  is converted to upper case. Then bit 6 of the character (hex 40) is inverted.  is converted to upper case. Then bit 6 of the character (hex 40) is inverted.
# Line 265  there is no terminating }, this form of Line 265  there is no terminating }, this form of
265  initial \ex will be interpreted as a basic hexadecimal escape, with no  initial \ex will be interpreted as a basic hexadecimal escape, with no
266  following digits, giving a character whose value is zero.  following digits, giving a character whose value is zero.
267  .P  .P
268  If the PCRE_JAVASCRIPT_COMPAT option is set, the interpretation of \ex is  If the PCRE_JAVASCRIPT_COMPAT option is set, the interpretation of \ex is
269  as just described only when it is followed by two hexadecimal digits.  as just described only when it is followed by two hexadecimal digits.
270  Otherwise, it matches a literal "x" character. In JavaScript mode, support for  Otherwise, it matches a literal "x" character. In JavaScript mode, support for
271  code points greater than 256 is provided by \eu, which must be followed by  code points greater than 256 is provided by \eu, which must be followed by
272  four hexadecimal digits; otherwise it matches a literal "u" character.  four hexadecimal digits; otherwise it matches a literal "u" character.
273  .P  .P
274  Characters whose value is less than 256 can be defined by either of the two  Characters whose value is less than 256 can be defined by either of the two
275  syntaxes for \ex (or by \eu in JavaScript mode). There is no difference in the  syntaxes for \ex (or by \eu in JavaScript mode). There is no difference in the
276  way they are handled. For example, \exdc is exactly the same as \ex{dc} (or  way they are handled. For example, \exdc is exactly the same as \ex{dc} (or
277  \eu00dc in JavaScript mode).  \eu00dc in JavaScript mode).
278  .P  .P
279  After \e0 up to two further octal digits are read. If there are fewer than two  After \e0 up to two further octal digits are read. If there are fewer than two
# Line 407  This is the same as Line 407  This is the same as
407  .\" </a>  .\" </a>
408  the "." metacharacter  the "." metacharacter
409  .\"  .\"
410  when PCRE_DOTALL is not set. Perl also uses \eN to match characters by name;  when PCRE_DOTALL is not set. Perl also uses \eN to match characters by name;
411  PCRE does not support this.  PCRE does not support this.
412  .P  .P
413  Each pair of lower and upper case escape sequences partitions the complete set  Each pair of lower and upper case escape sequences partitions the complete set
# Line 2593  the start-of-match optimizations by sett Line 2593  the start-of-match optimizations by sett
2593  when calling \fBpcre_compile()\fP or \fBpcre_exec()\fP, or by starting the  when calling \fBpcre_compile()\fP or \fBpcre_exec()\fP, or by starting the
2594  pattern with (*NO_START_OPT).  pattern with (*NO_START_OPT).
2595  .P  .P
2596  Experiments with Perl suggest that it too has similar optimizations, sometimes  Experiments with Perl suggest that it too has similar optimizations, sometimes
2597  leading to anomalous results.  leading to anomalous results.
2598  .  .
2599  .  .
# Line 2642  starting point (see (*SKIP) below). Line 2642  starting point (see (*SKIP) below).
2642  A name is always required with this verb. There may be as many instances of  A name is always required with this verb. There may be as many instances of
2643  (*MARK) as you like in a pattern, and their names do not have to be unique.  (*MARK) as you like in a pattern, and their names do not have to be unique.
2644  .P  .P
2645  When a match succeeds, the name of the last-encountered (*MARK) on the matching  When a match succeeds, the name of the last-encountered (*MARK) on the matching
2646  path is passed back to the caller via the \fIpcre_extra\fP data structure, as  path is passed back to the caller via the \fIpcre_extra\fP data structure, as
2647  described in the  described in the
2648  .\" HTML <a href="pcreapi.html#extradata">  .\" HTML <a href="pcreapi.html#extradata">
# Line 2681  After a partial match or a failed match, Line 2681  After a partial match or a failed match,
2681    No match, mark = B    No match, mark = B
2682  .sp  .sp
2683  Note that in this unanchored example the mark is retained from the match  Note that in this unanchored example the mark is retained from the match
2684  attempt that started at the letter "X". Subsequent match attempts starting at  attempt that started at the letter "X". Subsequent match attempts starting at
2685  "P" and then with an empty string do not get as far as the (*MARK) item, but  "P" and then with an empty string do not get as far as the (*MARK) item, but
2686  nevertheless do not reset it.  nevertheless do not reset it.
2687  .  .
2688  .  .
Legend:
Removed from v.771  
changed lines
  Added in v.788
  ViewVC Help
Powered by ViewVC 1.1.5