/[pcre]/code/trunk/doc/pcretest.1
ViewVC logotype

Diff of /code/trunk/doc/pcretest.1

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

revision 553 by ph10, Fri Oct 22 15:57:50 2010 UTC revision 576 by ph10, Sun Nov 21 18:45:10 2010 UTC
# Line 179  options that do not correspond to anythi Line 179  options that do not correspond to anythi
179    \fB/U\fP              PCRE_UNGREEDY    \fB/U\fP              PCRE_UNGREEDY
180    \fB/W\fP              PCRE_UCP    \fB/W\fP              PCRE_UCP
181    \fB/X\fP              PCRE_EXTRA    \fB/X\fP              PCRE_EXTRA
182      \fB/Y\fP              PCRE_NO_START_OPTIMIZE
183    \fB/<JS>\fP           PCRE_JAVASCRIPT_COMPAT    \fB/<JS>\fP           PCRE_JAVASCRIPT_COMPAT
184    \fB/<cr>\fP           PCRE_NEWLINE_CR    \fB/<cr>\fP           PCRE_NEWLINE_CR
185    \fB/<lf>\fP           PCRE_NEWLINE_LF    \fB/<lf>\fP           PCRE_NEWLINE_LF
# Line 219  begins with a lookbehind assertion (incl Line 220  begins with a lookbehind assertion (incl
220  If any call to \fBpcre_exec()\fP in a \fB/g\fP or \fB/G\fP sequence matches an  If any call to \fBpcre_exec()\fP in a \fB/g\fP or \fB/G\fP sequence matches an
221  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
222  PCRE_ANCHORED flags set in order to search for another, non-empty, match at the  PCRE_ANCHORED flags set in order to search for another, non-empty, match at the
223  same point. If this second match fails, the start offset is advanced by one  same point. If this second match fails, the start offset is advanced, and the
224  character, and the normal match is retried. This imitates the way Perl handles  normal match is retried. This imitates the way Perl handles such cases when
225  such cases when using the \fB/g\fP modifier or the \fBsplit()\fP function.  using the \fB/g\fP modifier or the \fBsplit()\fP function. Normally, the start
226    offset is advanced by one character, but if the newline convention recognizes
227    CRLF as a newline, and the current character is CR followed by LF, an advance
228    of two is used.
229  .  .
230  .  .
231  .SS "Other modifiers"  .SS "Other modifiers"
# Line 341  recognized: Line 345  recognized:
345    \et         tab (\ex09)    \et         tab (\ex09)
346    \ev         vertical tab (\ex0b)    \ev         vertical tab (\ex0b)
347    \ennn       octal character (up to 3 octal digits)    \ennn       octal character (up to 3 octal digits)
348    \exhh       hexadecimal character (up to 2 hex digits)                 always a byte unless > 255 in UTF-8 mode
349      \exhh       hexadecimal byte (up to 2 hex digits)
350  .\" JOIN  .\" JOIN
351    \ex{hh...}  hexadecimal character, any number of digits    \ex{hh...}  hexadecimal character, any number of digits
352                 in UTF-8 mode                 in UTF-8 mode
# Line 411  recognized: Line 416  recognized:
416  .\" JOIN  .\" JOIN
417    \e?         pass the PCRE_NO_UTF8_CHECK option to    \e?         pass the PCRE_NO_UTF8_CHECK option to
418                 \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP                 \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP
   \e>dd       start the match at offset dd (any number of digits);  
419  .\" JOIN  .\" JOIN
420                 this sets the \fIstartoffset\fP argument for \fBpcre_exec()\fP    \e>dd       start the match at offset dd (optional "-"; then
421                 or \fBpcre_dfa_exec()\fP                 any number of digits); this sets the \fIstartoffset\fP
422                   argument for \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP
423  .\" JOIN  .\" JOIN
424    \e<cr>      pass the PCRE_NEWLINE_CR option to \fBpcre_exec()\fP    \e<cr>      pass the PCRE_NEWLINE_CR option to \fBpcre_exec()\fP
425                 or \fBpcre_dfa_exec()\fP                 or \fBpcre_dfa_exec()\fP
# Line 431  recognized: Line 436  recognized:
436    \e<any>     pass the PCRE_NEWLINE_ANY option to \fBpcre_exec()\fP    \e<any>     pass the PCRE_NEWLINE_ANY option to \fBpcre_exec()\fP
437                 or \fBpcre_dfa_exec()\fP                 or \fBpcre_dfa_exec()\fP
438  .sp  .sp
439    Note that \exhh always specifies one byte, even in UTF-8 mode; this makes it
440    possible to construct invalid UTF-8 sequences for testing purposes. On the
441    other hand, \ex{hh} is interpreted as a UTF-8 character in UTF-8 mode,
442    generating more than one byte if the value is greater than 127. When not in
443    UTF-8 mode, it generates one byte for values less than 256, and causes an error
444    for greater values.
445    .P
446  The escapes that specify line ending sequences are literal strings, exactly as  The escapes that specify line ending sequences are literal strings, exactly as
447  shown. No more than one newline setting should be present in any data line.  shown. No more than one newline setting should be present in any data line.
448  .P  .P
# Line 767  Cambridge CB2 3QH, England. Line 779  Cambridge CB2 3QH, England.
779  .rs  .rs
780  .sp  .sp
781  .nf  .nf
782  Last updated: 22 October 2010  Last updated: 21 November 2010
783  Copyright (c) 1997-2010 University of Cambridge.  Copyright (c) 1997-2010 University of Cambridge.
784  .fi  .fi

Legend:
Removed from v.553  
changed lines
  Added in v.576

  ViewVC Help
Powered by ViewVC 1.1.5