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

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

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

revision 597 by ph10, Tue Jan 11 16:49:55 2011 UTC revision 598 by ph10, Sat May 7 15:37:31 2011 UTC
# Line 14  for requesting some minor changes that g Line 14  for requesting some minor changes that g
14  The current implementation of PCRE corresponds approximately with Perl 5.12,  The current implementation of PCRE corresponds approximately with Perl 5.12,
15  including support for UTF-8 encoded strings and Unicode general category  including support for UTF-8 encoded strings and Unicode general category
16  properties. However, UTF-8 and Unicode support has to be explicitly enabled; it  properties. However, UTF-8 and Unicode support has to be explicitly enabled; it
17  is not the default. The Unicode tables correspond to Unicode release 5.2.0.  is not the default. The Unicode tables correspond to Unicode release 6.0.0.
18  .P  .P
19  In addition to the Perl-compatible matching function, PCRE contains an  In addition to the Perl-compatible matching function, PCRE contains an
20  alternative function that matches the same compiled patterns in a different  alternative function that matches the same compiled patterns in a different
# Line 208  available as independent code points in Line 208  available as independent code points in
208  the whole surrogate thing is a fudge for UTF-16 which unfortunately messes up  the whole surrogate thing is a fudge for UTF-16 which unfortunately messes up
209  UTF-8.)  UTF-8.)
210  .P  .P
211  If an invalid UTF-8 string is passed to PCRE, an error return  If an invalid UTF-8 string is passed to PCRE, an error return is given. At
212  (PCRE_ERROR_BADUTF8) is given. In some situations, you may already know that  compile time, the only additional information is the offset to the first byte
213  your strings are valid, and therefore want to skip these checks in order to  of the failing character. The runtime functions (\fBpcre_exec()\fP and
214  improve performance. If you set the PCRE_NO_UTF8_CHECK flag at compile time or  \fBpcre_dfa_exec()\fP), pass back this information as well as a more detailed
215  at run time, PCRE assumes that the pattern or subject it is given  reason code if the caller has provided memory in which to do this.
216  (respectively) contains only valid UTF-8 codes. In this case, it does not  .P
217  diagnose an invalid UTF-8 string.  In some situations, you may already know that your strings are valid, and
218    therefore want to skip these checks in order to improve performance. If you set
219    the PCRE_NO_UTF8_CHECK flag at compile time or at run time, PCRE assumes that
220    the pattern or subject it is given (respectively) contains only valid UTF-8
221    codes. In this case, it does not diagnose an invalid UTF-8 string.
222  .P  .P
223  If you pass an invalid UTF-8 string when PCRE_NO_UTF8_CHECK is set, what  If you pass an invalid UTF-8 string when PCRE_NO_UTF8_CHECK is set, what
224  happens depends on why the string is invalid. If the string conforms to the  happens depends on why the string is invalid. If the string conforms to the
# Line 304  two digits 10, at the domain cam.ac.uk. Line 308  two digits 10, at the domain cam.ac.uk.
308  .rs  .rs
309  .sp  .sp
310  .nf  .nf
311  Last updated: 13 November 2010  Last updated: 07 May 2011
312  Copyright (c) 1997-2010 University of Cambridge.  Copyright (c) 1997-2011 University of Cambridge.
313  .fi  .fi

Legend:
Removed from v.597  
changed lines
  Added in v.598

  ViewVC Help
Powered by ViewVC 1.1.5