/[pcre]/code/trunk/doc/pcre.txt

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

Parent Directory | Revision Log | View Patch Patch

-revision 371 by ph10,
Mon Aug 25 18:28:05 2008 UTC
+revision 392 by ph10,
Tue Mar 17 21:30:30 2009 UTC
 Line 94 
 USER DOCUMENTATION
           pcrestack         discussion of stack usage
           pcretest          description of the pcretest testing command
-        In  addition,  in the "man" and HTML formats, there is a short page for
+        In addition, in the "man" and HTML formats, there is a short  page  for
         each C library function, listing its arguments and results.
  LIMITATIONS
-        There are some size limitations in PCRE but it is hoped that they  will
+        There  are some size limitations in PCRE but it is hoped that they will
         never in practice be relevant.
-        The  maximum  length of a compiled pattern is 65539 (sic) bytes if PCRE
+        The maximum length of a compiled pattern is 65539 (sic) bytes  if  PCRE
         is compiled with the default internal linkage size of 2. If you want to
-        process  regular  expressions  that are truly enormous, you can compile
+        process regular expressions that are truly enormous,  you  can  compile
-        PCRE with an internal linkage size of 3 or 4 (see the  README  file  in
+        PCRE  with  an  internal linkage size of 3 or 4 (see the README file in
-        the  source  distribution and the pcrebuild documentation for details).
+        the source distribution and the pcrebuild documentation  for  details).
-        In these cases the limit is substantially larger.  However,  the  speed
+        In  these  cases the limit is substantially larger.  However, the speed
         of execution is slower.
         All values in repeating quantifiers must be less than 65536.
 Line 119 
 LIMITATIONS
         The maximum length of name for a named subpattern is 32 characters, and
         the maximum number of named subpatterns is 10000.
-        The  maximum  length of a subject string is the largest positive number
+        The maximum length of a subject string is the largest  positive  number
-        that an integer variable can hold. However, when using the  traditional
+        that  an integer variable can hold. However, when using the traditional
         matching function, PCRE uses recursion to handle subpatterns and indef-
-        inite repetition.  This means that the available stack space may  limit
+        inite  repetition.  This means that the available stack space may limit
         the size of a subject string that can be processed by certain patterns.
         For a discussion of stack issues, see the pcrestack documentation.
  UTF-8 AND UNICODE PROPERTY SUPPORT
-        From release 3.3, PCRE has  had  some  support  for  character  strings
+        From  release  3.3,  PCRE  has  had  some support for character strings
-        encoded  in the UTF-8 format. For release 4.0 this was greatly extended
+        encoded in the UTF-8 format. For release 4.0 this was greatly  extended
-        to cover most common requirements, and in release 5.0  additional  sup-
+        to  cover  most common requirements, and in release 5.0 additional sup-
         port for Unicode general category properties was added.
-        In  order  process  UTF-8 strings, you must build PCRE to include UTF-8
+        In order process UTF-8 strings, you must build PCRE  to  include  UTF-8
-        support in the code, and, in addition,  you  must  call  pcre_compile()
+        support  in  the  code,  and, in addition, you must call pcre_compile()
-        with  the PCRE_UTF8 option flag. When you do this, both the pattern and
+        with the PCRE_UTF8 option flag. When you do this, both the pattern  and
-        any subject strings that are matched against it are  treated  as  UTF-8
+        any  subject  strings  that are matched against it are treated as UTF-8
         strings instead of just strings of bytes.
-        If  you compile PCRE with UTF-8 support, but do not use it at run time,
+        If you compile PCRE with UTF-8 support, but do not use it at run  time,
-        the library will be a bit bigger, but the additional run time  overhead
+        the  library will be a bit bigger, but the additional run time overhead
         is limited to testing the PCRE_UTF8 flag occasionally, so should not be
         very big.
         If PCRE is built with Unicode character property support (which implies
-        UTF-8  support),  the  escape sequences \p{..}, \P{..}, and \X are sup-
+        UTF-8 support), the escape sequences \p{..}, \P{..}, and  \X  are  sup-
         ported.  The available properties that can be tested are limited to the
-        general  category  properties such as Lu for an upper case letter or Nd
+        general category properties such as Lu for an upper case letter  or  Nd
-        for a decimal number, the Unicode script names such as Arabic  or  Han,
+        for  a  decimal number, the Unicode script names such as Arabic or Han,
-        and  the  derived  properties  Any  and L&. A full list is given in the
+        and the derived properties Any and L&. A full  list  is  given  in  the
         pcrepattern documentation. Only the short names for properties are sup-
-        ported.  For example, \p{L} matches a letter. Its Perl synonym, \p{Let-
+        ported. For example, \p{L} matches a letter. Its Perl synonym,  \p{Let-
-        ter}, is not supported.  Furthermore,  in  Perl,  many  properties  may
+        ter},  is  not  supported.   Furthermore,  in Perl, many properties may
-        optionally  be  prefixed by "Is", for compatibility with Perl 5.6. PCRE
+        optionally be prefixed by "Is", for compatibility with Perl  5.6.  PCRE
         does not support this.
     Validity of UTF-8 strings
-        When you set the PCRE_UTF8 flag, the strings  passed  as  patterns  and
+        When  you  set  the  PCRE_UTF8 flag, the strings passed as patterns and
         subjects are (by default) checked for validity on entry to the relevant
-        functions. From release 7.3 of PCRE, the check is according  the  rules
+        functions.  From  release 7.3 of PCRE, the check is according the rules
-        of  RFC  3629, which are themselves derived from the Unicode specifica-
+        of RFC 3629, which are themselves derived from the  Unicode  specifica-
-        tion. Earlier releases of PCRE followed the rules of  RFC  2279,  which
+        tion.  Earlier  releases  of PCRE followed the rules of RFC 2279, which
-        allows  the  full range of 31-bit values (0 to 0x7FFFFFFF). The current
+        allows the full range of 31-bit values (0 to 0x7FFFFFFF).  The  current
         check allows only values in the range U+0 to U+10FFFF, excluding U+D800
         to U+DFFF.
-        The  excluded  code  points are the "Low Surrogate Area" of Unicode, of
+        The excluded code points are the "Low Surrogate Area"  of  Unicode,  of
-        which the Unicode Standard says this: "The Low Surrogate Area does  not
+        which  the Unicode Standard says this: "The Low Surrogate Area does not
-        contain  any  character  assignments,  consequently  no  character code
+        contain any  character  assignments,  consequently  no  character  code
         charts or namelists are provided for this area. Surrogates are reserved
-        for  use  with  UTF-16 and then must be used in pairs." The code points
+        for use with UTF-16 and then must be used in pairs."  The  code  points
-        that are encoded by UTF-16 pairs  are  available  as  independent  code
+        that  are  encoded  by  UTF-16  pairs are available as independent code
-        points  in  the  UTF-8  encoding.  (In other words, the whole surrogate
+        points in the UTF-8 encoding. (In  other  words,  the  whole  surrogate
         thing is a fudge for UTF-16 which unfortunately messes up UTF-8.)
-        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
         (PCRE_ERROR_BADUTF8) is given. In some situations, you may already know
         that your strings are valid, and therefore want to skip these checks in
         order to improve performance. If you set the PCRE_NO_UTF8_CHECK flag at
-        compile time or at run time, PCRE assumes that the pattern  or  subject
+        compile  time  or at run time, PCRE assumes that the pattern or subject
-        it  is  given  (respectively)  contains only valid UTF-8 codes. In this
+        it is given (respectively) contains only valid  UTF-8  codes.  In  this
         case, it does not diagnose an invalid UTF-8 string.
-        If you pass an invalid UTF-8 string  when  PCRE_NO_UTF8_CHECK  is  set,
+        If  you  pass  an  invalid UTF-8 string when PCRE_NO_UTF8_CHECK is set,
-        what  happens  depends on why the string is invalid. If the string con-
+        what happens depends on why the string is invalid. If the  string  con-
         forms to the "old" definition of UTF-8 (RFC 2279), it is processed as a
-        string  of  characters  in  the  range 0 to 0x7FFFFFFF. In other words,
+        string of characters in the range 0  to  0x7FFFFFFF.  In  other  words,
         apart from the initial validity test, PCRE (when in UTF-8 mode) handles
-        strings  according  to  the more liberal rules of RFC 2279. However, if
+        strings according to the more liberal rules of RFC  2279.  However,  if
-        the string does not even conform to RFC 2279, the result is  undefined.
+        the  string does not even conform to RFC 2279, the result is undefined.
         Your program may crash.
-        If  you  want  to  process  strings  of  values  in the full range 0 to
+        If you want to process strings  of  values  in  the  full  range  0  to
-x7FFFFFFF, encoded in a UTF-8-like manner as per the old RFC, you  can
+x7FFFFFFF,  encoded in a UTF-8-like manner as per the old RFC, you can
         set PCRE_NO_UTF8_CHECK to bypass the more restrictive test. However, in
         this situation, you will have to apply your own validity check.
     General comments about UTF-8 mode
-. An unbraced hexadecimal escape sequence (such  as  \xb3)  matches  a
+.  An  unbraced  hexadecimal  escape sequence (such as \xb3) matches a
         two-byte UTF-8 character if the value is greater than 127.
-.  Octal  numbers  up to \777 are recognized, and match two-byte UTF-8
+. Octal numbers up to \777 are recognized, and  match  two-byte  UTF-8
         characters for values greater than \177.
-. Repeat quantifiers apply to complete UTF-8 characters, not to  indi-
+.  Repeat quantifiers apply to complete UTF-8 characters, not to indi-
         vidual bytes, for example: \x{100}{3}.
-.  The dot metacharacter matches one UTF-8 character instead of a sin-
+. The dot metacharacter matches one UTF-8 character instead of a  sin-
         gle byte.
-. The escape sequence \C can be used to match a single byte  in  UTF-8
+.  The  escape sequence \C can be used to match a single byte in UTF-8
-        mode,  but  its  use can lead to some strange effects. This facility is
+        mode, but its use can lead to some strange effects.  This  facility  is
         not available in the alternative matching function, pcre_dfa_exec().
-. The character escapes \b, \B, \d, \D, \s, \S, \w, and  \W  correctly
+.  The  character escapes \b, \B, \d, \D, \s, \S, \w, and \W correctly
-        test  characters of any code value, but the characters that PCRE recog-
+        test characters of any code value, but the characters that PCRE  recog-
-        nizes as digits, spaces, or word characters  remain  the  same  set  as
+        nizes  as  digits,  spaces,  or  word characters remain the same set as
         before, all with values less than 256. This remains true even when PCRE
-        includes Unicode property support, because to do otherwise  would  slow
+        includes  Unicode  property support, because to do otherwise would slow
-        down  PCRE in many common cases. If you really want to test for a wider
+        down PCRE in many common cases. If you really want to test for a  wider
-        sense of, say, "digit", you must use Unicode  property  tests  such  as
+        sense  of,  say,  "digit",  you must use Unicode property tests such as
         \p{Nd}.
-.  Similarly,  characters that match the POSIX named character classes
+. Similarly, characters that match the POSIX named  character  classes
         are all low-valued characters.
-. However, the Perl 5.10 horizontal and vertical  whitespace  matching
+.  However,  the Perl 5.10 horizontal and vertical whitespace matching
         escapes (\h, \H, \v, and \V) do match all the appropriate Unicode char-
         acters.
-. Case-insensitive matching applies only to  characters  whose  values
+.  Case-insensitive  matching  applies only to characters whose values
-        are  less than 128, unless PCRE is built with Unicode property support.
+        are less than 128, unless PCRE is built with Unicode property  support.
-        Even when Unicode property support is available, PCRE  still  uses  its
+        Even  when  Unicode  property support is available, PCRE still uses its
-        own  character  tables when checking the case of low-valued characters,
+        own character tables when checking the case of  low-valued  characters,
-        so as not to degrade performance.  The Unicode property information  is
+        so  as not to degrade performance.  The Unicode property information is
         used only for characters with higher values. Even when Unicode property
         support is available, PCRE supports case-insensitive matching only when
-        there  is  a  one-to-one  mapping between a letter's cases. There are a
+        there is a one-to-one mapping between a letter's  cases.  There  are  a
-        small number of many-to-one mappings in Unicode;  these  are  not  sup-
+        small  number  of  many-to-one  mappings in Unicode; these are not sup-
         ported by PCRE.
 Line 251 
 AUTHOR
         University Computing Service
         Cambridge CB2 3QH, England.
-        Putting  an actual email address here seems to have been a spam magnet,
+        Putting an actual email address here seems to have been a spam  magnet,
-        so I've taken it away. If you want to email me, use  my  two  initials,
+        so  I've  taken  it away. If you want to email me, use my two initials,
         followed by the two digits 10, at the domain cam.ac.uk.
 Line 307 
 C++ SUPPORT
  UTF-8 SUPPORT
-        To build PCRE with support for UTF-8 character strings, add
+        To build PCRE with support for UTF-8 Unicode character strings, add
           --enable-utf8
 Line 316 
 UTF-8 SUPPORT
         have have to set the PCRE_UTF8 option when you call the  pcre_compile()
         function.
+        If  you set --enable-utf8 when compiling in an EBCDIC environment, PCRE
+        expects its input to be either ASCII or UTF-8 (depending on the runtime
+        option).  It  is not possible to support both EBCDIC and UTF-8 codes in
+        the same  version  of  the  library.  Consequently,  --enable-utf8  and
+        --enable-ebcdic are mutually exclusive.
  UNICODE CHARACTER PROPERTY SUPPORT
-Line 337 
 UNICODE CHARACTER PROPERTY SUPPORT
+Line 343 
 UNICODE CHARACTER PROPERTY SUPPORT
  CODE VALUE OF NEWLINE
-        By default, PCRE interprets character 10 (linefeed, LF)  as  indicating
+        By default, PCRE interprets the linefeed (LF) character  as  indicating
         the  end  of  a line. This is the normal newline character on Unix-like
-        systems. You can compile PCRE to use character 13 (carriage return, CR)
+        systems. You can compile PCRE to use carriage return (CR)  instead,  by
-        instead, by adding
+        adding
           --enable-newline-is-cr
-Line 363 
 CODE VALUE OF NEWLINE
+Line 369 
 CODE VALUE OF NEWLINE
         causes PCRE to recognize any Unicode newline sequence.
-        Whatever  line  ending convention is selected when PCRE is built can be
+        Whatever line ending convention is selected when PCRE is built  can  be
-        overridden when the library functions are called. At build time  it  is
+        overridden  when  the library functions are called. At build time it is
         conventional to use the standard for your operating system.
  WHAT \R MATCHES
-        By  default,  the  sequence \R in a pattern matches any Unicode newline
+        By default, the sequence \R in a pattern matches  any  Unicode  newline
-        sequence, whatever has been selected as the line  ending  sequence.  If
+        sequence,  whatever  has  been selected as the line ending sequence. If
         you specify
           --enable-bsr-anycrlf
-        the  default  is changed so that \R matches only CR, LF, or CRLF. What-
+        the default is changed so that \R matches only CR, LF, or  CRLF.  What-
-        ever is selected when PCRE is built can be overridden when the  library
+        ever  is selected when PCRE is built can be overridden when the library
         functions are called.
  BUILDING SHARED AND STATIC LIBRARIES
-        The  PCRE building process uses libtool to build both shared and static
+        The PCRE building process uses libtool to build both shared and  static
-        Unix libraries by default. You can suppress one of these by adding  one
+        Unix  libraries by default. You can suppress one of these by adding one
         of
           --disable-shared
-Line 396 
 BUILDING SHARED AND STATIC LIBRARIES
+Line 402 
 BUILDING SHARED AND STATIC LIBRARIES
  POSIX MALLOC USAGE
         When PCRE is called through the POSIX interface (see the pcreposix doc-
-        umentation), additional working storage is  required  for  holding  the
+        umentation),  additional  working  storage  is required for holding the
-        pointers  to capturing substrings, because PCRE requires three integers
+        pointers to capturing substrings, because PCRE requires three  integers
-        per substring, whereas the POSIX interface provides only  two.  If  the
+        per  substring,  whereas  the POSIX interface provides only two. If the
         number of expected substrings is small, the wrapper function uses space
         on the stack, because this is faster than using malloc() for each call.
         The default threshold above which the stack is no longer used is 10; it
-Line 411 
 POSIX MALLOC USAGE
+Line 417 
 POSIX MALLOC USAGE
  HANDLING VERY LARGE PATTERNS
-        Within a compiled pattern, offset values are used  to  point  from  one
+        Within  a  compiled  pattern,  offset values are used to point from one
-        part  to another (for example, from an opening parenthesis to an alter-
+        part to another (for example, from an opening parenthesis to an  alter-
-        nation metacharacter). By default, two-byte values are used  for  these
+        nation  metacharacter).  By default, two-byte values are used for these
-        offsets,  leading  to  a  maximum size for a compiled pattern of around
+        offsets, leading to a maximum size for a  compiled  pattern  of  around
-K. This is sufficient to handle all but the most  gigantic  patterns.
+K.  This  is sufficient to handle all but the most gigantic patterns.
-        Nevertheless,  some  people do want to process enormous patterns, so it
+        Nevertheless, some people do want to process enormous patterns,  so  it
-        is possible to compile PCRE to use three-byte or four-byte  offsets  by
+        is  possible  to compile PCRE to use three-byte or four-byte offsets by
         adding a setting such as
           --with-link-size=3
-        to  the  configure  command.  The value given must be 2, 3, or 4. Using
+        to the configure command. The value given must be 2,  3,  or  4.  Using
-        longer offsets slows down the operation of PCRE because it has to  load
+        longer  offsets slows down the operation of PCRE because it has to load
         additional bytes when handling them.
  AVOIDING EXCESSIVE STACK USAGE
         When matching with the pcre_exec() function, PCRE implements backtrack-
-        ing by making recursive calls to an internal function  called  match().
+        ing  by  making recursive calls to an internal function called match().
-        In  environments  where  the size of the stack is limited, this can se-
+        In environments where the size of the stack is limited,  this  can  se-
-        verely limit PCRE's operation. (The Unix environment does  not  usually
+        verely  limit  PCRE's operation. (The Unix environment does not usually
         suffer from this problem, but it may sometimes be necessary to increase
-        the maximum stack size.  There is a discussion in the  pcrestack  docu-
+        the  maximum  stack size.  There is a discussion in the pcrestack docu-
-        mentation.)  An alternative approach to recursion that uses memory from
+        mentation.) An alternative approach to recursion that uses memory  from
-        the heap to remember data, instead of using recursive  function  calls,
+        the  heap  to remember data, instead of using recursive function calls,
-        has  been  implemented to work round the problem of limited stack size.
+        has been implemented to work round the problem of limited  stack  size.
         If you want to build a version of PCRE that works this way, add
           --disable-stack-for-recursion
-        to the configure command. With this configuration, PCRE  will  use  the
+        to  the  configure  command. With this configuration, PCRE will use the
-        pcre_stack_malloc  and pcre_stack_free variables to call memory manage-
+        pcre_stack_malloc and pcre_stack_free variables to call memory  manage-
-        ment functions. By default these point to malloc() and free(), but  you
+        ment  functions. By default these point to malloc() and free(), but you
         can replace the pointers so that your own functions are used.
-        Separate  functions  are  provided  rather  than  using pcre_malloc and
+        Separate functions are  provided  rather  than  using  pcre_malloc  and
-        pcre_free because the  usage  is  very  predictable:  the  block  sizes
+        pcre_free  because  the  usage  is  very  predictable:  the block sizes
-        requested  are  always  the  same,  and  the blocks are always freed in
+        requested are always the same, and  the  blocks  are  always  freed  in
-        reverse order. A calling program might be able to  implement  optimized
+        reverse  order.  A calling program might be able to implement optimized
-        functions  that  perform  better  than  malloc()  and free(). PCRE runs
+        functions that perform better  than  malloc()  and  free().  PCRE  runs
         noticeably more slowly when built in this way. This option affects only
-        the   pcre_exec()   function;   it   is   not   relevant  for  the  the
+        the  pcre_exec()  function;  it   is   not   relevant   for   the   the
         pcre_dfa_exec() function.
  LIMITING PCRE RESOURCE USAGE
-        Internally, PCRE has a function called match(), which it calls  repeat-
+        Internally,  PCRE has a function called match(), which it calls repeat-
-        edly   (sometimes   recursively)  when  matching  a  pattern  with  the
+        edly  (sometimes  recursively)  when  matching  a  pattern   with   the
-        pcre_exec() function. By controlling the maximum number of  times  this
+        pcre_exec()  function.  By controlling the maximum number of times this
-        function  may be called during a single matching operation, a limit can
+        function may be called during a single matching operation, a limit  can
-        be placed on the resources used by a single call  to  pcre_exec().  The
+        be  placed  on  the resources used by a single call to pcre_exec(). The
-        limit  can be changed at run time, as described in the pcreapi documen-
+        limit can be changed at run time, as described in the pcreapi  documen-
-        tation. The default is 10 million, but this can be changed by adding  a
+        tation.  The default is 10 million, but this can be changed by adding a
         setting such as
           --with-match-limit=500000
-        to   the   configure  command.  This  setting  has  no  effect  on  the
+        to  the  configure  command.  This  setting  has  no  effect   on   the
         pcre_dfa_exec() matching function.
-        In some environments it is desirable to limit the  depth  of  recursive
+        In  some  environments  it is desirable to limit the depth of recursive
         calls of match() more strictly than the total number of calls, in order
-        to restrict the maximum amount of stack (or heap,  if  --disable-stack-
+        to  restrict  the maximum amount of stack (or heap, if --disable-stack-
         for-recursion is specified) that is used. A second limit controls this;
-        it defaults to the value that  is  set  for  --with-match-limit,  which
+        it  defaults  to  the  value  that is set for --with-match-limit, which
-        imposes  no  additional constraints. However, you can set a lower limit
+        imposes no additional constraints. However, you can set a  lower  limit
         by adding, for example,
           --with-match-limit-recursion=10000
-        to the configure command. This value can  also  be  overridden  at  run
+        to  the  configure  command.  This  value can also be overridden at run
         time.
  CREATING CHARACTER TABLES AT BUILD TIME
-        PCRE  uses fixed tables for processing characters whose code values are
+        PCRE uses fixed tables for processing characters whose code values  are
-        less than 256. By default, PCRE is built with a set of tables that  are
+        less  than 256. By default, PCRE is built with a set of tables that are
-        distributed  in  the  file pcre_chartables.c.dist. These tables are for
+        distributed in the file pcre_chartables.c.dist. These  tables  are  for
         ASCII codes only. If you add
           --enable-rebuild-chartables
-        to the configure command, the distributed tables are  no  longer  used.
+        to  the  configure  command, the distributed tables are no longer used.
-        Instead,  a  program  called dftables is compiled and run. This outputs
+        Instead, a program called dftables is compiled and  run.  This  outputs
         the source for new set of tables, created in the default locale of your
         C runtime system. (This method of replacing the tables does not work if
-        you are cross compiling, because dftables is run on the local host.  If
+        you  are cross compiling, because dftables is run on the local host. If
-        you  need  to  create alternative tables when cross compiling, you will
+        you need to create alternative tables when cross  compiling,  you  will
         have to do so "by hand".)
  USING EBCDIC CODE
-        PCRE assumes by default that it will run in an  environment  where  the
+        PCRE  assumes  by  default that it will run in an environment where the
-        character  code  is  ASCII  (or Unicode, which is a superset of ASCII).
+        character code is ASCII (or Unicode, which is  a  superset  of  ASCII).
-        This is the case for most computer operating systems.  PCRE  can,  how-
+        This  is  the  case for most computer operating systems. PCRE can, how-
         ever, be compiled to run in an EBCDIC environment by adding
           --enable-ebcdic
         to the configure command. This setting implies --enable-rebuild-charta-
-        bles. You should only use it if you know that  you  are  in  an  EBCDIC
+        bles.  You  should  only  use  it if you know that you are in an EBCDIC
-        environment (for example, an IBM mainframe operating system).
+        environment (for example,  an  IBM  mainframe  operating  system).  The
+        --enable-ebcdic option is incompatible with --enable-utf8.
  PCREGREP OPTIONS FOR COMPRESSED FILE SUPPORT
-Line 578 
 AUTHOR
+Line 585 
 AUTHOR
  REVISION
-        Last updated: 13 April 2008
+        Last updated: 17 March 2009
-        Copyright (c) 1997-2008 University of Cambridge.
+        Copyright (c) 1997-2009 University of Cambridge.
  ------------------------------------------------------------------------------
-Line 999 
 MULTITHREADING
+Line 1006 
 MULTITHREADING
         pcre_malloc, pcre_free, pcre_stack_malloc, and pcre_stack_free, and the
         callout function pointed to by pcre_callout, are shared by all threads.
-        The compiled form of a regular expression is not altered during  match-
+        The  compiled form of a regular expression is not altered during match-
         ing, so the same compiled pattern can safely be used by several threads
         at once.
-Line 1007 
 MULTITHREADING
+Line 1014 
 MULTITHREADING
  SAVING PRECOMPILED PATTERNS FOR LATER USE
         The compiled form of a regular expression can be saved and re-used at a
-        later  time,  possibly by a different program, and even on a host other
+        later time, possibly by a different program, and even on a  host  other
-        than the one on which  it  was  compiled.  Details  are  given  in  the
+        than  the  one  on  which  it  was  compiled.  Details are given in the
-        pcreprecompile  documentation.  However, compiling a regular expression
+        pcreprecompile documentation. However, compiling a  regular  expression
-        with one version of PCRE for use with a different version is not  guar-
+        with  one version of PCRE for use with a different version is not guar-
         anteed to work and may cause crashes.
-Line 1018 
 CHECKING BUILD-TIME OPTIONS
+Line 1025 
 CHECKING BUILD-TIME OPTIONS
         int pcre_config(int what, void *where);
-        The  function pcre_config() makes it possible for a PCRE client to dis-
+        The function pcre_config() makes it possible for a PCRE client to  dis-
         cover which optional features have been compiled into the PCRE library.
-        The  pcrebuild documentation has more details about these optional fea-
+        The pcrebuild documentation has more details about these optional  fea-
         tures.
-        The first argument for pcre_config() is an  integer,  specifying  which
+        The  first  argument  for pcre_config() is an integer, specifying which
         information is required; the second argument is a pointer to a variable
-        into which the information is  placed.  The  following  information  is
+        into  which  the  information  is  placed. The following information is
         available:
           PCRE_CONFIG_UTF8
-        The  output is an integer that is set to one if UTF-8 support is avail-
+        The output is an integer that is set to one if UTF-8 support is  avail-
         able; otherwise it is set to zero.
           PCRE_CONFIG_UNICODE_PROPERTIES
-        The output is an integer that is set to  one  if  support  for  Unicode
+        The  output  is  an  integer  that is set to one if support for Unicode
         character properties is available; otherwise it is set to zero.
           PCRE_CONFIG_NEWLINE
-        The  output  is  an integer whose value specifies the default character
+        The output is an integer whose value specifies  the  default  character
-        sequence that is recognized as meaning "newline". The four values  that
+        sequence  that is recognized as meaning "newline". The four values that
         are supported are: 10 for LF, 13 for CR, 3338 for CRLF, -2 for ANYCRLF,
-        and -1 for ANY. The default should normally be  the  standard  sequence
+        and  -1  for  ANY.  Though they are derived from ASCII, the same values
-        for your operating system.
+        are returned in EBCDIC environments. The default should normally corre-
+        spond to the standard sequence for your operating system.
           PCRE_CONFIG_BSR
-Line 1071 
 CHECKING BUILD-TIME OPTIONS
+Line 1079 
 CHECKING BUILD-TIME OPTIONS
           PCRE_CONFIG_MATCH_LIMIT
-        The output is an integer that gives the default limit for the number of
+        The output is a long integer that gives the default limit for the  num-
-        internal  matching  function  calls in a pcre_exec() execution. Further
+        ber  of  internal  matching  function calls in a pcre_exec() execution.
-        details are given with pcre_exec() below.
+        Further details are given with pcre_exec() below.
           PCRE_CONFIG_MATCH_LIMIT_RECURSION
-        The output is an integer that gives the default limit for the depth  of
+        The output is a long integer that gives the default limit for the depth
-        recursion  when calling the internal matching function in a pcre_exec()
+        of   recursion  when  calling  the  internal  matching  function  in  a
-        execution. Further details are given with pcre_exec() below.
+        pcre_exec() execution.  Further  details  are  given  with  pcre_exec()
+        below.
           PCRE_CONFIG_STACKRECURSE
-        The output is an integer that is set to one if internal recursion  when
+        The  output is an integer that is set to one if internal recursion when
         running pcre_exec() is implemented by recursive function calls that use
-        the stack to remember their state. This is the usual way that  PCRE  is
+        the  stack  to remember their state. This is the usual way that PCRE is
         compiled. The output is zero if PCRE was compiled to use blocks of data
-        on the  heap  instead  of  recursive  function  calls.  In  this  case,
+        on  the  heap  instead  of  recursive  function  calls.  In  this case,
-        pcre_stack_malloc  and  pcre_stack_free  are  called  to  manage memory
+        pcre_stack_malloc and  pcre_stack_free  are  called  to  manage  memory
         blocks on the heap, thus avoiding the use of the stack.
-Line 1105 
 COMPILING A PATTERN
+Line 1114 
 COMPILING A PATTERN
         Either of the functions pcre_compile() or pcre_compile2() can be called
         to compile a pattern into an internal form. The only difference between
-        the two interfaces is that pcre_compile2() has an additional  argument,
+        the  two interfaces is that pcre_compile2() has an additional argument,
         errorcodeptr, via which a numerical error code can be returned.
         The pattern is a C string terminated by a binary zero, and is passed in
-        the pattern argument. A pointer to a single block  of  memory  that  is
+        the  pattern  argument.  A  pointer to a single block of memory that is
-        obtained  via  pcre_malloc is returned. This contains the compiled code
+        obtained via pcre_malloc is returned. This contains the  compiled  code
         and related data. The pcre type is defined for the returned block; this
         is a typedef for a structure whose contents are not externally defined.
         It is up to the caller to free the memory (via pcre_free) when it is no
         longer required.
-        Although  the compiled code of a PCRE regex is relocatable, that is, it
+        Although the compiled code of a PCRE regex is relocatable, that is,  it
         does not depend on memory location, the complete pcre data block is not
-        fully  relocatable, because it may contain a copy of the tableptr argu-
+        fully relocatable, because it may contain a copy of the tableptr  argu-
         ment, which is an address (see below).
         The options argument contains various bit settings that affect the com-
-        pilation.  It  should be zero if no options are required. The available
+        pilation. It should be zero if no options are required.  The  available
-        options are described below. Some of them, in  particular,  those  that
+        options  are  described  below. Some of them, in particular, those that
-        are  compatible  with  Perl,  can also be set and unset from within the
+        are compatible with Perl, can also be set and  unset  from  within  the
-        pattern (see the detailed description  in  the  pcrepattern  documenta-
+        pattern  (see  the  detailed  description in the pcrepattern documenta-
-        tion).  For  these options, the contents of the options argument speci-
+        tion). For these options, the contents of the options  argument  speci-
-        fies their initial settings at the start of compilation and  execution.
+        fies  their initial settings at the start of compilation and execution.
-        The  PCRE_ANCHORED  and PCRE_NEWLINE_xxx options can be set at the time
+        The PCRE_ANCHORED and PCRE_NEWLINE_xxx options can be set at  the  time
         of matching as well as at compile time.
         If errptr is NULL, pcre_compile() returns NULL immediately.  Otherwise,
-        if  compilation  of  a  pattern fails, pcre_compile() returns NULL, and
+        if compilation of a pattern fails,  pcre_compile()  returns  NULL,  and
         sets the variable pointed to by errptr to point to a textual error mes-
         sage. This is a static string that is part of the library. You must not
         try to free it. The offset from the start of the pattern to the charac-
         ter where the error was discovered is placed in the variable pointed to
-        by erroffset, which must not be NULL. If it is, an immediate  error  is
+        by  erroffset,  which must not be NULL. If it is, an immediate error is
         given.
-        If  pcre_compile2()  is  used instead of pcre_compile(), and the error-
+        If pcre_compile2() is used instead of pcre_compile(),  and  the  error-
-        codeptr argument is not NULL, a non-zero error code number is  returned
+        codeptr  argument is not NULL, a non-zero error code number is returned
-        via  this argument in the event of an error. This is in addition to the
+        via this argument in the event of an error. This is in addition to  the
         textual error message. Error codes and messages are listed below.
-        If the final argument, tableptr, is NULL, PCRE uses a  default  set  of
+        If  the  final  argument, tableptr, is NULL, PCRE uses a default set of
-        character  tables  that  are  built  when  PCRE  is compiled, using the
+        character tables that are  built  when  PCRE  is  compiled,  using  the
-        default C locale. Otherwise, tableptr must be an address  that  is  the
+        default  C  locale.  Otherwise, tableptr must be an address that is the
-        result  of  a  call to pcre_maketables(). This value is stored with the
+        result of a call to pcre_maketables(). This value is  stored  with  the
-        compiled pattern, and used again by pcre_exec(), unless  another  table
+        compiled  pattern,  and used again by pcre_exec(), unless another table
         pointer is passed to it. For more discussion, see the section on locale
         support below.
-        This code fragment shows a typical straightforward  call  to  pcre_com-
+        This  code  fragment  shows a typical straightforward call to pcre_com-
         pile():
           pcre *re;
-Line 1166 
 COMPILING A PATTERN
+Line 1175 
 COMPILING A PATTERN
             &erroffset,       /* for error offset */
             NULL);            /* use default character tables */
-        The  following  names  for option bits are defined in the pcre.h header
+        The following names for option bits are defined in  the  pcre.h  header
         file:
           PCRE_ANCHORED
         If this bit is set, the pattern is forced to be "anchored", that is, it
-        is  constrained to match only at the first matching point in the string
+        is constrained to match only at the first matching point in the  string
-        that is being searched (the "subject string"). This effect can also  be
+        that  is being searched (the "subject string"). This effect can also be
-        achieved  by appropriate constructs in the pattern itself, which is the
+        achieved by appropriate constructs in the pattern itself, which is  the
         only way to do it in Perl.
           PCRE_AUTO_CALLOUT
         If this bit is set, pcre_compile() automatically inserts callout items,
-        all  with  number  255, before each pattern item. For discussion of the
+        all with number 255, before each pattern item. For  discussion  of  the
         callout facility, see the pcrecallout documentation.
           PCRE_BSR_ANYCRLF
           PCRE_BSR_UNICODE
         These options (which are mutually exclusive) control what the \R escape
-        sequence  matches.  The choice is either to match only CR, LF, or CRLF,
+        sequence matches. The choice is either to match only CR, LF,  or  CRLF,
         or to match any Unicode newline sequence. The default is specified when
         PCRE is built. It can be overridden from within the pattern, or by set-
         ting an option when a compiled pattern is matched.
           PCRE_CASELESS
-        If this bit is set, letters in the pattern match both upper  and  lower
+        If  this  bit is set, letters in the pattern match both upper and lower
-        case  letters.  It  is  equivalent  to  Perl's /i option, and it can be
+        case letters. It is equivalent to Perl's  /i  option,  and  it  can  be
-        changed within a pattern by a (?i) option setting. In UTF-8 mode,  PCRE
+        changed  within a pattern by a (?i) option setting. In UTF-8 mode, PCRE
-        always  understands the concept of case for characters whose values are
+        always understands the concept of case for characters whose values  are
-        less than 128, so caseless matching is always possible. For  characters
+        less  than 128, so caseless matching is always possible. For characters
-        with  higher  values,  the concept of case is supported if PCRE is com-
+        with higher values, the concept of case is supported if  PCRE  is  com-
-        piled with Unicode property support, but not otherwise. If you want  to
+        piled  with Unicode property support, but not otherwise. If you want to
-        use  caseless  matching  for  characters 128 and above, you must ensure
+        use caseless matching for characters 128 and  above,  you  must  ensure
-        that PCRE is compiled with Unicode property support  as  well  as  with
+        that  PCRE  is  compiled  with Unicode property support as well as with
         UTF-8 support.
           PCRE_DOLLAR_ENDONLY
-        If  this bit is set, a dollar metacharacter in the pattern matches only
+        If this bit is set, a dollar metacharacter in the pattern matches  only
-        at the end of the subject string. Without this option,  a  dollar  also
+        at  the  end  of the subject string. Without this option, a dollar also
-        matches  immediately before a newline at the end of the string (but not
+        matches immediately before a newline at the end of the string (but  not
-        before any other newlines). The PCRE_DOLLAR_ENDONLY option  is  ignored
+        before  any  other newlines). The PCRE_DOLLAR_ENDONLY option is ignored
-        if  PCRE_MULTILINE  is  set.   There is no equivalent to this option in
+        if PCRE_MULTILINE is set.  There is no equivalent  to  this  option  in
         Perl, and no way to set it within a pattern.
           PCRE_DOTALL
         If this bit is set, a dot metacharater in the pattern matches all char-
-        acters,  including  those that indicate newline. Without it, a dot does
+        acters, including those that indicate newline. Without it, a  dot  does
-        not match when the current position is at a  newline.  This  option  is
+        not  match  when  the  current position is at a newline. This option is
-        equivalent  to Perl's /s option, and it can be changed within a pattern
+        equivalent to Perl's /s option, and it can be changed within a  pattern
-        by a (?s) option setting. A negative class such as [^a] always  matches
+        by  a (?s) option setting. A negative class such as [^a] always matches
         newline characters, independent of the setting of this option.
           PCRE_DUPNAMES
-        If  this  bit is set, names used to identify capturing subpatterns need
+        If this bit is set, names used to identify capturing  subpatterns  need
         not be unique. This can be helpful for certain types of pattern when it
-        is  known  that  only  one instance of the named subpattern can ever be
+        is known that only one instance of the named  subpattern  can  ever  be
-        matched. There are more details of named subpatterns  below;  see  also
+        matched.  There  are  more details of named subpatterns below; see also
         the pcrepattern documentation.
           PCRE_EXTENDED
-        If  this  bit  is  set,  whitespace  data characters in the pattern are
+        If this bit is set, whitespace  data  characters  in  the  pattern  are
         totally ignored except when escaped or inside a character class. White-
         space does not include the VT character (code 11). In addition, charac-
         ters between an unescaped # outside a character class and the next new-
-        line,  inclusive,  are  also  ignored.  This is equivalent to Perl's /x
+        line, inclusive, are also ignored. This  is  equivalent  to  Perl's  /x
-        option, and it can be changed within a pattern by a  (?x)  option  set-
+        option,  and  it  can be changed within a pattern by a (?x) option set-
         ting.
-        This  option  makes  it possible to include comments inside complicated
+        This option makes it possible to include  comments  inside  complicated
-        patterns.  Note, however, that this applies only  to  data  characters.
+        patterns.   Note,  however,  that this applies only to data characters.
-        Whitespace   characters  may  never  appear  within  special  character
+        Whitespace  characters  may  never  appear  within  special   character
-        sequences in a pattern, for  example  within  the  sequence  (?(  which
+        sequences  in  a  pattern,  for  example  within the sequence (?( which
         introduces a conditional subpattern.
           PCRE_EXTRA
-        This  option  was invented in order to turn on additional functionality
+        This option was invented in order to turn on  additional  functionality
-        of PCRE that is incompatible with Perl, but it  is  currently  of  very
+        of  PCRE  that  is  incompatible with Perl, but it is currently of very
-        little  use. When set, any backslash in a pattern that is followed by a
+        little use. When set, any backslash in a pattern that is followed by  a
-        letter that has no special meaning  causes  an  error,  thus  reserving
+        letter  that  has  no  special  meaning causes an error, thus reserving
-        these  combinations  for  future  expansion.  By default, as in Perl, a
+        these combinations for future expansion. By  default,  as  in  Perl,  a
-        backslash followed by a letter with no special meaning is treated as  a
+        backslash  followed by a letter with no special meaning is treated as a
-        literal.  (Perl can, however, be persuaded to give a warning for this.)
+        literal. (Perl can, however, be persuaded to give a warning for  this.)
-        There are at present no other features controlled by  this  option.  It
+        There  are  at  present no other features controlled by this option. It
         can also be set by a (?X) option setting within a pattern.
           PCRE_FIRSTLINE
-        If  this  option  is  set,  an  unanchored pattern is required to match
+        If this option is set, an  unanchored  pattern  is  required  to  match
-        before or at the first  newline  in  the  subject  string,  though  the
+        before  or  at  the  first  newline  in  the subject string, though the
         matched text may continue over the newline.
           PCRE_JAVASCRIPT_COMPAT
         If this option is set, PCRE's behaviour is changed in some ways so that
-        it is compatible with JavaScript rather than Perl. The changes  are  as
+        it  is  compatible with JavaScript rather than Perl. The changes are as
         follows:
-        (1)  A  lone  closing square bracket in a pattern causes a compile-time
+        (1) A lone closing square bracket in a pattern  causes  a  compile-time
-        error, because this is illegal in JavaScript (by default it is  treated
+        error,  because this is illegal in JavaScript (by default it is treated
         as a data character). Thus, the pattern AB]CD becomes illegal when this
         option is set.
-        (2) At run time, a back reference to an unset subpattern group  matches
+        (2)  At run time, a back reference to an unset subpattern group matches
-        an  empty  string (by default this causes the current matching alterna-
+        an empty string (by default this causes the current  matching  alterna-
-        tive to fail). A pattern such as (\1)(a) succeeds when this  option  is
+        tive  to  fail). A pattern such as (\1)(a) succeeds when this option is
-        set  (assuming  it can find an "a" in the subject), whereas it fails by
+        set (assuming it can find an "a" in the subject), whereas it  fails  by
         default, for Perl compatibility.
           PCRE_MULTILINE
-        By default, PCRE treats the subject string as consisting  of  a  single
+        By  default,  PCRE  treats the subject string as consisting of a single
-        line  of characters (even if it actually contains newlines). The "start
+        line of characters (even if it actually contains newlines). The  "start
-        of line" metacharacter (^) matches only at the  start  of  the  string,
+        of  line"  metacharacter  (^)  matches only at the start of the string,
-        while  the  "end  of line" metacharacter ($) matches only at the end of
+        while the "end of line" metacharacter ($) matches only at  the  end  of
         the string, or before a terminating newline (unless PCRE_DOLLAR_ENDONLY
         is set). This is the same as Perl.
-        When  PCRE_MULTILINE  it  is set, the "start of line" and "end of line"
+        When PCRE_MULTILINE it is set, the "start of line" and  "end  of  line"
-        constructs match immediately following or immediately  before  internal
+        constructs  match  immediately following or immediately before internal
-        newlines  in  the  subject string, respectively, as well as at the very
+        newlines in the subject string, respectively, as well as  at  the  very
-        start and end. This is equivalent to Perl's /m option, and  it  can  be
+        start  and  end.  This is equivalent to Perl's /m option, and it can be
         changed within a pattern by a (?m) option setting. If there are no new-
-        lines in a subject string, or no occurrences of ^ or $  in  a  pattern,
+        lines  in  a  subject string, or no occurrences of ^ or $ in a pattern,
         setting PCRE_MULTILINE has no effect.
           PCRE_NEWLINE_CR
-Line 1305 
 COMPILING A PATTERN
+Line 1314 
 COMPILING A PATTERN
           PCRE_NEWLINE_ANYCRLF
           PCRE_NEWLINE_ANY
-        These  options  override the default newline definition that was chosen
+        These options override the default newline definition that  was  chosen
-        when PCRE was built. Setting the first or the second specifies  that  a
+        when  PCRE  was built. Setting the first or the second specifies that a
-        newline  is  indicated  by a single character (CR or LF, respectively).
+        newline is indicated by a single character (CR  or  LF,  respectively).
-        Setting PCRE_NEWLINE_CRLF specifies that a newline is indicated by  the
+        Setting  PCRE_NEWLINE_CRLF specifies that a newline is indicated by the
-        two-character  CRLF  sequence.  Setting  PCRE_NEWLINE_ANYCRLF specifies
+        two-character CRLF  sequence.  Setting  PCRE_NEWLINE_ANYCRLF  specifies
         that any of the three preceding sequences should be recognized. Setting
-        PCRE_NEWLINE_ANY  specifies that any Unicode newline sequence should be
+        PCRE_NEWLINE_ANY specifies that any Unicode newline sequence should  be
         recognized. The Unicode newline sequences are the three just mentioned,
-        plus  the  single  characters  VT (vertical tab, U+000B), FF (formfeed,
+        plus the single characters VT (vertical  tab,  U+000B),  FF  (formfeed,
-        U+000C), NEL (next line, U+0085), LS (line separator, U+2028),  and  PS
+        U+000C),  NEL  (next line, U+0085), LS (line separator, U+2028), and PS
-        (paragraph  separator,  U+2029).  The  last  two are recognized only in
+        (paragraph separator, U+2029). The last  two  are  recognized  only  in
         UTF-8 mode.
-        The newline setting in the  options  word  uses  three  bits  that  are
+        The  newline  setting  in  the  options  word  uses three bits that are
         treated as a number, giving eight possibilities. Currently only six are
-        used (default plus the five values above). This means that if  you  set
+        used  (default  plus the five values above). This means that if you set
-        more  than one newline option, the combination may or may not be sensi-
+        more than one newline option, the combination may or may not be  sensi-
         ble. For example, PCRE_NEWLINE_CR with PCRE_NEWLINE_LF is equivalent to
-        PCRE_NEWLINE_CRLF,  but other combinations may yield unused numbers and
+        PCRE_NEWLINE_CRLF, but other combinations may yield unused numbers  and
         cause an error.
-        The only time that a line break is specially recognized when  compiling
+        The  only time that a line break is specially recognized when compiling
-        a  pattern  is  if  PCRE_EXTENDED  is set, and an unescaped # outside a
+        a pattern is if PCRE_EXTENDED is set, and  an  unescaped  #  outside  a
-        character class is encountered. This indicates  a  comment  that  lasts
+        character  class  is  encountered.  This indicates a comment that lasts
-        until  after the next line break sequence. In other circumstances, line
+        until after the next line break sequence. In other circumstances,  line
-        break  sequences  are  treated  as  literal  data,   except   that   in
+        break   sequences   are   treated  as  literal  data,  except  that  in
         PCRE_EXTENDED mode, both CR and LF are treated as whitespace characters
         and are therefore ignored.
         The newline option that is set at compile time becomes the default that
-        is  used for pcre_exec() and pcre_dfa_exec(), but it can be overridden.
+        is used for pcre_exec() and pcre_dfa_exec(), but it can be overridden.
           PCRE_NO_AUTO_CAPTURE
-Line 1803 
 MATCHING A PATTERN: THE TRADITIONAL FUNC
+Line 1812 
 MATCHING A PATTERN: THE TRADITIONAL FUNC
              const char *subject, int length, int startoffset,
              int options, int *ovector, int ovecsize);
-        The  function pcre_exec() is called to match a subject string against a
+        The function pcre_exec() is called to match a subject string against  a
-        compiled pattern, which is passed in the code argument. If the  pattern
+        compiled  pattern, which is passed in the code argument. If the pattern
         has been studied, the result of the study should be passed in the extra
-        argument. This function is the main matching facility of  the  library,
+        argument.  This  function is the main matching facility of the library,
         and it operates in a Perl-like manner. For specialist use there is also
-        an alternative matching function, which is described below in the  sec-
+        an  alternative matching function, which is described below in the sec-
         tion about the pcre_dfa_exec() function.
-        In  most applications, the pattern will have been compiled (and option-
+        In most applications, the pattern will have been compiled (and  option-
-        ally studied) in the same process that calls pcre_exec().  However,  it
+        ally  studied)  in the same process that calls pcre_exec(). However, it
         is possible to save compiled patterns and study data, and then use them
-        later in different processes, possibly even on different hosts.  For  a
+        later  in  different processes, possibly even on different hosts. For a
         discussion about this, see the pcreprecompile documentation.
         Here is an example of a simple call to pcre_exec():
-Line 1833 
 MATCHING A PATTERN: THE TRADITIONAL FUNC
+Line 1842 
 MATCHING A PATTERN: THE TRADITIONAL FUNC
     Extra data for pcre_exec()
-        If  the  extra argument is not NULL, it must point to a pcre_extra data
+        If the extra argument is not NULL, it must point to a  pcre_extra  data
-        block. The pcre_study() function returns such a block (when it  doesn't
+        block.  The pcre_study() function returns such a block (when it doesn't
-        return  NULL), but you can also create one for yourself, and pass addi-
+        return NULL), but you can also create one for yourself, and pass  addi-
-        tional information in it. The pcre_extra block contains  the  following
+        tional  information  in it. The pcre_extra block contains the following
         fields (not necessarily in this order):
           unsigned long int flags;
-Line 1846 
 MATCHING A PATTERN: THE TRADITIONAL FUNC
+Line 1855 
 MATCHING A PATTERN: THE TRADITIONAL FUNC
           void *callout_data;
           const unsigned char *tables;
-        The  flags  field  is a bitmap that specifies which of the other fields
+        The flags field is a bitmap that specifies which of  the  other  fields
         are set. The flag bits are:
           PCRE_EXTRA_STUDY_DATA
-Line 1855 
 MATCHING A PATTERN: THE TRADITIONAL FUNC
+Line 1864 
 MATCHING A PATTERN: THE TRADITIONAL FUNC
           PCRE_EXTRA_CALLOUT_DATA
           PCRE_EXTRA_TABLES
-        Other flag bits should be set to zero. The study_data field is  set  in
+        Other  flag  bits should be set to zero. The study_data field is set in
-        the  pcre_extra  block  that is returned by pcre_study(), together with
+        the pcre_extra block that is returned by  pcre_study(),  together  with
         the appropriate flag bit. You should not set this yourself, but you may
-        add  to  the  block by setting the other fields and their corresponding
+        add to the block by setting the other fields  and  their  corresponding
         flag bits.
         The match_limit field provides a means of preventing PCRE from using up
-        a  vast amount of resources when running patterns that are not going to
+        a vast amount of resources when running patterns that are not going  to
-        match, but which have a very large number  of  possibilities  in  their
+        match,  but  which  have  a very large number of possibilities in their
-        search  trees.  The  classic  example  is  the  use of nested unlimited
+        search trees. The classic  example  is  the  use  of  nested  unlimited
         repeats.
-        Internally, PCRE uses a function called match() which it calls  repeat-
+        Internally,  PCRE uses a function called match() which it calls repeat-
-        edly  (sometimes  recursively). The limit set by match_limit is imposed
+        edly (sometimes recursively). The limit set by match_limit  is  imposed
-        on the number of times this function is called during  a  match,  which
+        on  the  number  of times this function is called during a match, which
-        has  the  effect  of  limiting the amount of backtracking that can take
+        has the effect of limiting the amount of  backtracking  that  can  take
         place. For patterns that are not anchored, the count restarts from zero
         for each position in the subject string.
-        The  default  value  for  the  limit can be set when PCRE is built; the
+        The default value for the limit can be set  when  PCRE  is  built;  the
-        default default is 10 million, which handles all but the  most  extreme
+        default  default  is 10 million, which handles all but the most extreme
-        cases.  You  can  override  the  default by suppling pcre_exec() with a
+        cases. You can override the default  by  suppling  pcre_exec()  with  a
-        pcre_extra    block    in    which    match_limit    is    set,     and
+        pcre_extra     block    in    which    match_limit    is    set,    and
-        PCRE_EXTRA_MATCH_LIMIT  is  set  in  the  flags  field. If the limit is
+        PCRE_EXTRA_MATCH_LIMIT is set in the  flags  field.  If  the  limit  is
         exceeded, pcre_exec() returns PCRE_ERROR_MATCHLIMIT.
-        The match_limit_recursion field is similar to match_limit, but  instead
+        The  match_limit_recursion field is similar to match_limit, but instead
         of limiting the total number of times that match() is called, it limits
-        the depth of recursion. The recursion depth is a  smaller  number  than
+        the  depth  of  recursion. The recursion depth is a smaller number than
-        the  total number of calls, because not all calls to match() are recur-
+        the total number of calls, because not all calls to match() are  recur-
         sive.  This limit is of use only if it is set smaller than match_limit.
         Limiting  the  recursion  depth  limits the amount of stack that can be
-Line 1916 
 MATCHING A PATTERN: THE TRADITIONAL FUNC
+Line 1925 
 MATCHING A PATTERN: THE TRADITIONAL FUNC
         The unused bits of the options argument for pcre_exec() must  be  zero.
         The  only  bits  that  may  be set are PCRE_ANCHORED, PCRE_NEWLINE_xxx,
-        PCRE_NOTBOL,   PCRE_NOTEOL,   PCRE_NOTEMPTY,   PCRE_NO_UTF8_CHECK   and
+        PCRE_NOTBOL,   PCRE_NOTEOL,   PCRE_NOTEMPTY,    PCRE_NO_START_OPTIMIZE,
-        PCRE_PARTIAL.
+        PCRE_NO_UTF8_CHECK and PCRE_PARTIAL.
           PCRE_ANCHORED
-Line 2011 
 MATCHING A PATTERN: THE TRADITIONAL FUNC
+Line 2020 
 MATCHING A PATTERN: THE TRADITIONAL FUNC
         an ordinary match again. There is some code that demonstrates how to do
         this in the pcredemo.c sample program.
+          PCRE_NO_START_OPTIMIZE
+        There are a number of optimizations that pcre_exec() uses at the  start
+        of  a  match,  in  order to speed up the process. For example, if it is
+        known that a match must start with a specific  character,  it  searches
+        the subject for that character, and fails immediately if it cannot find
+        it, without actually running the main matching function. When  callouts
+        are  in  use,  these  optimizations  can cause them to be skipped. This
+        option disables the "start-up" optimizations,  causing  performance  to
+        suffer, but ensuring that the callouts do occur.
           PCRE_NO_UTF8_CHECK
         When PCRE_UTF8 is set at compile time, the validity of the subject as a
-        UTF-8  string is automatically checked when pcre_exec() is subsequently
+        UTF-8 string is automatically checked when pcre_exec() is  subsequently
-        called.  The value of startoffset is also checked  to  ensure  that  it
+        called.   The  value  of  startoffset is also checked to ensure that it
-        points  to  the start of a UTF-8 character. There is a discussion about
+        points to the start of a UTF-8 character. There is a  discussion  about
-        the validity of UTF-8 strings in the section on UTF-8  support  in  the
+        the  validity  of  UTF-8 strings in the section on UTF-8 support in the
-        main  pcre  page.  If  an  invalid  UTF-8  sequence  of bytes is found,
+        main pcre page. If  an  invalid  UTF-8  sequence  of  bytes  is  found,
-        pcre_exec() returns the error PCRE_ERROR_BADUTF8. If  startoffset  con-
+        pcre_exec()  returns  the error PCRE_ERROR_BADUTF8. If startoffset con-
         tains an invalid value, PCRE_ERROR_BADUTF8_OFFSET is returned.
-        If  you  already  know that your subject is valid, and you want to skip
+        If you already know that your subject is valid, and you  want  to  skip
-        these   checks   for   performance   reasons,   you   can    set    the
+        these    checks    for   performance   reasons,   you   can   set   the
-        PCRE_NO_UTF8_CHECK  option  when calling pcre_exec(). You might want to
+        PCRE_NO_UTF8_CHECK option when calling pcre_exec(). You might  want  to
-        do this for the second and subsequent calls to pcre_exec() if  you  are
+        do  this  for the second and subsequent calls to pcre_exec() if you are
-        making  repeated  calls  to  find  all  the matches in a single subject
+        making repeated calls to find all  the  matches  in  a  single  subject
-        string. However, you should be  sure  that  the  value  of  startoffset
+        string.  However,  you  should  be  sure  that the value of startoffset
-        points  to  the  start of a UTF-8 character. When PCRE_NO_UTF8_CHECK is
+        points to the start of a UTF-8 character.  When  PCRE_NO_UTF8_CHECK  is
-        set, the effect of passing an invalid UTF-8 string as a subject,  or  a
+        set,  the  effect of passing an invalid UTF-8 string as a subject, or a
-        value  of startoffset that does not point to the start of a UTF-8 char-
+        value of startoffset that does not point to the start of a UTF-8  char-
         acter, is undefined. Your program may crash.
           PCRE_PARTIAL
-        This option turns on the  partial  matching  feature.  If  the  subject
+        This  option  turns  on  the  partial  matching feature. If the subject
-        string  fails to match the pattern, but at some point during the match-
+        string fails to match the pattern, but at some point during the  match-
-        ing process the end of the subject was reached (that  is,  the  subject
+        ing  process  the  end of the subject was reached (that is, the subject
-        partially  matches  the  pattern and the failure to match occurred only
+        partially matches the pattern and the failure to  match  occurred  only
-        because there were not enough subject characters), pcre_exec()  returns
+        because  there were not enough subject characters), pcre_exec() returns
-        PCRE_ERROR_PARTIAL  instead of PCRE_ERROR_NOMATCH. When PCRE_PARTIAL is
+        PCRE_ERROR_PARTIAL instead of PCRE_ERROR_NOMATCH. When PCRE_PARTIAL  is
-        used, there are restrictions on what may appear in the  pattern.  These
+        used,  there  are restrictions on what may appear in the pattern. These
         are discussed in the pcrepartial documentation.
     The string to be matched by pcre_exec()
-        The  subject string is passed to pcre_exec() as a pointer in subject, a
+        The subject string is passed to pcre_exec() as a pointer in subject,  a
         length (in bytes) in length, and a starting byte offset in startoffset.
         In UTF-8 mode, the byte offset must point to the start of a UTF-8 char-
-        acter. Unlike the pattern string, the subject may contain  binary  zero
+        acter.  Unlike  the pattern string, the subject may contain binary zero
-        bytes.  When the starting offset is zero, the search for a match starts
+        bytes. When the starting offset is zero, the search for a match  starts
-        at the beginning of the subject, and this is by  far  the  most  common
+        at  the  beginning  of  the subject, and this is by far the most common
         case.
-        A  non-zero  starting offset is useful when searching for another match
+        A non-zero starting offset is useful when searching for  another  match
-        in the same subject by calling pcre_exec() again after a previous  suc-
+        in  the same subject by calling pcre_exec() again after a previous suc-
-        cess.   Setting  startoffset differs from just passing over a shortened
+        cess.  Setting startoffset differs from just passing over  a  shortened
-        string and setting PCRE_NOTBOL in the case of  a  pattern  that  begins
+        string  and  setting  PCRE_NOTBOL  in the case of a pattern that begins
         with any kind of lookbehind. For example, consider the pattern
           \Biss\B
-        which  finds  occurrences  of "iss" in the middle of words. (\B matches
+        which finds occurrences of "iss" in the middle of  words.  (\B  matches
-        only if the current position in the subject is not  a  word  boundary.)
+        only  if  the  current position in the subject is not a word boundary.)
-        When  applied  to the string "Mississipi" the first call to pcre_exec()
+        When applied to the string "Mississipi" the first call  to  pcre_exec()
-        finds the first occurrence. If pcre_exec() is called  again  with  just
+        finds  the  first  occurrence. If pcre_exec() is called again with just
-        the  remainder  of  the  subject,  namely  "issipi", it does not match,
+        the remainder of the subject,  namely  "issipi",  it  does  not  match,
         because \B is always false at the start of the subject, which is deemed
-        to  be  a  word  boundary. However, if pcre_exec() is passed the entire
+        to be a word boundary. However, if pcre_exec()  is  passed  the  entire
         string again, but with startoffset set to 4, it finds the second occur-
-        rence  of "iss" because it is able to look behind the starting point to
+        rence of "iss" because it is able to look behind the starting point  to
         discover that it is preceded by a letter.
-        If a non-zero starting offset is passed when the pattern  is  anchored,
+        If  a  non-zero starting offset is passed when the pattern is anchored,
         one attempt to match at the given offset is made. This can only succeed
-        if the pattern does not require the match to be at  the  start  of  the
+        if  the  pattern  does  not require the match to be at the start of the
         subject.
     How pcre_exec() returns captured substrings
-        In  general, a pattern matches a certain portion of the subject, and in
+        In general, a pattern matches a certain portion of the subject, and  in
-        addition, further substrings from the subject  may  be  picked  out  by
+        addition,  further  substrings  from  the  subject may be picked out by
-        parts  of  the  pattern.  Following the usage in Jeffrey Friedl's book,
+        parts of the pattern. Following the usage  in  Jeffrey  Friedl's  book,
-        this is called "capturing" in what follows, and the  phrase  "capturing
+        this  is  called "capturing" in what follows, and the phrase "capturing
-        subpattern"  is  used for a fragment of a pattern that picks out a sub-
+        subpattern" is used for a fragment of a pattern that picks out  a  sub-
-        string. PCRE supports several other kinds of  parenthesized  subpattern
+        string.  PCRE  supports several other kinds of parenthesized subpattern
         that do not cause substrings to be captured.
         Captured substrings are returned to the caller via a vector of integers
-        whose address is passed in ovector. The number of elements in the  vec-
+        whose  address is passed in ovector. The number of elements in the vec-
-        tor  is  passed in ovecsize, which must be a non-negative number. Note:
+        tor is passed in ovecsize, which must be a non-negative  number.  Note:
         this argument is NOT the size of ovector in bytes.
-        The first two-thirds of the vector is used to pass back  captured  sub-
+        The  first  two-thirds of the vector is used to pass back captured sub-
-        strings,  each  substring using a pair of integers. The remaining third
+        strings, each substring using a pair of integers. The  remaining  third
-        of the vector is used as workspace by pcre_exec() while  matching  cap-
+        of  the  vector is used as workspace by pcre_exec() while matching cap-
-        turing  subpatterns, and is not available for passing back information.
+        turing subpatterns, and is not available for passing back  information.
-        The number passed in ovecsize should always be a multiple of three.  If
+        The  number passed in ovecsize should always be a multiple of three. If
         it is not, it is rounded down.
-        When  a  match  is successful, information about captured substrings is
+        When a match is successful, information about  captured  substrings  is
-        returned in pairs of integers, starting at the  beginning  of  ovector,
+        returned  in  pairs  of integers, starting at the beginning of ovector,
-        and  continuing  up  to two-thirds of its length at the most. The first
+        and continuing up to two-thirds of its length at the  most.  The  first
-        element of each pair is set to the byte offset of the  first  character
+        element  of  each pair is set to the byte offset of the first character
-        in  a  substring, and the second is set to the byte offset of the first
+        in a substring, and the second is set to the byte offset of  the  first
-        character after the end of a substring. Note: these values  are  always
+        character  after  the end of a substring. Note: these values are always
         byte offsets, even in UTF-8 mode. They are not character counts.
-        The  first  pair  of  integers, ovector[0] and ovector[1], identify the
+        The first pair of integers, ovector[0]  and  ovector[1],  identify  the
-        portion of the subject string matched by the entire pattern.  The  next
+        portion  of  the subject string matched by the entire pattern. The next
-        pair  is  used for the first capturing subpattern, and so on. The value
+        pair is used for the first capturing subpattern, and so on.  The  value
         returned by pcre_exec() is one more than the highest numbered pair that
-        has  been  set.  For example, if two substrings have been captured, the
+        has been set.  For example, if two substrings have been  captured,  the
-        returned value is 3. If there are no capturing subpatterns, the  return
+        returned  value is 3. If there are no capturing subpatterns, the return
         value from a successful match is 1, indicating that just the first pair
         of offsets has been set.
         If a capturing subpattern is matched repeatedly, it is the last portion
         of the string that it matched that is returned.
-        If  the vector is too small to hold all the captured substring offsets,
+        If the vector is too small to hold all the captured substring  offsets,
         it is used as far as possible (up to two-thirds of its length), and the
-        function  returns  a value of zero. If the substring offsets are not of
+        function returns a value of zero. If the substring offsets are  not  of
-        interest, pcre_exec() may be called with ovector  passed  as  NULL  and
+        interest,  pcre_exec()  may  be  called with ovector passed as NULL and
-        ovecsize  as zero. However, if the pattern contains back references and
+        ovecsize as zero. However, if the pattern contains back references  and
-        the ovector is not big enough to remember the related substrings,  PCRE
+        the  ovector is not big enough to remember the related substrings, PCRE
-        has  to  get additional memory for use during matching. Thus it is usu-
+        has to get additional memory for use during matching. Thus it  is  usu-
         ally advisable to supply an ovector.
-        The pcre_info() function can be used to find  out  how  many  capturing
+        The  pcre_info()  function  can  be used to find out how many capturing
-        subpatterns  there  are  in  a  compiled pattern. The smallest size for
+        subpatterns there are in a compiled  pattern.  The  smallest  size  for
-        ovector that will allow for n captured substrings, in addition  to  the
+        ovector  that  will allow for n captured substrings, in addition to the
         offsets of the substring matched by the whole pattern, is (n+1)*3.
-        It  is  possible for capturing subpattern number n+1 to match some part
+        It is possible for capturing subpattern number n+1 to match  some  part
         of the subject when subpattern n has not been used at all. For example,
-        if  the  string  "abc"  is  matched against the pattern (a|(z))(bc) the
+        if the string "abc" is matched  against  the  pattern  (a|(z))(bc)  the
         return from the function is 4, and subpatterns 1 and 3 are matched, but
- is  not.  When  this happens, both values in the offset pairs corre-
+is not. When this happens, both values in  the  offset  pairs  corre-
         sponding to unused subpatterns are set to -1.
-        Offset values that correspond to unused subpatterns at the end  of  the
+        Offset  values  that correspond to unused subpatterns at the end of the
-        expression  are  also  set  to  -1. For example, if the string "abc" is
+        expression are also set to -1. For example,  if  the  string  "abc"  is
-        matched against the pattern (abc)(x(yz)?)? subpatterns 2 and 3 are  not
+        matched  against the pattern (abc)(x(yz)?)? subpatterns 2 and 3 are not
-        matched.  The  return  from the function is 2, because the highest used
+        matched. The return from the function is 2, because  the  highest  used
         capturing subpattern number is 1. However, you can refer to the offsets
-        for  the  second  and third capturing subpatterns if you wish (assuming
+        for the second and third capturing subpatterns if  you  wish  (assuming
         the vector is large enough, of course).
-        Some convenience functions are provided  for  extracting  the  captured
+        Some  convenience  functions  are  provided for extracting the captured
         substrings as separate strings. These are described below.
     Error return values from pcre_exec()
-        If  pcre_exec()  fails, it returns a negative number. The following are
+        If pcre_exec() fails, it returns a negative number. The  following  are
         defined in the header file:
           PCRE_ERROR_NOMATCH        (-1)
-Line 2163 
 MATCHING A PATTERN: THE TRADITIONAL FUNC
+Line 2183 
 MATCHING A PATTERN: THE TRADITIONAL FUNC
           PCRE_ERROR_NULL           (-2)
-        Either code or subject was passed as NULL,  or  ovector  was  NULL  and
+        Either  code  or  subject  was  passed as NULL, or ovector was NULL and
         ovecsize was not zero.
           PCRE_ERROR_BADOPTION      (-3)
-Line 2172 
 MATCHING A PATTERN: THE TRADITIONAL FUNC
+Line 2192 
 MATCHING A PATTERN: THE TRADITIONAL FUNC
           PCRE_ERROR_BADMAGIC       (-4)
-        PCRE  stores a 4-byte "magic number" at the start of the compiled code,
+        PCRE stores a 4-byte "magic number" at the start of the compiled  code,
         to catch the case when it is passed a junk pointer and to detect when a
         pattern that was compiled in an environment of one endianness is run in
-        an environment with the other endianness. This is the error  that  PCRE
+        an  environment  with the other endianness. This is the error that PCRE
         gives when the magic number is not present.
           PCRE_ERROR_UNKNOWN_OPCODE (-5)
         While running the pattern match, an unknown item was encountered in the
-        compiled pattern. This error could be caused by a bug  in  PCRE  or  by
+        compiled  pattern.  This  error  could be caused by a bug in PCRE or by
         overwriting of the compiled pattern.
           PCRE_ERROR_NOMEMORY       (-6)
-        If  a  pattern contains back references, but the ovector that is passed
+        If a pattern contains back references, but the ovector that  is  passed
         to pcre_exec() is not big enough to remember the referenced substrings,
-        PCRE  gets  a  block of memory at the start of matching to use for this
+        PCRE gets a block of memory at the start of matching to  use  for  this
-        purpose. If the call via pcre_malloc() fails, this error is given.  The
+        purpose.  If the call via pcre_malloc() fails, this error is given. The
         memory is automatically freed at the end of matching.
           PCRE_ERROR_NOSUBSTRING    (-7)
-        This  error is used by the pcre_copy_substring(), pcre_get_substring(),
+        This error is used by the pcre_copy_substring(),  pcre_get_substring(),
         and  pcre_get_substring_list()  functions  (see  below).  It  is  never
         returned by pcre_exec().
           PCRE_ERROR_MATCHLIMIT     (-8)
-        The  backtracking  limit,  as  specified  by the match_limit field in a
+        The backtracking limit, as specified by  the  match_limit  field  in  a
-        pcre_extra structure (or defaulted) was reached.  See  the  description
+        pcre_extra  structure  (or  defaulted) was reached. See the description
         above.
           PCRE_ERROR_CALLOUT        (-9)
         This error is never generated by pcre_exec() itself. It is provided for
-        use by callout functions that want to yield a distinctive  error  code.
+        use  by  callout functions that want to yield a distinctive error code.
         See the pcrecallout documentation for details.
           PCRE_ERROR_BADUTF8        (-10)
-        A  string  that contains an invalid UTF-8 byte sequence was passed as a
+        A string that contains an invalid UTF-8 byte sequence was passed  as  a
         subject.
           PCRE_ERROR_BADUTF8_OFFSET (-11)
         The UTF-8 byte sequence that was passed as a subject was valid, but the
-        value  of startoffset did not point to the beginning of a UTF-8 charac-
+        value of startoffset did not point to the beginning of a UTF-8  charac-
         ter.
           PCRE_ERROR_PARTIAL        (-12)
-        The subject string did not match, but it did match partially.  See  the
+        The  subject  string did not match, but it did match partially. See the
         pcrepartial documentation for details of partial matching.
           PCRE_ERROR_BADPARTIAL     (-13)
-        The  PCRE_PARTIAL  option  was  used with a compiled pattern containing
+        The PCRE_PARTIAL option was used with  a  compiled  pattern  containing
-        items that are not supported for partial matching. See the  pcrepartial
+        items  that are not supported for partial matching. See the pcrepartial
         documentation for details of partial matching.
           PCRE_ERROR_INTERNAL       (-14)
-        An  unexpected  internal error has occurred. This error could be caused
+        An unexpected internal error has occurred. This error could  be  caused
         by a bug in PCRE or by overwriting of the compiled pattern.
           PCRE_ERROR_BADCOUNT       (-15)
-        This error is given if the value of the ovecsize argument is  negative.
+        This error is given if the value of the ovecsize argument is negative.
           PCRE_ERROR_RECURSIONLIMIT (-21)
-Line 2389 
 EXTRACTING CAPTURED SUBSTRINGS BY NAME
+Line 2409 
 EXTRACTING CAPTURED SUBSTRINGS BY NAME
         ate. NOTE: If PCRE_DUPNAMES is set and there are duplicate  names,  the
         behaviour may not be what you want (see the next section).
+        Warning:  If the pattern uses the "(?|" feature to set up multiple sub-
+        patterns with the same number, you  cannot  use  names  to  distinguish
+        them, because names are not included in the compiled code. The matching
+        process uses only numbers.
  DUPLICATE SUBPATTERN NAMES
         int pcre_get_stringtable_entries(const pcre *code,
              const char *name, char **first, char **last);
-        When  a  pattern  is  compiled with the PCRE_DUPNAMES option, names for
+        When a pattern is compiled with the  PCRE_DUPNAMES  option,  names  for
-        subpatterns are not required to  be  unique.  Normally,  patterns  with
+        subpatterns  are  not  required  to  be unique. Normally, patterns with
-        duplicate  names  are such that in any one match, only one of the named
+        duplicate names are such that in any one match, only one of  the  named
-        subpatterns participates. An example is shown in the pcrepattern  docu-
+        subpatterns  participates. An example is shown in the pcrepattern docu-
         mentation.
-        When    duplicates   are   present,   pcre_copy_named_substring()   and
+        When   duplicates   are   present,   pcre_copy_named_substring()    and
-        pcre_get_named_substring() return the first substring corresponding  to
+        pcre_get_named_substring()  return the first substring corresponding to
-        the  given  name  that  is set. If none are set, PCRE_ERROR_NOSUBSTRING
+        the given name that is set. If  none  are  set,  PCRE_ERROR_NOSUBSTRING
-        (-7) is returned; no  data  is  returned.  The  pcre_get_stringnumber()
+        (-7)  is  returned;  no  data  is returned. The pcre_get_stringnumber()
-        function  returns one of the numbers that are associated with the name,
+        function returns one of the numbers that are associated with the  name,
         but it is not defined which it is.
-        If you want to get full details of all captured substrings for a  given
+        If  you want to get full details of all captured substrings for a given
-        name,  you  must  use  the pcre_get_stringtable_entries() function. The
+        name, you must use  the  pcre_get_stringtable_entries()  function.  The
         first argument is the compiled pattern, and the second is the name. The
-        third  and  fourth  are  pointers to variables which are updated by the
+        third and fourth are pointers to variables which  are  updated  by  the
         function. After it has run, they point to the first and last entries in
-        the  name-to-number  table  for  the  given  name.  The function itself
+        the name-to-number table  for  the  given  name.  The  function  itself
-        returns the length of each entry,  or  PCRE_ERROR_NOSUBSTRING  (-7)  if
+        returns  the  length  of  each entry, or PCRE_ERROR_NOSUBSTRING (-7) if
-        there  are none. The format of the table is described above in the sec-
+        there are none. The format of the table is described above in the  sec-
-        tion entitled Information about a  pattern.   Given  all  the  relevant
+        tion  entitled  Information  about  a  pattern.  Given all the relevant
-        entries  for the name, you can extract each of their numbers, and hence
+        entries for the name, you can extract each of their numbers, and  hence
         the captured data, if any.
  FINDING ALL POSSIBLE MATCHES
-        The traditional matching function uses a  similar  algorithm  to  Perl,
+        The  traditional  matching  function  uses a similar algorithm to Perl,
         which stops when it finds the first match, starting at a given point in
-        the subject. If you want to find all possible matches, or  the  longest
+        the  subject.  If you want to find all possible matches, or the longest
-        possible  match,  consider using the alternative matching function (see
+        possible match, consider using the alternative matching  function  (see
-        below) instead. If you cannot use the alternative function,  but  still
+        below)  instead.  If you cannot use the alternative function, but still
-        need  to  find all possible matches, you can kludge it up by making use
+        need to find all possible matches, you can kludge it up by  making  use
         of the callout facility, which is described in the pcrecallout documen-
         tation.
         What you have to do is to insert a callout right at the end of the pat-
-        tern.  When your callout function is called, extract and save the  cur-
+        tern.   When your callout function is called, extract and save the cur-
-        rent  matched  substring.  Then  return  1, which forces pcre_exec() to
+        rent matched substring. Then return  1,  which  forces  pcre_exec()  to
-        backtrack and try other alternatives. Ultimately, when it runs  out  of
+        backtrack  and  try other alternatives. Ultimately, when it runs out of
         matches, pcre_exec() will yield PCRE_ERROR_NOMATCH.
-Line 2446 
 MATCHING A PATTERN: THE ALTERNATIVE FUNC
+Line 2471 
 MATCHING A PATTERN: THE ALTERNATIVE FUNC
              int options, int *ovector, int ovecsize,
              int *workspace, int wscount);
-        The  function  pcre_dfa_exec()  is  called  to  match  a subject string
+        The function pcre_dfa_exec()  is  called  to  match  a  subject  string
-        against a compiled pattern, using a matching algorithm that  scans  the
+        against  a  compiled pattern, using a matching algorithm that scans the
-        subject  string  just  once, and does not backtrack. This has different
+        subject string just once, and does not backtrack.  This  has  different
-        characteristics to the normal algorithm, and  is  not  compatible  with
+        characteristics  to  the  normal  algorithm, and is not compatible with
-        Perl.  Some  of the features of PCRE patterns are not supported. Never-
+        Perl. Some of the features of PCRE patterns are not  supported.  Never-
-        theless, there are times when this kind of matching can be useful.  For
+        theless,  there are times when this kind of matching can be useful. For
         a discussion of the two matching algorithms, see the pcrematching docu-
         mentation.
-        The arguments for the pcre_dfa_exec() function  are  the  same  as  for
+        The  arguments  for  the  pcre_dfa_exec()  function are the same as for
         pcre_exec(), plus two extras. The ovector argument is used in a differ-
-        ent way, and this is described below. The other  common  arguments  are
+        ent  way,  and  this is described below. The other common arguments are
-        used  in  the  same way as for pcre_exec(), so their description is not
+        used in the same way as for pcre_exec(), so their  description  is  not
         repeated here.
-        The two additional arguments provide workspace for  the  function.  The
+        The  two  additional  arguments provide workspace for the function. The
-        workspace  vector  should  contain at least 20 elements. It is used for
+        workspace vector should contain at least 20 elements. It  is  used  for
         keeping  track  of  multiple  paths  through  the  pattern  tree.  More
-        workspace  will  be  needed for patterns and subjects where there are a
+        workspace will be needed for patterns and subjects where  there  are  a
         lot of potential matches.
         Here is an example of a simple call to pcre_dfa_exec():
-Line 2486 
 MATCHING A PATTERN: THE ALTERNATIVE FUNC
+Line 2511 
 MATCHING A PATTERN: THE ALTERNATIVE FUNC
     Option bits for pcre_dfa_exec()
-        The unused bits of the options argument  for  pcre_dfa_exec()  must  be
+        The  unused  bits  of  the options argument for pcre_dfa_exec() must be
-        zero.  The  only  bits  that  may  be  set are PCRE_ANCHORED, PCRE_NEW-
+        zero. The only bits  that  may  be  set  are  PCRE_ANCHORED,  PCRE_NEW-
-        LINE_xxx, PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY,  PCRE_NO_UTF8_CHECK,
+        LINE_xxx,  PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, PCRE_NO_UTF8_CHECK,
         PCRE_PARTIAL, PCRE_DFA_SHORTEST, and PCRE_DFA_RESTART. All but the last
         three of these are the same as for pcre_exec(), so their description is
         not repeated here.
           PCRE_PARTIAL
-        This  has  the  same general effect as it does for pcre_exec(), but the
+        This has the same general effect as it does for  pcre_exec(),  but  the
-        details  are  slightly  different.  When  PCRE_PARTIAL   is   set   for
+        details   are   slightly   different.  When  PCRE_PARTIAL  is  set  for
-        pcre_dfa_exec(),  the  return code PCRE_ERROR_NOMATCH is converted into
+        pcre_dfa_exec(), the return code PCRE_ERROR_NOMATCH is  converted  into
-        PCRE_ERROR_PARTIAL if the end of the subject  is  reached,  there  have
+        PCRE_ERROR_PARTIAL  if  the  end  of the subject is reached, there have
         been no complete matches, but there is still at least one matching pos-
-        sibility. The portion of the string that provided the partial match  is
+        sibility.  The portion of the string that provided the partial match is
         set as the first matching string.
           PCRE_DFA_SHORTEST
-        Setting  the  PCRE_DFA_SHORTEST option causes the matching algorithm to
+        Setting the PCRE_DFA_SHORTEST option causes the matching  algorithm  to
         stop as soon as it has found one match. Because of the way the alterna-
-        tive  algorithm  works, this is necessarily the shortest possible match
+        tive algorithm works, this is necessarily the shortest  possible  match
         at the first possible matching point in the subject string.
           PCRE_DFA_RESTART
-        When pcre_dfa_exec()  is  called  with  the  PCRE_PARTIAL  option,  and
+        When  pcre_dfa_exec()  is  called  with  the  PCRE_PARTIAL  option, and
-        returns  a  partial  match, it is possible to call it again, with addi-
+        returns a partial match, it is possible to call it  again,  with  addi-
-        tional subject characters, and have it continue with  the  same  match.
+        tional  subject  characters,  and have it continue with the same match.
-        The  PCRE_DFA_RESTART  option requests this action; when it is set, the
+        The PCRE_DFA_RESTART option requests this action; when it is  set,  the
-        workspace and wscount options must reference the same vector as  before
+        workspace  and wscount options must reference the same vector as before
-        because  data  about  the  match so far is left in them after a partial
+        because data about the match so far is left in  them  after  a  partial
-        match. There is more discussion of this  facility  in  the  pcrepartial
+        match.  There  is  more  discussion of this facility in the pcrepartial
         documentation.
     Successful returns from pcre_dfa_exec()
-        When  pcre_dfa_exec()  succeeds, it may have matched more than one sub-
+        When pcre_dfa_exec() succeeds, it may have matched more than  one  sub-
         string in the subject. Note, however, that all the matches from one run
-        of  the  function  start  at the same point in the subject. The shorter
+        of the function start at the same point in  the  subject.  The  shorter
-        matches are all initial substrings of the longer matches. For  example,
+        matches  are all initial substrings of the longer matches. For example,
         if the pattern
           <.*>
-Line 2541 
 MATCHING A PATTERN: THE ALTERNATIVE FUNC
+Line 2566 
 MATCHING A PATTERN: THE ALTERNATIVE FUNC
           <something> <something else>
           <something> <something else> <something further>
-        On  success,  the  yield of the function is a number greater than zero,
+        On success, the yield of the function is a number  greater  than  zero,
-        which is the number of matched substrings.  The  substrings  themselves
+        which  is  the  number of matched substrings. The substrings themselves
-        are  returned  in  ovector. Each string uses two elements; the first is
+        are returned in ovector. Each string uses two elements;  the  first  is
-        the offset to the start, and the second is the offset to  the  end.  In
+        the  offset  to  the start, and the second is the offset to the end. In
-        fact,  all  the  strings  have the same start offset. (Space could have
+        fact, all the strings have the same start  offset.  (Space  could  have
-        been saved by giving this only once, but it was decided to retain  some
+        been  saved by giving this only once, but it was decided to retain some
-        compatibility  with  the  way pcre_exec() returns data, even though the
+        compatibility with the way pcre_exec() returns data,  even  though  the
         meaning of the strings is different.)
         The strings are returned in reverse order of length; that is, the long-
-        est  matching  string is given first. If there were too many matches to
+        est matching string is given first. If there were too many  matches  to
-        fit into ovector, the yield of the function is zero, and the vector  is
+        fit  into ovector, the yield of the function is zero, and the vector is
         filled with the longest matches.
     Error returns from pcre_dfa_exec()
-        The  pcre_dfa_exec()  function returns a negative number when it fails.
+        The pcre_dfa_exec() function returns a negative number when  it  fails.
-        Many of the errors are the same  as  for  pcre_exec(),  and  these  are
+        Many  of  the  errors  are  the  same as for pcre_exec(), and these are
-        described  above.   There are in addition the following errors that are
+        described above.  There are in addition the following errors  that  are
         specific to pcre_dfa_exec():
           PCRE_ERROR_DFA_UITEM      (-16)
-        This return is given if pcre_dfa_exec() encounters an item in the  pat-
+        This  return is given if pcre_dfa_exec() encounters an item in the pat-
-        tern  that  it  does not support, for instance, the use of \C or a back
+        tern that it does not support, for instance, the use of \C  or  a  back
         reference.
           PCRE_ERROR_DFA_UCOND      (-17)
-        This return is given if pcre_dfa_exec()  encounters  a  condition  item
+        This  return  is  given  if pcre_dfa_exec() encounters a condition item
-        that  uses  a back reference for the condition, or a test for recursion
+        that uses a back reference for the condition, or a test  for  recursion
         in a specific group. These are not supported.
           PCRE_ERROR_DFA_UMLIMIT    (-18)
-        This return is given if pcre_dfa_exec() is called with an  extra  block
+        This  return  is given if pcre_dfa_exec() is called with an extra block
         that contains a setting of the match_limit field. This is not supported
         (it is meaningless).
           PCRE_ERROR_DFA_WSSIZE     (-19)
-        This return is given if  pcre_dfa_exec()  runs  out  of  space  in  the
+        This  return  is  given  if  pcre_dfa_exec()  runs  out of space in the
         workspace vector.
           PCRE_ERROR_DFA_RECURSE    (-20)
-        When  a  recursive subpattern is processed, the matching function calls
+        When a recursive subpattern is processed, the matching  function  calls
-        itself recursively, using private vectors for  ovector  and  workspace.
+        itself  recursively,  using  private vectors for ovector and workspace.
-        This  error  is  given  if  the output vector is not large enough. This
+        This error is given if the output vector  is  not  large  enough.  This
         should be extremely rare, as a vector of size 1000 is used.
  SEE ALSO
-        pcrebuild(3), pcrecallout(3), pcrecpp(3)(3), pcrematching(3),  pcrepar-
+        pcrebuild(3),  pcrecallout(3), pcrecpp(3)(3), pcrematching(3), pcrepar-
-        tial(3),  pcreposix(3), pcreprecompile(3), pcresample(3), pcrestack(3).
+        tial(3), pcreposix(3), pcreprecompile(3), pcresample(3), pcrestack(3).
  AUTHOR
-Line 2608 
 AUTHOR
+Line 2633 
 AUTHOR
  REVISION
-        Last updated: 24 August 2008
+        Last updated: 17 March 2009
-        Copyright (c) 1997-2008 University of Cambridge.
+        Copyright (c) 1997-2009 University of Cambridge.
  ------------------------------------------------------------------------------
-Line 2660 
 PCRE CALLOUTS
+Line 2685 
 PCRE CALLOUTS
  MISSING CALLOUTS
         You  should  be  aware  that,  because of optimizations in the way PCRE
-        matches patterns, callouts sometimes do not happen. For example, if the
+        matches patterns by default, callouts  sometimes  do  not  happen.  For
-        pattern is
+        example, if the pattern is
           ab(?C4)cd
-Line 2670 
 MISSING CALLOUTS
+Line 2695 
 MISSING CALLOUTS
         ever  start,  and  the  callout is never reached. However, with "abyd",
         though the result is still no match, the callout is obeyed.
+        You can disable these optimizations by passing the  PCRE_NO_START_OPTI-
+        MIZE  option  to  pcre_exec()  or  pcre_dfa_exec(). This slows down the
+        matching process, but does ensure that callouts  such  as  the  example
+        above are obeyed.
  THE CALLOUT INTERFACE
-        During matching, when PCRE reaches a callout point, the external  func-
+        During  matching, when PCRE reaches a callout point, the external func-
-        tion  defined by pcre_callout is called (if it is set). This applies to
+        tion defined by pcre_callout is called (if it is set). This applies  to
-        both the pcre_exec() and the pcre_dfa_exec()  matching  functions.  The
+        both  the  pcre_exec()  and the pcre_dfa_exec() matching functions. The
-        only  argument  to  the callout function is a pointer to a pcre_callout
+        only argument to the callout function is a pointer  to  a  pcre_callout
         block. This structure contains the following fields:
           int          version;
-Line 2692 
 THE CALLOUT INTERFACE
+Line 2722 
 THE CALLOUT INTERFACE
           int          pattern_position;
           int          next_item_length;
-        The version field is an integer containing the version  number  of  the
+        The  version  field  is an integer containing the version number of the
-        block  format. The initial version was 0; the current version is 1. The
+        block format. The initial version was 0; the current version is 1.  The
-        version number will change again in future  if  additional  fields  are
+        version  number  will  change  again in future if additional fields are
         added, but the intention is never to remove any of the existing fields.
         The callout_number field contains the number of the  callout,  as  com-
-Line 2779 
 AUTHOR
+Line 2809 
 AUTHOR
  REVISION
-        Last updated: 29 May 2007
+        Last updated: 15 March 2009
-        Copyright (c) 1997-2007 University of Cambridge.
+        Copyright (c) 1997-2009 University of Cambridge.
  ------------------------------------------------------------------------------
-Line 3059 
 CHARACTERS AND METACHARACTERS
+Line 3089 
 CHARACTERS AND METACHARACTERS
                    syntax)
           ]      terminates the character class
-        The  following sections describe the use of each of the metacharacters.
+        The following sections describe the use of each of the metacharacters.
  BACKSLASH
         The backslash character has several uses. Firstly, if it is followed by
-        a  non-alphanumeric  character,  it takes away any special meaning that
+        a non-alphanumeric character, it takes away any  special  meaning  that
-        character may have. This  use  of  backslash  as  an  escape  character
+        character  may  have.  This  use  of  backslash  as an escape character
         applies both inside and outside character classes.
-        For  example,  if  you want to match a * character, you write \* in the
+        For example, if you want to match a * character, you write  \*  in  the
-        pattern.  This escaping action applies whether  or  not  the  following
+        pattern.   This  escaping  action  applies whether or not the following
-        character  would  otherwise be interpreted as a metacharacter, so it is
+        character would otherwise be interpreted as a metacharacter, so  it  is
-        always safe to precede a non-alphanumeric  with  backslash  to  specify
+        always  safe  to  precede  a non-alphanumeric with backslash to specify
-        that  it stands for itself. In particular, if you want to match a back-
+        that it stands for itself. In particular, if you want to match a  back-
         slash, you write \\.
-        If a pattern is compiled with the PCRE_EXTENDED option,  whitespace  in
+        If  a  pattern is compiled with the PCRE_EXTENDED option, whitespace in
-        the  pattern (other than in a character class) and characters between a
+        the pattern (other than in a character class) and characters between  a
         # outside a character class and the next newline are ignored. An escap-
-        ing  backslash  can  be  used to include a whitespace or # character as
+        ing backslash can be used to include a whitespace  or  #  character  as
         part of the pattern.
-        If you want to remove the special meaning from a  sequence  of  charac-
+        If  you  want  to remove the special meaning from a sequence of charac-
-        ters,  you can do so by putting them between \Q and \E. This is differ-
+        ters, you can do so by putting them between \Q and \E. This is  differ-
-        ent from Perl in that $ and  @  are  handled  as  literals  in  \Q...\E
+        ent  from  Perl  in  that  $  and  @ are handled as literals in \Q...\E
-        sequences  in  PCRE, whereas in Perl, $ and @ cause variable interpola-
+        sequences in PCRE, whereas in Perl, $ and @ cause  variable  interpola-
         tion. Note the following examples:
           Pattern            PCRE matches   Perl matches
-Line 3095 
 BACKSLASH
+Line 3125 
 BACKSLASH
           \Qabc\$xyz\E       abc\$xyz       abc\$xyz
           \Qabc\E\$\Qxyz\E   abc$xyz        abc$xyz
-        The \Q...\E sequence is recognized both inside  and  outside  character
+        The  \Q...\E  sequence  is recognized both inside and outside character
         classes.
     Non-printing characters
         A second use of backslash provides a way of encoding non-printing char-
-        acters in patterns in a visible manner. There is no restriction on  the
+        acters  in patterns in a visible manner. There is no restriction on the
-        appearance  of non-printing characters, apart from the binary zero that
+        appearance of non-printing characters, apart from the binary zero  that
-        terminates a pattern, but when a pattern  is  being  prepared  by  text
+        terminates  a  pattern,  but  when  a pattern is being prepared by text
-        editing,  it  is  usually  easier  to  use  one of the following escape
+        editing, it is usually easier  to  use  one  of  the  following  escape
         sequences than the binary character it represents:
           \a        alarm, that is, the BEL character (hex 07)
-Line 3118 
 BACKSLASH
+Line 3148 
 BACKSLASH
           \xhh      character with hex code hh
           \x{hhh..} character with hex code hhh..
-        The precise effect of \cx is as follows: if x is a lower  case  letter,
+        The  precise  effect of \cx is as follows: if x is a lower case letter,
-        it  is converted to upper case. Then bit 6 of the character (hex 40) is
+        it is converted to upper case. Then bit 6 of the character (hex 40)  is
-        inverted.  Thus \cz becomes hex 1A, but \c{ becomes hex 3B,  while  \c;
+        inverted.   Thus  \cz becomes hex 1A, but \c{ becomes hex 3B, while \c;
         becomes hex 7B.
-        After  \x, from zero to two hexadecimal digits are read (letters can be
+        After \x, from zero to two hexadecimal digits are read (letters can  be
-        in upper or lower case). Any number of hexadecimal  digits  may  appear
+        in  upper  or  lower case). Any number of hexadecimal digits may appear
-        between  \x{  and  },  but the value of the character code must be less
+        between \x{ and }, but the value of the character  code  must  be  less
         than 256 in non-UTF-8 mode, and less than 2**31 in UTF-8 mode. That is,
-        the  maximum value in hexadecimal is 7FFFFFFF. Note that this is bigger
+        the maximum value in hexadecimal is 7FFFFFFF. Note that this is  bigger
         than the largest Unicode code point, which is 10FFFF.
-        If characters other than hexadecimal digits appear between \x{  and  },
+        If  characters  other than hexadecimal digits appear between \x{ and },
         or if there is no terminating }, this form of escape is not recognized.
-        Instead, the initial \x will be  interpreted  as  a  basic  hexadecimal
+        Instead,  the  initial  \x  will  be interpreted as a basic hexadecimal
-        escape,  with  no  following  digits, giving a character whose value is
+        escape, with no following digits, giving a  character  whose  value  is
         zero.
         Characters whose value is less than 256 can be defined by either of the
-        two  syntaxes  for  \x. There is no difference in the way they are han-
+        two syntaxes for \x. There is no difference in the way  they  are  han-
         dled. For example, \xdc is exactly the same as \x{dc}.
-        After \0 up to two further octal digits are read. If  there  are  fewer
+        After  \0  up  to two further octal digits are read. If there are fewer
-        than  two  digits,  just  those  that  are  present  are used. Thus the
+        than two digits, just  those  that  are  present  are  used.  Thus  the
         sequence \0\x\07 specifies two binary zeros followed by a BEL character
-        (code  value 7). Make sure you supply two digits after the initial zero
+        (code value 7). Make sure you supply two digits after the initial  zero
         if the pattern character that follows is itself an octal digit.
         The handling of a backslash followed by a digit other than 0 is compli-
         cated.  Outside a character class, PCRE reads it and any following dig-
-        its as a decimal number. If the number is less than  10,  or  if  there
+        its  as  a  decimal  number. If the number is less than 10, or if there
         have been at least that many previous capturing left parentheses in the
-        expression, the entire  sequence  is  taken  as  a  back  reference.  A
+        expression,  the  entire  sequence  is  taken  as  a  back reference. A
-        description  of how this works is given later, following the discussion
+        description of how this works is given later, following the  discussion
         of parenthesized subpatterns.
-        Inside a character class, or if the decimal number is  greater  than  9
+        Inside  a  character  class, or if the decimal number is greater than 9
-        and  there have not been that many capturing subpatterns, PCRE re-reads
+        and there have not been that many capturing subpatterns, PCRE  re-reads
         up to three octal digits following the backslash, and uses them to gen-
-        erate  a data character. Any subsequent digits stand for themselves. In
+        erate a data character. Any subsequent digits stand for themselves.  In
-        non-UTF-8 mode, the value of a character specified  in  octal  must  be
+        non-UTF-8  mode,  the  value  of a character specified in octal must be
-        less  than  \400.  In  UTF-8 mode, values up to \777 are permitted. For
+        less than \400. In UTF-8 mode, values up to  \777  are  permitted.  For
         example:
           \040   is another way of writing a space
-Line 3177 
 BACKSLASH
+Line 3207 
 BACKSLASH
           \81    is either a back reference, or a binary zero
                     followed by the two characters "8" and "1"
-        Note that octal values of 100 or greater must not be  introduced  by  a
+        Note  that  octal  values of 100 or greater must not be introduced by a
         leading zero, because no more than three octal digits are ever read.
         All the sequences that define a single character value can be used both
-        inside and outside character classes. In addition, inside  a  character
+        inside  and  outside character classes. In addition, inside a character
-        class,  the  sequence \b is interpreted as the backspace character (hex
+        class, the sequence \b is interpreted as the backspace  character  (hex
-), and the sequences \R and \X are interpreted as the characters  "R"
+),  and the sequences \R and \X are interpreted as the characters "R"
-        and  "X", respectively. Outside a character class, these sequences have
+        and "X", respectively. Outside a character class, these sequences  have
         different meanings (see below).
     Absolute and relative back references
-        The sequence \g followed by an unsigned or a negative  number,  option-
+        The  sequence  \g followed by an unsigned or a negative number, option-
-        ally  enclosed  in braces, is an absolute or relative back reference. A
+        ally enclosed in braces, is an absolute or relative back  reference.  A
         named back reference can be coded as \g{name}. Back references are dis-
         cussed later, following the discussion of parenthesized subpatterns.
     Absolute and relative subroutine calls
-        For  compatibility with Oniguruma, the non-Perl syntax \g followed by a
+        For compatibility with Oniguruma, the non-Perl syntax \g followed by  a
         name or a number enclosed either in angle brackets or single quotes, is
-        an  alternative  syntax for referencing a subpattern as a "subroutine".
+        an alternative syntax for referencing a subpattern as  a  "subroutine".
-        Details are discussed later.   Note  that  \g{...}  (Perl  syntax)  and
+        Details  are  discussed  later.   Note  that  \g{...} (Perl syntax) and
-        \g<...>  (Oniguruma  syntax)  are  not synonymous. The former is a back
+        \g<...> (Oniguruma syntax) are not synonymous. The  former  is  a  back
         reference; the latter is a subroutine call.
     Generic character types
-Line 3220 
 BACKSLASH
+Line 3250 
 BACKSLASH
           \W     any "non-word" character
         Each pair of escape sequences partitions the complete set of characters
-        into two disjoint sets. Any given character matches one, and only  one,
+        into  two disjoint sets. Any given character matches one, and only one,
         of each pair.
         These character type sequences can appear both inside and outside char-
-        acter classes. They each match one character of the  appropriate  type.
+        acter  classes.  They each match one character of the appropriate type.
-        If  the current matching point is at the end of the subject string, all
+        If the current matching point is at the end of the subject string,  all
         of them fail, since there is no character to match.
-        For compatibility with Perl, \s does not match the VT  character  (code
+        For  compatibility  with Perl, \s does not match the VT character (code
-).   This makes it different from the the POSIX "space" class. The \s
+).  This makes it different from the the POSIX "space" class. The  \s
-        characters are HT (9), LF (10), FF (12), CR (13), and  space  (32).  If
+        characters  are  HT  (9), LF (10), FF (12), CR (13), and space (32). If
         "use locale;" is included in a Perl script, \s may match the VT charac-
         ter. In PCRE, it never does.
-        In UTF-8 mode, characters with values greater than 128 never match  \d,
+        In  UTF-8 mode, characters with values greater than 128 never match \d,
         \s, or \w, and always match \D, \S, and \W. This is true even when Uni-
-        code character property support is available.  These  sequences  retain
+        code  character  property  support is available. These sequences retain
         their original meanings from before UTF-8 support was available, mainly
         for efficiency reasons.
         The sequences \h, \H, \v, and \V are Perl 5.10 features. In contrast to
-        the  other  sequences, these do match certain high-valued codepoints in
+        the other sequences, these do match certain high-valued  codepoints  in
         UTF-8 mode.  The horizontal space characters are:
           U+0009     Horizontal tab
-Line 3275 
 BACKSLASH
+Line 3305 
 BACKSLASH
           U+2029     Paragraph separator
         A "word" character is an underscore or any character less than 256 that
-        is  a  letter  or  digit.  The definition of letters and digits is con-
+        is a letter or digit. The definition of  letters  and  digits  is  con-
-        trolled by PCRE's low-valued character tables, and may vary if  locale-
+        trolled  by PCRE's low-valued character tables, and may vary if locale-
-        specific  matching is taking place (see "Locale support" in the pcreapi
+        specific matching is taking place (see "Locale support" in the  pcreapi
-        page). For example, in a French locale such  as  "fr_FR"  in  Unix-like
+        page).  For  example,  in  a French locale such as "fr_FR" in Unix-like
-        systems,  or "french" in Windows, some character codes greater than 128
+        systems, or "french" in Windows, some character codes greater than  128
-        are used for accented letters, and these are matched by \w. The use  of
+        are  used for accented letters, and these are matched by \w. The use of
         locales with Unicode is discouraged.
     Newline sequences
-        Outside  a  character class, by default, the escape sequence \R matches
+        Outside a character class, by default, the escape sequence  \R  matches
         any Unicode newline sequence. This is a Perl 5.10 feature. In non-UTF-8
         mode \R is equivalent to the following:
           (?>\r\n|\n|\x0b|\f|\r|\x85)
-        This  is  an  example  of an "atomic group", details of which are given
+        This is an example of an "atomic group", details  of  which  are  given
         below.  This particular group matches either the two-character sequence
-        CR  followed  by  LF,  or  one  of  the single characters LF (linefeed,
+        CR followed by LF, or  one  of  the  single  characters  LF  (linefeed,
         U+000A), VT (vertical tab, U+000B), FF (formfeed, U+000C), CR (carriage
         return, U+000D), or NEL (next line, U+0085). The two-character sequence
         is treated as a single unit that cannot be split.
-        In UTF-8 mode, two additional characters whose codepoints  are  greater
+        In  UTF-8  mode, two additional characters whose codepoints are greater
         than 255 are added: LS (line separator, U+2028) and PS (paragraph sepa-
-        rator, U+2029).  Unicode character property support is not  needed  for
+        rator,  U+2029).   Unicode character property support is not needed for
         these characters to be recognized.
         It is possible to restrict \R to match only CR, LF, or CRLF (instead of
-        the complete set  of  Unicode  line  endings)  by  setting  the  option
+        the  complete  set  of  Unicode  line  endings)  by  setting the option
         PCRE_BSR_ANYCRLF either at compile time or when the pattern is matched.
         (BSR is an abbrevation for "backslash R".) This can be made the default
-        when  PCRE  is  built;  if this is the case, the other behaviour can be
+        when PCRE is built; if this is the case, the  other  behaviour  can  be
-        requested via the PCRE_BSR_UNICODE option.   It  is  also  possible  to
+        requested  via  the  PCRE_BSR_UNICODE  option.   It is also possible to
-        specify  these  settings  by  starting a pattern string with one of the
+        specify these settings by starting a pattern string  with  one  of  the
         following sequences:
           (*BSR_ANYCRLF)   CR, LF, or CRLF only
-Line 3318 
 BACKSLASH
+Line 3348 
 BACKSLASH
         These override the default and the options given to pcre_compile(), but
         they can be overridden by options given to pcre_exec(). Note that these
         special settings, which are not Perl-compatible, are recognized only at
-        the  very  start  of a pattern, and that they must be in upper case. If
+        the very start of a pattern, and that they must be in  upper  case.  If
-        more than one of them is present, the last one is  used.  They  can  be
+        more  than  one  of  them is present, the last one is used. They can be
-        combined  with  a  change of newline convention, for example, a pattern
+        combined with a change of newline convention, for  example,  a  pattern
         can start with:
           (*ANY)(*BSR_ANYCRLF)
-Line 3330 
 BACKSLASH
+Line 3360 
 BACKSLASH
     Unicode character properties
         When PCRE is built with Unicode character property support, three addi-
-        tional  escape sequences that match characters with specific properties
+        tional escape sequences that match characters with specific  properties
-        are available.  When not in UTF-8 mode, these sequences are  of  course
+        are  available.   When not in UTF-8 mode, these sequences are of course
-        limited  to  testing characters whose codepoints are less than 256, but
+        limited to testing characters whose codepoints are less than  256,  but
         they do work in this mode.  The extra escape sequences are:
           \p{xx}   a character with the xx property
           \P{xx}   a character without the xx property
           \X       an extended Unicode sequence
-        The property names represented by xx above are limited to  the  Unicode
+        The  property  names represented by xx above are limited to the Unicode
         script names, the general category properties, and "Any", which matches
         any character (including newline). Other properties such as "InMusical-
-        Symbols"  are  not  currently supported by PCRE. Note that \P{Any} does
+        Symbols" are not currently supported by PCRE. Note  that  \P{Any}  does
         not match any characters, so always causes a match failure.
         Sets of Unicode characters are defined as belonging to certain scripts.
-        A  character from one of these sets can be matched using a script name.
+        A character from one of these sets can be matched using a script  name.
         For example:
           \p{Greek}
           \P{Han}
-        Those that are not part of an identified script are lumped together  as
+        Those  that are not part of an identified script are lumped together as
         "Common". The current list of scripts is:
         Arabic,  Armenian,  Balinese,  Bengali,  Bopomofo,  Braille,  Buginese,
-        Buhid,  Canadian_Aboriginal,  Cherokee,  Common,   Coptic,   Cuneiform,
+        Buhid,   Canadian_Aboriginal,   Cherokee,  Common,  Coptic,  Cuneiform,
         Cypriot, Cyrillic, Deseret, Devanagari, Ethiopic, Georgian, Glagolitic,
-        Gothic, Greek, Gujarati, Gurmukhi, Han, Hangul, Hanunoo, Hebrew,  Hira-
+        Gothic,  Greek, Gujarati, Gurmukhi, Han, Hangul, Hanunoo, Hebrew, Hira-
-        gana,  Inherited,  Kannada,  Katakana,  Kharoshthi,  Khmer, Lao, Latin,
+        gana, Inherited, Kannada,  Katakana,  Kharoshthi,  Khmer,  Lao,  Latin,
         Limbu,  Linear_B,  Malayalam,  Mongolian,  Myanmar,  New_Tai_Lue,  Nko,
-        Ogham,  Old_Italic,  Old_Persian, Oriya, Osmanya, Phags_Pa, Phoenician,
+        Ogham, Old_Italic, Old_Persian, Oriya, Osmanya,  Phags_Pa,  Phoenician,
         Runic,  Shavian,  Sinhala,  Syloti_Nagri,  Syriac,  Tagalog,  Tagbanwa,
         Tai_Le, Tamil, Telugu, Thaana, Thai, Tibetan, Tifinagh, Ugaritic, Yi.
-        Each  character has exactly one general category property, specified by
+        Each character has exactly one general category property, specified  by
         a two-letter abbreviation. For compatibility with Perl, negation can be
-        specified  by  including a circumflex between the opening brace and the
+        specified by including a circumflex between the opening brace  and  the
         property name. For example, \p{^Lu} is the same as \P{Lu}.
         If only one letter is specified with \p or \P, it includes all the gen-
-        eral  category properties that start with that letter. In this case, in
+        eral category properties that start with that letter. In this case,  in
-        the absence of negation, the curly brackets in the escape sequence  are
+        the  absence of negation, the curly brackets in the escape sequence are
         optional; these two examples have the same effect:
           \p{L}
-Line 3424 
 BACKSLASH
+Line 3454 
 BACKSLASH
           Zp    Paragraph separator
           Zs    Space separator
-        The  special property L& is also supported: it matches a character that
+        The special property L& is also supported: it matches a character  that
-        has the Lu, Ll, or Lt property, in other words, a letter  that  is  not
+        has  the  Lu,  Ll, or Lt property, in other words, a letter that is not
         classified as a modifier or "other".
-        The  Cs  (Surrogate)  property  applies only to characters in the range
+        The Cs (Surrogate) property applies only to  characters  in  the  range
-        U+D800 to U+DFFF. Such characters are not valid in UTF-8  strings  (see
+        U+D800  to  U+DFFF. Such characters are not valid in UTF-8 strings (see
         RFC 3629) and so cannot be tested by PCRE, unless UTF-8 validity check-
-        ing has been turned off (see the discussion  of  PCRE_NO_UTF8_CHECK  in
+        ing  has  been  turned off (see the discussion of PCRE_NO_UTF8_CHECK in
         the pcreapi page).
-        The  long  synonyms  for  these  properties that Perl supports (such as
+        The long synonyms for these properties  that  Perl  supports  (such  as
-        \p{Letter}) are not supported by PCRE, nor is it  permitted  to  prefix
+        \p{Letter})  are  not  supported by PCRE, nor is it permitted to prefix
         any of these properties with "Is".
         No character that is in the Unicode table has the Cn (unassigned) prop-
         erty.  Instead, this property is assumed for any code point that is not
         in the Unicode table.
-        Specifying  caseless  matching  does not affect these escape sequences.
+        Specifying caseless matching does not affect  these  escape  sequences.
         For example, \p{Lu} always matches only upper case letters.
-        The \X escape matches any number of Unicode  characters  that  form  an
+        The  \X  escape  matches  any number of Unicode characters that form an
         extended Unicode sequence. \X is equivalent to
           (?>\PM\pM*)
-        That  is,  it matches a character without the "mark" property, followed
+        That is, it matches a character without the "mark"  property,  followed
-        by zero or more characters with the "mark"  property,  and  treats  the
+        by  zero  or  more  characters with the "mark" property, and treats the
-        sequence  as  an  atomic group (see below).  Characters with the "mark"
+        sequence as an atomic group (see below).  Characters  with  the  "mark"
-        property are typically accents that  affect  the  preceding  character.
+        property  are  typically  accents  that affect the preceding character.
-        None  of  them  have  codepoints less than 256, so in non-UTF-8 mode \X
+        None of them have codepoints less than 256, so  in  non-UTF-8  mode  \X
         matches any one character.
-        Matching characters by Unicode property is not fast, because  PCRE  has
+        Matching  characters  by Unicode property is not fast, because PCRE has
-        to  search  a  structure  that  contains data for over fifteen thousand
+        to search a structure that contains  data  for  over  fifteen  thousand
         characters. That is why the traditional escape sequences such as \d and
         \w do not use Unicode properties in PCRE.
     Resetting the match start
         The escape sequence \K, which is a Perl 5.10 feature, causes any previ-
-        ously matched characters not  to  be  included  in  the  final  matched
+        ously  matched  characters  not  to  be  included  in the final matched
         sequence. For example, the pattern:
           foo\Kbar
-        matches  "foobar",  but reports that it has matched "bar". This feature
+        matches "foobar", but reports that it has matched "bar".  This  feature
-        is similar to a lookbehind assertion (described  below).   However,  in
+        is  similar  to  a lookbehind assertion (described below).  However, in
-        this  case, the part of the subject before the real match does not have
+        this case, the part of the subject before the real match does not  have
-        to be of fixed length, as lookbehind assertions do. The use of \K  does
+        to  be of fixed length, as lookbehind assertions do. The use of \K does
-        not  interfere  with  the setting of captured substrings.  For example,
+        not interfere with the setting of captured  substrings.   For  example,
         when the pattern
           (foo)\Kbar
-Line 3483 
 BACKSLASH
+Line 3513 
 BACKSLASH
     Simple assertions
-        The final use of backslash is for certain simple assertions. An  asser-
+        The  final use of backslash is for certain simple assertions. An asser-
-        tion  specifies a condition that has to be met at a particular point in
+        tion specifies a condition that has to be met at a particular point  in
-        a match, without consuming any characters from the subject string.  The
+        a  match, without consuming any characters from the subject string. The
-        use  of subpatterns for more complicated assertions is described below.
+        use of subpatterns for more complicated assertions is described  below.
         The backslashed assertions are:
           \b     matches at a word boundary
-Line 3497 
 BACKSLASH
+Line 3527 
 BACKSLASH
           \z     matches only at the end of the subject
           \G     matches at the first matching position in the subject
-        These assertions may not appear in character classes (but note that  \b
+        These  assertions may not appear in character classes (but note that \b
         has a different meaning, namely the backspace character, inside a char-
         acter class).
-        A word boundary is a position in the subject string where  the  current
+        A  word  boundary is a position in the subject string where the current
-        character  and  the previous character do not both match \w or \W (i.e.
+        character and the previous character do not both match \w or  \W  (i.e.
-        one matches \w and the other matches \W), or the start or  end  of  the
+        one  matches  \w  and the other matches \W), or the start or end of the
         string if the first or last character matches \w, respectively.
-        The  \A,  \Z,  and \z assertions differ from the traditional circumflex
+        The \A, \Z, and \z assertions differ from  the  traditional  circumflex
         and dollar (described in the next section) in that they only ever match
-        at  the  very start and end of the subject string, whatever options are
+        at the very start and end of the subject string, whatever  options  are
-        set. Thus, they are independent of multiline mode. These  three  asser-
+        set.  Thus,  they are independent of multiline mode. These three asser-
         tions are not affected by the PCRE_NOTBOL or PCRE_NOTEOL options, which
-        affect only the behaviour of the circumflex and dollar  metacharacters.
+        affect  only the behaviour of the circumflex and dollar metacharacters.
-        However,  if the startoffset argument of pcre_exec() is non-zero, indi-
+        However, if the startoffset argument of pcre_exec() is non-zero,  indi-
         cating that matching is to start at a point other than the beginning of
-        the  subject,  \A  can never match. The difference between \Z and \z is
+        the subject, \A can never match. The difference between \Z  and  \z  is
         that \Z matches before a newline at the end of the string as well as at
         the very end, whereas \z matches only at the end.
-        The  \G assertion is true only when the current matching position is at
+        The \G assertion is true only when the current matching position is  at
-        the start point of the match, as specified by the startoffset  argument
+        the  start point of the match, as specified by the startoffset argument
-        of  pcre_exec().  It  differs  from \A when the value of startoffset is
+        of pcre_exec(). It differs from \A when the  value  of  startoffset  is
-        non-zero. By calling pcre_exec() multiple times with appropriate  argu-
+        non-zero.  By calling pcre_exec() multiple times with appropriate argu-
         ments, you can mimic Perl's /g option, and it is in this kind of imple-
         mentation where \G can be useful.
-        Note, however, that PCRE's interpretation of \G, as the  start  of  the
+        Note,  however,  that  PCRE's interpretation of \G, as the start of the
         current match, is subtly different from Perl's, which defines it as the
-        end of the previous match. In Perl, these can  be  different  when  the
+        end  of  the  previous  match. In Perl, these can be different when the
-        previously  matched  string was empty. Because PCRE does just one match
+        previously matched string was empty. Because PCRE does just  one  match
         at a time, it cannot reproduce this behaviour.
-        If all the alternatives of a pattern begin with \G, the  expression  is
+        If  all  the alternatives of a pattern begin with \G, the expression is
         anchored to the starting match position, and the "anchored" flag is set
         in the compiled regular expression.
-Line 3539 
 BACKSLASH
+Line 3569 
 BACKSLASH
  CIRCUMFLEX AND DOLLAR
         Outside a character class, in the default matching mode, the circumflex
-        character  is  an  assertion  that is true only if the current matching
+        character is an assertion that is true only  if  the  current  matching
-        point is at the start of the subject string. If the  startoffset  argu-
+        point  is  at the start of the subject string. If the startoffset argu-
-        ment  of  pcre_exec()  is  non-zero,  circumflex can never match if the
+        ment of pcre_exec() is non-zero, circumflex  can  never  match  if  the
-        PCRE_MULTILINE option is unset. Inside a  character  class,  circumflex
+        PCRE_MULTILINE  option  is  unset. Inside a character class, circumflex
         has an entirely different meaning (see below).
-        Circumflex  need  not be the first character of the pattern if a number
+        Circumflex need not be the first character of the pattern if  a  number
-        of alternatives are involved, but it should be the first thing in  each
+        of  alternatives are involved, but it should be the first thing in each
-        alternative  in  which  it appears if the pattern is ever to match that
+        alternative in which it appears if the pattern is ever  to  match  that
-        branch. If all possible alternatives start with a circumflex, that  is,
+        branch.  If all possible alternatives start with a circumflex, that is,
-        if  the  pattern  is constrained to match only at the start of the sub-
+        if the pattern is constrained to match only at the start  of  the  sub-
-        ject, it is said to be an "anchored" pattern.  (There  are  also  other
+        ject,  it  is  said  to be an "anchored" pattern. (There are also other
         constructs that can cause a pattern to be anchored.)
-        A  dollar  character  is  an assertion that is true only if the current
+        A dollar character is an assertion that is true  only  if  the  current
-        matching point is at the end of  the  subject  string,  or  immediately
+        matching  point  is  at  the  end of the subject string, or immediately
         before a newline at the end of the string (by default). Dollar need not
-        be the last character of the pattern if a number  of  alternatives  are
+        be  the  last  character of the pattern if a number of alternatives are
-        involved,  but  it  should  be  the last item in any branch in which it
+        involved, but it should be the last item in  any  branch  in  which  it
         appears. Dollar has no special meaning in a character class.
-        The meaning of dollar can be changed so that it  matches  only  at  the
+        The  meaning  of  dollar  can be changed so that it matches only at the
-        very  end  of  the string, by setting the PCRE_DOLLAR_ENDONLY option at
+        very end of the string, by setting the  PCRE_DOLLAR_ENDONLY  option  at
         compile time. This does not affect the \Z assertion.
         The meanings of the circumflex and dollar characters are changed if the
-        PCRE_MULTILINE  option  is  set.  When  this  is the case, a circumflex
+        PCRE_MULTILINE option is set. When  this  is  the  case,  a  circumflex
-        matches immediately after internal newlines as well as at the start  of
+        matches  immediately after internal newlines as well as at the start of
-        the  subject  string.  It  does not match after a newline that ends the
+        the subject string. It does not match after a  newline  that  ends  the
-        string. A dollar matches before any newlines in the string, as well  as
+        string.  A dollar matches before any newlines in the string, as well as
-        at  the very end, when PCRE_MULTILINE is set. When newline is specified
+        at the very end, when PCRE_MULTILINE is set. When newline is  specified
-        as the two-character sequence CRLF, isolated CR and  LF  characters  do
+        as  the  two-character  sequence CRLF, isolated CR and LF characters do
         not indicate newlines.
-        For  example, the pattern /^abc$/ matches the subject string "def\nabc"
+        For example, the pattern /^abc$/ matches the subject string  "def\nabc"
-        (where \n represents a newline) in multiline mode, but  not  otherwise.
+        (where  \n  represents a newline) in multiline mode, but not otherwise.
-        Consequently,  patterns  that  are anchored in single line mode because
+        Consequently, patterns that are anchored in single  line  mode  because
-        all branches start with ^ are not anchored in  multiline  mode,  and  a
+        all  branches  start  with  ^ are not anchored in multiline mode, and a
-        match  for  circumflex  is  possible  when  the startoffset argument of
+        match for circumflex is  possible  when  the  startoffset  argument  of
-        pcre_exec() is non-zero. The PCRE_DOLLAR_ENDONLY option is  ignored  if
+        pcre_exec()  is  non-zero. The PCRE_DOLLAR_ENDONLY option is ignored if
         PCRE_MULTILINE is set.
-        Note  that  the sequences \A, \Z, and \z can be used to match the start
+        Note that the sequences \A, \Z, and \z can be used to match  the  start
-        and end of the subject in both modes, and if all branches of a  pattern
+        and  end of the subject in both modes, and if all branches of a pattern
-        start  with  \A it is always anchored, whether or not PCRE_MULTILINE is
+        start with \A it is always anchored, whether or not  PCRE_MULTILINE  is
         set.
  FULL STOP (PERIOD, DOT)
         Outside a character class, a dot in the pattern matches any one charac-
-        ter  in  the subject string except (by default) a character that signi-
+        ter in the subject string except (by default) a character  that  signi-
-        fies the end of a line. In UTF-8 mode, the  matched  character  may  be
+        fies  the  end  of  a line. In UTF-8 mode, the matched character may be
         more than one byte long.
-        When  a line ending is defined as a single character, dot never matches
+        When a line ending is defined as a single character, dot never  matches
-        that character; when the two-character sequence CRLF is used, dot  does
+        that  character; when the two-character sequence CRLF is used, dot does
-        not  match  CR  if  it  is immediately followed by LF, but otherwise it
+        not match CR if it is immediately followed  by  LF,  but  otherwise  it
-        matches all characters (including isolated CRs and LFs). When any  Uni-
+        matches  all characters (including isolated CRs and LFs). When any Uni-
-        code  line endings are being recognized, dot does not match CR or LF or
+        code line endings are being recognized, dot does not match CR or LF  or
         any of the other line ending characters.
-        The behaviour of dot with regard to newlines can  be  changed.  If  the
+        The  behaviour  of  dot  with regard to newlines can be changed. If the
-        PCRE_DOTALL  option  is  set,  a dot matches any one character, without
+        PCRE_DOTALL option is set, a dot matches  any  one  character,  without
         exception. If the two-character sequence CRLF is present in the subject
         string, it takes two dots to match it.
-        The  handling of dot is entirely independent of the handling of circum-
+        The handling of dot is entirely independent of the handling of  circum-
-        flex and dollar, the only relationship being  that  they  both  involve
+        flex  and  dollar,  the  only relationship being that they both involve
         newlines. Dot has no special meaning in a character class.
  MATCHING A SINGLE BYTE
         Outside a character class, the escape sequence \C matches any one byte,
-        both in and out of UTF-8 mode. Unlike a  dot,  it  always  matches  any
+        both  in  and  out  of  UTF-8 mode. Unlike a dot, it always matches any
-        line-ending  characters.  The  feature  is provided in Perl in order to
+        line-ending characters. The feature is provided in  Perl  in  order  to
-        match individual bytes in UTF-8 mode. Because it breaks up UTF-8  char-
+        match  individual bytes in UTF-8 mode. Because it breaks up UTF-8 char-
-        acters  into individual bytes, what remains in the string may be a mal-
+        acters into individual bytes, what remains in the string may be a  mal-
-        formed UTF-8 string. For this reason, the \C escape  sequence  is  best
+        formed  UTF-8  string.  For this reason, the \C escape sequence is best
         avoided.
-        PCRE  does  not  allow \C to appear in lookbehind assertions (described
+        PCRE does not allow \C to appear in  lookbehind  assertions  (described
-        below), because in UTF-8 mode this would make it impossible  to  calcu-
+        below),  because  in UTF-8 mode this would make it impossible to calcu-
         late the length of the lookbehind.
-Line 3631 
 SQUARE BRACKETS AND CHARACTER CLASSES
+Line 3661 
 SQUARE BRACKETS AND CHARACTER CLASSES
         An opening square bracket introduces a character class, terminated by a
         closing square bracket. A closing square bracket on its own is not spe-
         cial. If a closing square bracket is required as a member of the class,
-        it should be the first data character in the class  (after  an  initial
+        it  should  be  the first data character in the class (after an initial
         circumflex, if present) or escaped with a backslash.
-        A  character  class matches a single character in the subject. In UTF-8
+        A character class matches a single character in the subject.  In  UTF-8
-        mode, the character may occupy more than one byte. A matched  character
+        mode,  the character may occupy more than one byte. A matched character
         must be in the set of characters defined by the class, unless the first
-        character in the class definition is a circumflex, in  which  case  the
+        character  in  the  class definition is a circumflex, in which case the
-        subject  character  must  not  be in the set defined by the class. If a
+        subject character must not be in the set defined by  the  class.  If  a
-        circumflex is actually required as a member of the class, ensure it  is
+        circumflex  is actually required as a member of the class, ensure it is
         not the first character, or escape it with a backslash.
-        For  example, the character class [aeiou] matches any lower case vowel,
+        For example, the character class [aeiou] matches any lower case  vowel,
-        while [^aeiou] matches any character that is not a  lower  case  vowel.
+        while  [^aeiou]  matches  any character that is not a lower case vowel.
         Note that a circumflex is just a convenient notation for specifying the
-        characters that are in the class by enumerating those that are  not.  A
+        characters  that  are in the class by enumerating those that are not. A
-        class  that starts with a circumflex is not an assertion: it still con-
+        class that starts with a circumflex is not an assertion: it still  con-
-        sumes a character from the subject string, and therefore  it  fails  if
+        sumes  a  character  from the subject string, and therefore it fails if
         the current pointer is at the end of the string.
-        In  UTF-8 mode, characters with values greater than 255 can be included
+        In UTF-8 mode, characters with values greater than 255 can be  included
-        in a class as a literal string of bytes, or by using the  \x{  escaping
+        in  a  class as a literal string of bytes, or by using the \x{ escaping
         mechanism.
-        When  caseless  matching  is set, any letters in a class represent both
+        When caseless matching is set, any letters in a  class  represent  both
-        their upper case and lower case versions, so for  example,  a  caseless
+        their  upper  case  and lower case versions, so for example, a caseless
-        [aeiou]  matches  "A"  as well as "a", and a caseless [^aeiou] does not
+        [aeiou] matches "A" as well as "a", and a caseless  [^aeiou]  does  not
-        match "A", whereas a caseful version would. In UTF-8 mode, PCRE  always
+        match  "A", whereas a caseful version would. In UTF-8 mode, PCRE always
-        understands  the  concept  of case for characters whose values are less
+        understands the concept of case for characters whose  values  are  less
-        than 128, so caseless matching is always possible. For characters  with
+        than  128, so caseless matching is always possible. For characters with
-        higher  values,  the  concept  of case is supported if PCRE is compiled
+        higher values, the concept of case is supported  if  PCRE  is  compiled
-        with Unicode property support, but not otherwise.  If you want  to  use
+        with  Unicode  property support, but not otherwise.  If you want to use
-        caseless  matching  for  characters 128 and above, you must ensure that
+        caseless matching for characters 128 and above, you  must  ensure  that
-        PCRE is compiled with Unicode property support as well  as  with  UTF-8
+        PCRE  is  compiled  with Unicode property support as well as with UTF-8
         support.
-        Characters  that  might  indicate  line breaks are never treated in any
+        Characters that might indicate line breaks are  never  treated  in  any
-        special way  when  matching  character  classes,  whatever  line-ending
+        special  way  when  matching  character  classes,  whatever line-ending
-        sequence  is  in  use,  and  whatever  setting  of  the PCRE_DOTALL and
+        sequence is in  use,  and  whatever  setting  of  the  PCRE_DOTALL  and
         PCRE_MULTILINE options is used. A class such as [^a] always matches one
         of these characters.
-        The  minus (hyphen) character can be used to specify a range of charac-
+        The minus (hyphen) character can be used to specify a range of  charac-
-        ters in a character  class.  For  example,  [d-m]  matches  any  letter
+        ters  in  a  character  class.  For  example,  [d-m] matches any letter
-        between  d  and  m,  inclusive.  If  a minus character is required in a
+        between d and m, inclusive. If a  minus  character  is  required  in  a
-        class, it must be escaped with a backslash  or  appear  in  a  position
+        class,  it  must  be  escaped  with a backslash or appear in a position
-        where  it cannot be interpreted as indicating a range, typically as the
+        where it cannot be interpreted as indicating a range, typically as  the
         first or last character in the class.
         It is not possible to have the literal character "]" as the end charac-
-        ter  of a range. A pattern such as [W-]46] is interpreted as a class of
+        ter of a range. A pattern such as [W-]46] is interpreted as a class  of
-        two characters ("W" and "-") followed by a literal string "46]", so  it
+        two  characters ("W" and "-") followed by a literal string "46]", so it
-        would  match  "W46]"  or  "-46]". However, if the "]" is escaped with a
+        would match "W46]" or "-46]". However, if the "]"  is  escaped  with  a
-        backslash it is interpreted as the end of range, so [W-\]46] is  inter-
+        backslash  it is interpreted as the end of range, so [W-\]46] is inter-
-        preted  as a class containing a range followed by two other characters.
+        preted as a class containing a range followed by two other  characters.
-        The octal or hexadecimal representation of "]" can also be used to  end
+        The  octal or hexadecimal representation of "]" can also be used to end
         a range.
-        Ranges  operate in the collating sequence of character values. They can
+        Ranges operate in the collating sequence of character values. They  can
-        also  be  used  for  characters  specified  numerically,  for   example
+        also   be  used  for  characters  specified  numerically,  for  example
-        [\000-\037].  In UTF-8 mode, ranges can include characters whose values
+        [\000-\037]. In UTF-8 mode, ranges can include characters whose  values
         are greater than 255, for example [\x{100}-\x{2ff}].
         If a range that includes letters is used when caseless matching is set,
         it matches the letters in either case. For example, [W-c] is equivalent
-        to [][\\^_`wxyzabc], matched caselessly,  and  in  non-UTF-8  mode,  if
+        to  [][\\^_`wxyzabc],  matched  caselessly,  and  in non-UTF-8 mode, if
-        character  tables  for  a French locale are in use, [\xc8-\xcb] matches
+        character tables for a French locale are in  use,  [\xc8-\xcb]  matches
-        accented E characters in both cases. In UTF-8 mode, PCRE  supports  the
+        accented  E  characters in both cases. In UTF-8 mode, PCRE supports the
-        concept  of  case for characters with values greater than 128 only when
+        concept of case for characters with values greater than 128  only  when
         it is compiled with Unicode property support.
-        The character types \d, \D, \p, \P, \s, \S, \w, and \W may also  appear
+        The  character types \d, \D, \p, \P, \s, \S, \w, and \W may also appear
-        in  a  character  class,  and add the characters that they match to the
+        in a character class, and add the characters that  they  match  to  the
         class. For example, [\dABCDEF] matches any hexadecimal digit. A circum-
-        flex  can  conveniently  be used with the upper case character types to
+        flex can conveniently be used with the upper case  character  types  to
-        specify a more restricted set of characters  than  the  matching  lower
+        specify  a  more  restricted  set of characters than the matching lower
-        case  type.  For example, the class [^\W_] matches any letter or digit,
+        case type. For example, the class [^\W_] matches any letter  or  digit,
         but not underscore.
-        The only metacharacters that are recognized in  character  classes  are
+        The  only  metacharacters  that are recognized in character classes are
-        backslash,  hyphen  (only  where  it can be interpreted as specifying a
+        backslash, hyphen (only where it can be  interpreted  as  specifying  a
-        range), circumflex (only at the start), opening  square  bracket  (only
+        range),  circumflex  (only  at the start), opening square bracket (only
-        when  it can be interpreted as introducing a POSIX class name - see the
+        when it can be interpreted as introducing a POSIX class name - see  the
-        next section), and the terminating  closing  square  bracket.  However,
+        next  section),  and  the  terminating closing square bracket. However,
         escaping other non-alphanumeric characters does no harm.
  POSIX CHARACTER CLASSES
         Perl supports the POSIX notation for character classes. This uses names
-        enclosed by [: and :] within the enclosing square brackets.  PCRE  also
+        enclosed  by  [: and :] within the enclosing square brackets. PCRE also
         supports this notation. For example,
           [01[:alpha:]%]
-Line 3743 
 POSIX CHARACTER CLASSES
+Line 3773 
 POSIX CHARACTER CLASSES
           word     "word" characters (same as \w)
           xdigit   hexadecimal digits
-        The "space" characters are HT (9), LF (10), VT (11), FF (12), CR  (13),
+        The  "space" characters are HT (9), LF (10), VT (11), FF (12), CR (13),
-        and  space  (32). Notice that this list includes the VT character (code
+        and space (32). Notice that this list includes the VT  character  (code
 ). This makes "space" different to \s, which does not include VT (for
         Perl compatibility).
-        The  name  "word"  is  a Perl extension, and "blank" is a GNU extension
+        The name "word" is a Perl extension, and "blank"  is  a  GNU  extension
-        from Perl 5.8. Another Perl extension is negation, which  is  indicated
+        from  Perl  5.8. Another Perl extension is negation, which is indicated
         by a ^ character after the colon. For example,
           [12[:^digit:]]
-        matches  "1", "2", or any non-digit. PCRE (and Perl) also recognize the
+        matches "1", "2", or any non-digit. PCRE (and Perl) also recognize  the
         POSIX syntax [.ch.] and [=ch=] where "ch" is a "collating element", but
         these are not supported, and an error is given if they are encountered.
-Line 3774 
 VERTICAL BAR
+Line 3804 
 VERTICAL BAR
         string). The matching process tries each alternative in turn, from left
         to  right, and the first one that succeeds is used. If the alternatives
         are within a subpattern (defined below), "succeeds" means matching  the
-        rest  of the main pattern as well as the alternative in the subpattern.
+        rest of the main pattern as well as the alternative in the subpattern.
  INTERNAL OPTION SETTING
-        The settings of the  PCRE_CASELESS,  PCRE_MULTILINE,  PCRE_DOTALL,  and
+        The  settings  of  the  PCRE_CASELESS, PCRE_MULTILINE, PCRE_DOTALL, and
-        PCRE_EXTENDED  options  (which are Perl-compatible) can be changed from
+        PCRE_EXTENDED options (which are Perl-compatible) can be  changed  from
-        within the pattern by  a  sequence  of  Perl  option  letters  enclosed
+        within  the  pattern  by  a  sequence  of  Perl option letters enclosed
         between "(?" and ")".  The option letters are
           i  for PCRE_CASELESS
-Line 3791 
 INTERNAL OPTION SETTING
+Line 3821 
 INTERNAL OPTION SETTING
         For example, (?im) sets caseless, multiline matching. It is also possi-
         ble to unset these options by preceding the letter with a hyphen, and a
-        combined  setting and unsetting such as (?im-sx), which sets PCRE_CASE-
+        combined setting and unsetting such as (?im-sx), which sets  PCRE_CASE-
-        LESS and PCRE_MULTILINE while unsetting PCRE_DOTALL and  PCRE_EXTENDED,
+        LESS  and PCRE_MULTILINE while unsetting PCRE_DOTALL and PCRE_EXTENDED,
-        is  also  permitted.  If  a  letter  appears  both before and after the
+        is also permitted. If a  letter  appears  both  before  and  after  the
         hyphen, the option is unset.
-        The PCRE-specific options PCRE_DUPNAMES, PCRE_UNGREEDY, and  PCRE_EXTRA
+        The  PCRE-specific options PCRE_DUPNAMES, PCRE_UNGREEDY, and PCRE_EXTRA
-        can  be changed in the same way as the Perl-compatible options by using
+        can be changed in the same way as the Perl-compatible options by  using
         the characters J, U and X respectively.
-        When an option change occurs at top level (that is, not inside  subpat-
+        When  an option change occurs at top level (that is, not inside subpat-
-        tern  parentheses),  the change applies to the remainder of the pattern
+        tern parentheses), the change applies to the remainder of  the  pattern
         that follows.  If the change is placed right at the start of a pattern,
         PCRE extracts it into the global options (and it will therefore show up
         in data extracted by the pcre_fullinfo() function).
-        An option change within a subpattern (see below for  a  description  of
+        An  option  change  within a subpattern (see below for a description of
         subpatterns) affects only that part of the current pattern that follows
         it, so
           (a(?i)b)c
         matches abc and aBc and no other strings (assuming PCRE_CASELESS is not
-        used).   By  this means, options can be made to have different settings
+        used).  By this means, options can be made to have  different  settings
-        in different parts of the pattern. Any changes made in one  alternative
+        in  different parts of the pattern. Any changes made in one alternative
-        do  carry  on  into subsequent branches within the same subpattern. For
+        do carry on into subsequent branches within the  same  subpattern.  For
         example,
           (a(?i)b|c)
-        matches "ab", "aB", "c", and "C", even though  when  matching  "C"  the
+        matches  "ab",  "aB",  "c",  and "C", even though when matching "C" the
-        first  branch  is  abandoned before the option setting. This is because
+        first branch is abandoned before the option setting.  This  is  because
-        the effects of option settings happen at compile time. There  would  be
+        the  effects  of option settings happen at compile time. There would be
         some very weird behaviour otherwise.
-        Note:  There  are  other  PCRE-specific  options that can be set by the
+        Note: There are other PCRE-specific options that  can  be  set  by  the
-        application when the compile or match functions  are  called.  In  some
+        application  when  the  compile  or match functions are called. In some
-        cases  the  pattern  can  contain special leading sequences to override
+        cases the pattern can contain special  leading  sequences  to  override
-        what the application has set or what has been  defaulted.  Details  are
+        what  the  application  has set or what has been defaulted. Details are
         given in the section entitled "Newline sequences" above.
-Line 3841 
 SUBPATTERNS
+Line 3871 
 SUBPATTERNS
           cat(aract|erpillar|)
-        matches one of the words "cat", "cataract", or  "caterpillar".  Without
+        matches  one  of the words "cat", "cataract", or "caterpillar". Without
-        the  parentheses,  it  would  match  "cataract", "erpillar" or an empty
+        the parentheses, it would match  "cataract",  "erpillar"  or  an  empty
         string.
-. It sets up the subpattern as  a  capturing  subpattern.  This  means
+.  It  sets  up  the  subpattern as a capturing subpattern. This means
-        that,  when  the  whole  pattern  matches,  that portion of the subject
+        that, when the whole pattern  matches,  that  portion  of  the  subject
         string that matched the subpattern is passed back to the caller via the
-        ovector  argument  of pcre_exec(). Opening parentheses are counted from
+        ovector argument of pcre_exec(). Opening parentheses are  counted  from
-        left to right (starting from 1) to obtain  numbers  for  the  capturing
+        left  to  right  (starting  from 1) to obtain numbers for the capturing
         subpatterns.
-        For  example,  if the string "the red king" is matched against the pat-
+        For example, if the string "the red king" is matched against  the  pat-
         tern
           the ((red|white) (king|queen))
-Line 3860 
 SUBPATTERNS
+Line 3890 
 SUBPATTERNS
         the captured substrings are "red king", "red", and "king", and are num-
         bered 1, 2, and 3, respectively.
-        The  fact  that  plain  parentheses  fulfil two functions is not always
+        The fact that plain parentheses fulfil  two  functions  is  not  always
-        helpful.  There are often times when a grouping subpattern is  required
+        helpful.   There are often times when a grouping subpattern is required
-        without  a capturing requirement. If an opening parenthesis is followed
+        without a capturing requirement. If an opening parenthesis is  followed
-        by a question mark and a colon, the subpattern does not do any  captur-
+        by  a question mark and a colon, the subpattern does not do any captur-
-        ing,  and  is  not  counted when computing the number of any subsequent
+        ing, and is not counted when computing the  number  of  any  subsequent
-        capturing subpatterns. For example, if the string "the white queen"  is
+        capturing  subpatterns. For example, if the string "the white queen" is
         matched against the pattern
           the ((?:red|white) (king|queen))
-Line 3873 
 SUBPATTERNS
+Line 3903 
 SUBPATTERNS
         the captured substrings are "white queen" and "queen", and are numbered
 and 2. The maximum number of capturing subpatterns is 65535.
-        As a convenient shorthand, if any option settings are required  at  the
+        As  a  convenient shorthand, if any option settings are required at the
-        start  of  a  non-capturing  subpattern,  the option letters may appear
+        start of a non-capturing subpattern,  the  option  letters  may  appear
         between the "?" and the ":". Thus the two patterns
           (?i:saturday|sunday)
           (?:(?i)saturday|sunday)
         match exactly the same set of strings. Because alternative branches are
-        tried  from  left  to right, and options are not reset until the end of
+        tried from left to right, and options are not reset until  the  end  of
-        the subpattern is reached, an option setting in one branch does  affect
+        the  subpattern is reached, an option setting in one branch does affect
-        subsequent  branches,  so  the above patterns match "SUNDAY" as well as
+        subsequent branches, so the above patterns match "SUNDAY"  as  well  as
         "Saturday".
  DUPLICATE SUBPATTERN NUMBERS
         Perl 5.10 introduced a feature whereby each alternative in a subpattern
-        uses  the same numbers for its capturing parentheses. Such a subpattern
+        uses the same numbers for its capturing parentheses. Such a  subpattern
-        starts with (?| and is itself a non-capturing subpattern. For  example,
+        starts  with (?| and is itself a non-capturing subpattern. For example,
         consider this pattern:
           (?|(Sat)ur|(Sun))day
-        Because  the two alternatives are inside a (?| group, both sets of cap-
+        Because the two alternatives are inside a (?| group, both sets of  cap-
-        turing parentheses are numbered one. Thus, when  the  pattern  matches,
+        turing  parentheses  are  numbered one. Thus, when the pattern matches,
-        you  can  look  at captured substring number one, whichever alternative
+        you can look at captured substring number  one,  whichever  alternative
-        matched. This construct is useful when you want to  capture  part,  but
+        matched.  This  construct  is useful when you want to capture part, but
         not all, of one of a number of alternatives. Inside a (?| group, paren-
-        theses are numbered as usual, but the number is reset at the  start  of
+        theses  are  numbered as usual, but the number is reset at the start of
-        each  branch. The numbers of any capturing buffers that follow the sub-
+        each branch. The numbers of any capturing buffers that follow the  sub-
-        pattern start after the highest number used in any branch. The  follow-
+        pattern  start after the highest number used in any branch. The follow-
-        ing  example  is taken from the Perl documentation.  The numbers under-
+        ing example is taken from the Perl documentation.  The  numbers  under-
         neath show in which buffer the captured content will be stored.
           # before  ---------------branch-reset----------- after
           / ( a )  (?| x ( y ) z | (p (q) r) | (t) u (v) ) ( z ) /x
           # 1            2         2  3        2     3     4
-        A backreference or a recursive call to  a  numbered  subpattern  always
+        A  backreference  or  a  recursive call to a numbered subpattern always
         refers to the first one in the pattern with the given number.
-        An  alternative approach to using this "branch reset" feature is to use
+        An alternative approach to using this "branch reset" feature is to  use
         duplicate named subpatterns, as described in the next section.
  NAMED SUBPATTERNS
-        Identifying capturing parentheses by number is simple, but  it  can  be
+        Identifying  capturing  parentheses  by number is simple, but it can be
-        very  hard  to keep track of the numbers in complicated regular expres-
+        very hard to keep track of the numbers in complicated  regular  expres-
-        sions. Furthermore, if an  expression  is  modified,  the  numbers  may
+        sions.  Furthermore,  if  an  expression  is  modified, the numbers may
-        change.  To help with this difficulty, PCRE supports the naming of sub-
+        change. To help with this difficulty, PCRE supports the naming of  sub-
         patterns. This feature was not added to Perl until release 5.10. Python
-        had  the  feature earlier, and PCRE introduced it at release 4.0, using
+        had the feature earlier, and PCRE introduced it at release  4.0,  using
-        the Python syntax. PCRE now supports both the Perl and the Python  syn-
+        the  Python syntax. PCRE now supports both the Perl and the Python syn-
         tax.
-        In  PCRE,  a subpattern can be named in one of three ways: (?<name>...)
+        In PCRE, a subpattern can be named in one of three  ways:  (?<name>...)
-        or (?'name'...) as in Perl, or (?P<name>...) as in  Python.  References
+        or  (?'name'...)  as in Perl, or (?P<name>...) as in Python. References
         to capturing parentheses from other parts of the pattern, such as back-
-        references, recursion, and conditions, can be made by name as  well  as
+        references,  recursion,  and conditions, can be made by name as well as
         by number.
-        Names  consist  of  up  to  32 alphanumeric characters and underscores.
+        Names consist of up to  32  alphanumeric  characters  and  underscores.
-        Named capturing parentheses are still  allocated  numbers  as  well  as
+        Named  capturing  parentheses  are  still  allocated numbers as well as
-        names,  exactly as if the names were not present. The PCRE API provides
+        names, exactly as if the names were not present. The PCRE API  provides
         function calls for extracting the name-to-number translation table from
         a compiled pattern. There is also a convenience function for extracting
         a captured substring by name.
-        By default, a name must be unique within a pattern, but it is  possible
+        By  default, a name must be unique within a pattern, but it is possible
         to relax this constraint by setting the PCRE_DUPNAMES option at compile
-        time. This can be useful for patterns where only one  instance  of  the
+        time.  This  can  be useful for patterns where only one instance of the
-        named  parentheses  can  match. Suppose you want to match the name of a
+        named parentheses can match. Suppose you want to match the  name  of  a
-        weekday, either as a 3-letter abbreviation or as the full name, and  in
+        weekday,  either as a 3-letter abbreviation or as the full name, and in
         both cases you want to extract the abbreviation. This pattern (ignoring
         the line breaks) does the job:
-Line 3956 
 NAMED SUBPATTERNS
+Line 3986 
 NAMED SUBPATTERNS
           (?<DN>Thu)(?:rsday)?|
           (?<DN>Sat)(?:urday)?
-        There are five capturing substrings, but only one is ever set  after  a
+        There  are  five capturing substrings, but only one is ever set after a
         match.  (An alternative way of solving this problem is to use a "branch
         reset" subpattern, as described in the previous section.)
-        The convenience function for extracting the data by  name  returns  the
+        The  convenience  function  for extracting the data by name returns the
-        substring  for  the first (and in this example, the only) subpattern of
+        substring for the first (and in this example, the only)  subpattern  of
-        that name that matched. This saves searching  to  find  which  numbered
+        that  name  that  matched.  This saves searching to find which numbered
-        subpattern  it  was. If you make a reference to a non-unique named sub-
+        subpattern it was. If you make a reference to a non-unique  named  sub-
-        pattern from elsewhere in the pattern, the one that corresponds to  the
+        pattern  from elsewhere in the pattern, the one that corresponds to the
-        lowest  number  is used. For further details of the interfaces for han-
+        lowest number is used. For further details of the interfaces  for  han-
         dling named subpatterns, see the pcreapi documentation.
+        Warning: You cannot use different names to distinguish between two sub-
+        patterns with the same number (see the previous section)  because  PCRE
+        uses only the numbers when matching.
  REPETITION
-        Repetition is specified by quantifiers, which can  follow  any  of  the
+        Repetition  is  specified  by  quantifiers, which can follow any of the
         following items:
           a literal data character
-Line 3984 
 REPETITION
+Line 4018 
 REPETITION
           a back reference (see next section)
           a parenthesized subpattern (unless it is an assertion)
-        The  general repetition quantifier specifies a minimum and maximum num-
+        The general repetition quantifier specifies a minimum and maximum  num-
-        ber of permitted matches, by giving the two numbers in  curly  brackets
+        ber  of  permitted matches, by giving the two numbers in curly brackets
-        (braces),  separated  by  a comma. The numbers must be less than 65536,
+        (braces), separated by a comma. The numbers must be  less  than  65536,
         and the first must be less than or equal to the second. For example:
           z{2,4}
-        matches "zz", "zzz", or "zzzz". A closing brace on its  own  is  not  a
+        matches  "zz",  "zzz",  or  "zzzz". A closing brace on its own is not a
-        special  character.  If  the second number is omitted, but the comma is
+        special character. If the second number is omitted, but  the  comma  is
-        present, there is no upper limit; if the second number  and  the  comma
+        present,  there  is  no upper limit; if the second number and the comma
-        are  both omitted, the quantifier specifies an exact number of required
+        are both omitted, the quantifier specifies an exact number of  required
         matches. Thus
           [aeiou]{3,}
-Line 4003 
 REPETITION
+Line 4037 
 REPETITION
           \d{8}
-        matches exactly 8 digits. An opening curly bracket that  appears  in  a
+        matches  exactly  8  digits. An opening curly bracket that appears in a
-        position  where a quantifier is not allowed, or one that does not match
+        position where a quantifier is not allowed, or one that does not  match
-        the syntax of a quantifier, is taken as a literal character. For  exam-
+        the  syntax of a quantifier, is taken as a literal character. For exam-
         ple, {,6} is not a quantifier, but a literal string of four characters.
         In UTF-8 mode, quantifiers apply to UTF-8  characters  rather  than  to
-Line 4149 
 ATOMIC GROUPING AND POSSESSIVE QUANTIFIE
+Line 4183 
 ATOMIC GROUPING AND POSSESSIVE QUANTIFIE
           (?>\d+)foo
-        This  kind  of  parenthesis "locks up" the  part of the pattern it con-
+        This kind of parenthesis "locks up" the  part of the  pattern  it  con-
-        tains once it has matched, and a failure further into  the  pattern  is
+        tains  once  it  has matched, and a failure further into the pattern is
-        prevented  from  backtracking into it. Backtracking past it to previous
+        prevented from backtracking into it. Backtracking past it  to  previous
         items, however, works as normal.
-        An alternative description is that a subpattern of  this  type  matches
+        An  alternative  description  is that a subpattern of this type matches
-        the  string  of  characters  that an identical standalone pattern would
+        the string of characters that an  identical  standalone  pattern  would
         match, if anchored at the current point in the subject string.
         Atomic grouping subpatterns are not capturing subpatterns. Simple cases
         such as the above example can be thought of as a maximizing repeat that
-        must swallow everything it can. So, while both \d+ and  \d+?  are  pre-
+        must  swallow  everything  it can. So, while both \d+ and \d+? are pre-
-        pared  to  adjust  the number of digits they match in order to make the
+        pared to adjust the number of digits they match in order  to  make  the
         rest of the pattern match, (?>\d+) can only match an entire sequence of
         digits.
-        Atomic  groups in general can of course contain arbitrarily complicated
+        Atomic groups in general can of course contain arbitrarily  complicated
-        subpatterns, and can be nested. However, when  the  subpattern  for  an
+        subpatterns,  and  can  be  nested. However, when the subpattern for an
         atomic group is just a single repeated item, as in the example above, a
-        simpler notation, called a "possessive quantifier" can  be  used.  This
+        simpler  notation,  called  a "possessive quantifier" can be used. This
-        consists  of  an  additional  + character following a quantifier. Using
+        consists of an additional + character  following  a  quantifier.  Using
         this notation, the previous example can be rewritten as
           \d++foo
-Line 4179 
 ATOMIC GROUPING AND POSSESSIVE QUANTIFIE
+Line 4213 
 ATOMIC GROUPING AND POSSESSIVE QUANTIFIE
           (abc|xyz){2,3}+
-        Possessive   quantifiers   are   always  greedy;  the  setting  of  the
+        Possessive  quantifiers  are  always  greedy;  the   setting   of   the
         PCRE_UNGREEDY option is ignored. They are a convenient notation for the
-        simpler  forms  of atomic group. However, there is no difference in the
+        simpler forms of atomic group. However, there is no difference  in  the
-        meaning of a possessive quantifier and  the  equivalent  atomic  group,
+        meaning  of  a  possessive  quantifier and the equivalent atomic group,
-        though  there  may  be a performance difference; possessive quantifiers
+        though there may be a performance  difference;  possessive  quantifiers
         should be slightly faster.
-        The possessive quantifier syntax is an extension to the Perl  5.8  syn-
+        The  possessive  quantifier syntax is an extension to the Perl 5.8 syn-
-        tax.   Jeffrey  Friedl  originated the idea (and the name) in the first
+        tax.  Jeffrey Friedl originated the idea (and the name)  in  the  first
         edition of his book. Mike McCloskey liked it, so implemented it when he
-        built  Sun's Java package, and PCRE copied it from there. It ultimately
+        built Sun's Java package, and PCRE copied it from there. It  ultimately
         found its way into Perl at release 5.10.
         PCRE has an optimization that automatically "possessifies" certain sim-
-        ple  pattern  constructs.  For  example, the sequence A+B is treated as
+        ple pattern constructs. For example, the sequence  A+B  is  treated  as
-        A++B because there is no point in backtracking into a sequence  of  A's
+        A++B  because  there is no point in backtracking into a sequence of A's
         when B must follow.
-        When  a  pattern  contains an unlimited repeat inside a subpattern that
+        When a pattern contains an unlimited repeat inside  a  subpattern  that
-        can itself be repeated an unlimited number of  times,  the  use  of  an
+        can  itself  be  repeated  an  unlimited number of times, the use of an
-        atomic  group  is  the  only way to avoid some failing matches taking a
+        atomic group is the only way to avoid some  failing  matches  taking  a
         very long time indeed. The pattern
           (\D+|<\d+>)*[!?]
-        matches an unlimited number of substrings that either consist  of  non-
+        matches  an  unlimited number of substrings that either consist of non-
-        digits,  or  digits  enclosed in <>, followed by either ! or ?. When it
+        digits, or digits enclosed in <>, followed by either ! or  ?.  When  it
         matches, it runs quickly. However, if it is applied to
           aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
-        it takes a long time before reporting  failure.  This  is  because  the
+        it  takes  a  long  time  before reporting failure. This is because the
-        string  can be divided between the internal \D+ repeat and the external
+        string can be divided between the internal \D+ repeat and the  external
-        * repeat in a large number of ways, and all  have  to  be  tried.  (The
+        *  repeat  in  a  large  number of ways, and all have to be tried. (The
-        example  uses  [!?]  rather than a single character at the end, because
+        example uses [!?] rather than a single character at  the  end,  because
-        both PCRE and Perl have an optimization that allows  for  fast  failure
+        both  PCRE  and  Perl have an optimization that allows for fast failure
-        when  a single character is used. They remember the last single charac-
+        when a single character is used. They remember the last single  charac-
-        ter that is required for a match, and fail early if it is  not  present
+        ter  that  is required for a match, and fail early if it is not present
-        in  the  string.)  If  the pattern is changed so that it uses an atomic
+        in the string.) If the pattern is changed so that  it  uses  an  atomic
         group, like this:
           ((?>\D+)|<\d+>)*[!?]
-        sequences of non-digits cannot be broken, and failure happens  quickly.
+        sequences of non-digits cannot be broken, and failure happens quickly.
  BACK REFERENCES
-Line 4985 
 AUTHOR
+Line 5019 
 AUTHOR
  REVISION
-        Last updated: 19 April 2008
+        Last updated: 08 March 2009
-        Copyright (c) 1997-2008 University of Cambridge.
+        Copyright (c) 1997-2009 University of Cambridge.
  ------------------------------------------------------------------------------
-Line 5514 
 MULTI-SEGMENT MATCHING WITH pcre_dfa_exe
+Line 5548 
 MULTI-SEGMENT MATCHING WITH pcre_dfa_exe
 : dogsbody
 : dog
-        The  pattern matches the words "dog" or "dogsbody". When the subject is
+        The pattern matches the words "dog" or "dogsbody". When the subject  is
-        presented in several parts ("do" and "gsb" being  the  first  two)  the
+        presented  in  several  parts  ("do" and "gsb" being the first two) the
-        match  stops  when "dog" has been found, and it is not possible to con-
+        match stops when "dog" has been found, and it is not possible  to  con-
-        tinue. On the other hand,  if  "dogsbody"  is  presented  as  a  single
+        tinue.  On  the  other  hand,  if  "dogsbody"  is presented as a single
         string, both matches are found.
-        Because  of  this  phenomenon,  it does not usually make sense to end a
+        Because of this phenomenon, it does not usually make  sense  to  end  a
         pattern that is going to be matched in this way with a variable repeat.
 . Patterns that contain alternatives at the top level which do not all
-Line 5867 
 DESCRIPTION
+Line 5901 
 DESCRIPTION
         command  for  linking  an application that uses them. Because the POSIX
         functions call the native ones, it is also necessary to add -lpcre.
-        I have implemented only those option bits that can be reasonably mapped
+        I have implemented only those POSIX option bits that can be  reasonably
-        to PCRE native options. In addition, the option REG_EXTENDED is defined
+        mapped  to PCRE native options. In addition, the option REG_EXTENDED is
-        with the value zero. This has no effect, but since  programs  that  are
+        defined with the value zero. This has no  effect,  but  since  programs
-        written  to  the  POSIX interface often use it, this makes it easier to
+        that  are  written  to  the POSIX interface often use it, this makes it
-        slot in PCRE as a replacement library. Other POSIX options are not even
+        easier to slot in PCRE as a replacement library.  Other  POSIX  options
-        defined.
+        are not even defined.
         When  PCRE  is  called  via these functions, it is only the API that is
         POSIX-like in style. The syntax and semantics of  the  regular  expres-
-Line 5952 
 COMPILING A PATTERN
+Line 5986 
 COMPILING A PATTERN
  MATCHING NEWLINE CHARACTERS
         This area is not simple, because POSIX and Perl take different views of
-        things.  It is not possible to get PCRE to obey  POSIX  semantics,  but
+        things.   It  is  not possible to get PCRE to obey POSIX semantics, but
-        then  PCRE was never intended to be a POSIX engine. The following table
+        then PCRE was never intended to be a POSIX engine. The following  table
-        lists the different possibilities for matching  newline  characters  in
+        lists  the  different  possibilities for matching newline characters in
         PCRE:
                                   Default   Change with
-Line 5976 
 MATCHING NEWLINE CHARACTERS
+Line 6010 
 MATCHING NEWLINE CHARACTERS
           ^ matches \n in middle     no     REG_NEWLINE
         PCRE's behaviour is the same as Perl's, except that there is no equiva-
-        lent for PCRE_DOLLAR_ENDONLY in Perl. In both PCRE and Perl,  there  is
+        lent  for  PCRE_DOLLAR_ENDONLY in Perl. In both PCRE and Perl, there is
         no way to stop newline from matching [^a].
-        The   default  POSIX  newline  handling  can  be  obtained  by  setting
+        The  default  POSIX  newline  handling  can  be  obtained  by   setting
-        PCRE_DOTALL and PCRE_DOLLAR_ENDONLY, but there is no way to  make  PCRE
+        PCRE_DOTALL  and  PCRE_DOLLAR_ENDONLY, but there is no way to make PCRE
         behave exactly as for the REG_NEWLINE action.
  MATCHING A PATTERN
-        The  function  regexec()  is  called  to  match a compiled pattern preg
+        The function regexec() is called  to  match  a  compiled  pattern  preg
-        against a given string, which is by default terminated by a  zero  byte
+        against  a  given string, which is by default terminated by a zero byte
-        (but  see  REG_STARTEND below), subject to the options in eflags. These
+        (but see REG_STARTEND below), subject to the options in  eflags.  These
         can be:
           REG_NOTBOL
-Line 5996 
 MATCHING A PATTERN
+Line 6030 
 MATCHING A PATTERN
         The PCRE_NOTBOL option is set when calling the underlying PCRE matching
         function.
+          REG_NOTEMPTY
+        The PCRE_NOTEMPTY option is set when calling the underlying PCRE match-
+        ing function. Note that REG_NOTEMPTY is not part of the POSIX standard.
+        However, setting this option can give more POSIX-like behaviour in some
+        situations.
           REG_NOTEOL
         The PCRE_NOTEOL option is set when calling the underlying PCRE matching
-Line 6058 
 AUTHOR
+Line 6099 
 AUTHOR
  REVISION
-        Last updated: 05 April 2008
+        Last updated: 11 March 2009
-        Copyright (c) 1997-2008 University of Cambridge.
+        Copyright (c) 1997-2009 University of Cambridge.
  ------------------------------------------------------------------------------
-Line 6163 
 MATCHING INTERFACE
+Line 6204 
 MATCHING INTERFACE
         need    more,    consider    using    the    more   general   interface
         pcrecpp::RE::DoMatch. See pcrecpp.h for the signature for DoMatch.
+        NOTE: Do not use no_arg, which is used internally to mark the end of  a
+        list  of optional arguments, as a placeholder for missing arguments, as
+        this can lead to segfaults.
  QUOTING METACHARACTERS
-Line 6396 
 AUTHOR
+Line 6441 
 AUTHOR
  REVISION
-        Last updated: 12 November 2007
+        Last updated: 17 March 2009
  ------------------------------------------------------------------------------

 Legend:



Removed from v.371
 


changed lines


 
Added in v.392
 Legend:



Removed from v.371
 


changed lines


 
Added in v.392
-Removed from v.371
+Added in v.392

	ViewVC Help
Powered by ViewVC 1.1.5