/[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 578 by ph10, Sun Nov 21 18:45:10 2010 UTC revision 579 by ph10, Wed Nov 24 17:39:25 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    \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 222  empty string, the next call is done with Line 222  empty string, the next call is done with
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, and the  same point. If this second match fails, the start offset is advanced, and the
224  normal match is retried. This imitates the way Perl handles such cases when  normal match is retried. This imitates the way Perl handles such cases when
225  using the \fB/g\fP modifier or the \fBsplit()\fP function. Normally, the start  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  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  CRLF as a newline, and the current character is CR followed by LF, an advance
228  of two is used.  of two is used.
229  .  .
230  .  .
# Line 345  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                 always a byte unless > 255 in UTF-8 mode                 always a byte unless > 255 in UTF-8 mode
349    \exhh       hexadecimal byte (up to 2 hex digits)    \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
# Line 418  recognized: Line 418  recognized:
418                 \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP                 \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP
419  .\" JOIN  .\" JOIN
420    \e>dd       start the match at offset dd (optional "-"; then    \e>dd       start the match at offset dd (optional "-"; then
421                 any number of digits); this sets the \fIstartoffset\fP                 any number of digits); this sets the \fIstartoffset\fP
422                 argument for \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP                 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
# Line 436  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  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  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,  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  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  UTF-8 mode, it generates one byte for values less than 256, and causes an error
444  for greater values.  for greater values.
445  .P  .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

Legend:
Removed from v.578  
changed lines
  Added in v.579

  ViewVC Help
Powered by ViewVC 1.1.5