ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 152 by ph10, Tue Apr 17 15:55:53 2007 UTC revision 641 by ph10, Mon Jul 25 16:56:54 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.1 12-Mar-07  Version 8.13 30-Apr-2011
5    ------------------------
7    1.  The Unicode data tables have been updated to Unicode 6.0.0.
9    2.  Two minor typos in pcre_internal.h have been fixed.
11    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
12        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
13        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
15    4.  There were a number of related bugs in the code for matching backrefences
16        caselessly in UTF-8 mode when codes for the characters concerned were
17        different numbers of bytes. For example, U+023A and U+2C65 are an upper
18        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
19        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
20        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
21        2-byte code at the end of the subject (it thought there wasn't enough data
22        left).
24    5.  Comprehensive information about what went wrong is now returned by
25        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
26        as the output vector has at least 2 elements. The offset of the start of
27        the failing character and a reason code are placed in the vector.
29    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
30        now returned is for the first byte of the failing character, instead of the
31        last byte inspected. This is an incompatible change, but I hope it is small
32        enough not to be a problem. It makes the returned offset consistent with
33        pcre_exec() and pcre_dfa_exec().
35    7.  pcretest now gives a text phrase as well as the error number when
36        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
37        failure, the offset and reason code are output.
39    8.  When \R was used with a maximizing quantifier it failed to skip backwards
40        over a \r\n pair if the subsequent match failed. Instead, it just skipped
41        back over a single character (\n). This seems wrong (because it treated the
42        two characters as a single entity when going forwards), conflicts with the
43        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
44        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
45        has been changed.
47    9.  Some internal refactoring has changed the processing so that the handling
48        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
49        time (the PCRE_DOTALL option was changed this way some time ago: version
50        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
51        which was always a bit of a fudge. It also means that there is one less
52        argument for the match() function, which reduces its stack requirements
53        slightly. This change also fixes an incompatibility with Perl: the pattern
54        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
56    10. More internal refactoring has drastically reduced the number of recursive
57        calls to match() for possessively repeated groups such as (abc)++ when
58        using pcre_exec().
60    11. While implementing 10, a number of bugs in the handling of groups were
61        discovered and fixed:
63        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
64        (a|)*(?1) gave a compile-time internal error.
65        ((a|)+)+  did not notice that the outer group could match an empty string.
66        (^a|^)+   was not marked as anchored.
67        (.*a|.*)+ was not marked as matching at start or after a newline.
69    12. Yet more internal refactoring has removed another argument from the match()
70        function. Special calls to this function are now indicated by setting a
71        value in a variable in the "match data" data block.
73    13. Be more explicit in pcre_study() instead of relying on "default" for
74        opcodes that mean there is no starting character; this means that when new
75        ones are added and accidentally left out of pcre_study(), testing should
76        pick them up.
78    14. The -s option of pcretest has been documented for ages as being an old
79        synonym of -m (show memory usage). I have changed it to mean "force study
80        for every regex", that is, assume /S for every regex. This is similar to -i
81        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
82        using it. It makes it easier to run collections of tests with and without
83        study enabled, and thereby test pcre_study() more easily. All the standard
84        tests are now run with and without -s (but some patterns can be marked as
85        "never study" - see 20 below).
87    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
88        restoration of the capturing data to the outer values was not happening
89        correctly.
91    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
92        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
93        pattern had matched an empty string, and so incorrectly returned a no
94        match.
96    17. There was optimizing code for the last branch of non-capturing parentheses,
97        and also for the obeyed branch of a conditional subexpression, which used
98        tail recursion to cut down on stack usage. Unfortunately, not that there is
99        the possibility of (*THEN) occurring in these branches, tail recursion is
100        no longer possible because the return has to be checked for (*THEN). These
101        two optimizations have therefore been removed.
103    18. If a pattern containing \R was studied, it was assumed that \R always
104        matched two bytes, thus causing the minimum subject length to be
105        incorrectly computed because \R can also match just one byte.
107    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
108        was incorrectly computed.
110    20. If /S is present twice on a test pattern in pcretest input, it *disables*
111        studying, thereby overriding the use of -s on the command line. This is
112        necessary for one or two tests to keep the output identical in both cases.
114    21. When (*ACCEPT) was used in an assertion that matched an empty string and
115        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
117    22. When an atomic group that contained a capturing parenthesis was
118        successfully matched, but the branch in which it appeared failed, the
119        capturing was not being forgotten if a higher numbered group was later
120        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
121        group 1 to "a", when in fact it should be unset. This applied to multi-
122        branched capturing and non-capturing groups, repeated or not, and also to
123        positive assertions (capturing in negative assertions is not well defined
124        in PCRE) and also to nested atomic groups.
126    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
127        subject after a captured substring (to make it easier to tell which of a
128        number of identical substrings has been captured).
130    24. The way atomic groups are processed by pcre_exec() has been changed so that
131        if they are repeated, backtracking one repetition now resets captured
132        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
133        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
134        "aaa". Previously, it would have been "a". As part of this code
135        refactoring, the way recursive calls are handled has also been changed.
137    24. If an assertion condition captured any substrings, they were not passed
138        back unless some other capturing happened later. For example, if
139        (?(?=(a))a) was matched against "a", no capturing was returned.
141    25. When studying a pattern that contained subroutine calls or assertions,
142        the code for finding the minimum length of a possible match was handling
143        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
144        group 1 called group 2 while simultaneously a separate group 2 called group
145        1). A stack overflow occurred in this case. I have fixed this by limiting
146        the recursion depth to 10.
148    26. Updated RunTest.bat in the distribution to the version supplied by Tom
149        Fortmann. This supports explicit test numbers on the command line, and has
150        argument validation and error reporting.
152    27. An instance of \X with an unlimited repeat could fail if at any point the
153        first character it looked at was a mark character.
155    28. Some minor code refactoring concerning Unicode properties and scripts
156        should reduce the stack requirement of match() slightly.
158    29. Added the '=' option to pcretest to check the setting of unused capturing
159        slots at the end of the pattern, which are documented as being -1, but are
160        not included in the return count.
162    30. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
163        compiled something random. Now it gives a compile-time error (as does
164        Perl).
166    31. A *MARK encountered during the processing of a positive assertion is now
167        recorded and passed back (compatible with Perl).
169    32. If --only-matching or --colour was set on a pcregrep call whose pattern
170        had alternative anchored branches, the search for a second match in a line
171        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
172        matched the line "0102" twice. The same bug affected patterns that started
173        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
174        twice.
176    33. Previously, PCRE did not allow quantification of assertions. However, Perl
177        does, and because of capturing effects, quantifying parenthesized
178        assertions may at times be useful. Quantifiers are now allowed for
179        parenthesized assertions.
181    34. A minor code tidy in pcre_compile() when checking options for \R usage.
183    35. \g was being checked for fancy things in a character class, when it should
184        just be a literal "g".
186    36. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
187        appearance of a nested POSIX class supersedes an apparent external class.
188        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
189        unescaped square brackets may also appear as part of class names. For
190        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
191        more like Perl.
193    37. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
194        was because it thought it was \N{name}, which is not supported).
196    38. Add minix to OS list not supporting the -S option in pcretest.
199    Version 8.12 15-Jan-2011
200    ------------------------
202    1.  Fixed some typos in the markup of the man pages, and wrote a script that
203        checks for such things as part of the documentation building process.
205    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
206        --match-limit and --recursion-limit options (added for 8.11). In
207        particular, this made one of the standard tests fail. (The integer value
208        went into the wrong half of a long int.)
210    3.  If the --colour option was given to pcregrep with -v (invert match), it
211        did strange things, either producing crazy output, or crashing. It should,
212        of course, ignore a request for colour when reporting lines that do not
213        match.
215    4.  Another pcregrep bug caused similar problems if --colour was specified with
216        -M (multiline) and the pattern match finished with a line ending.
218    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
219        matched in multiline mode, the following line was shown as part of the
220        match. This seems wrong, so I have changed it.
222    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
223        the check for further matches in the same line (so they could be coloured)
224        to overrun the end of the current line. If another match was found, it was
225        incorrectly shown (and then shown again when found in the next line).
227    7.  If pcregrep was compiled under Windows, there was a reference to the
228        function pcregrep_exit() before it was defined. I am assuming this was
229        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
230        reported by a user. I've moved the definition above the reference.
233    Version 8.11 10-Dec-2010
234    ------------------------
236    1.  (*THEN) was not working properly if there were untried alternatives prior
237        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
238        backtracked to try for "b" instead of moving to the next alternative branch
239        at the same level (in this case, to look for "c"). The Perl documentation
240        is clear that when (*THEN) is backtracked onto, it goes to the "next
241        alternative in the innermost enclosing group".
243    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
244        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
245        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
246        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
247        (*THEN).
249    3.  If \s appeared in a character class, it removed the VT character from
250        the class, even if it had been included by some previous item, for example
251        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
252        of \s, but is part of the POSIX "space" class.)
254    4.  A partial match never returns an empty string (because you can always
255        match an empty string at the end of the subject); however the checking for
256        an empty string was starting at the "start of match" point. This has been
257        changed to the "earliest inspected character" point, because the returned
258        data for a partial match starts at this character. This means that, for
259        example, /(?<=abc)def/ gives a partial match for the subject "abc"
260        (previously it gave "no match").
262    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
263        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
264        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
265        has an implication that the given string is incomplete (because a partial
266        match is preferred over a full match). For this reason, these items now
267        give a partial match in this situation. [Aside: previously, the one case
268        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
269        match rather than a full match, which was wrong by the old rules, but is
270        now correct.]
272    6.  There was a bug in the handling of #-introduced comments, recognized when
273        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
274        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
275        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
276        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
277        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
278        places in pcre_compile().
280    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
281        comments when looking ahead for named forward references to subpatterns,
282        the only newline sequence it recognized was NL. It now handles newlines
283        according to the set newline convention.
285    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
286        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
287        cater for a lack of strerror(). These oversights have been fixed.
289    9.  Added --match-limit and --recursion-limit to pcregrep.
291    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
293    11. When the -o option was used, pcregrep was setting a return code of 1, even
294        when matches were found, and --line-buffered was not being honoured.
296    12. Added an optional parentheses number to the -o and --only-matching options
297        of pcregrep.
299    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
300        can match an empty string. The code to do it in pcretest and pcredemo
301        needed fixing:
303        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
304            only one byte after an empty string match just before CRLF (this case
305            just got forgotten; "any" and "anycrlf" were OK).
307        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
308            mode when an empty string match preceded an ASCII character followed by
309            a non-ASCII character. (The code for advancing by one character rather
310            than one byte was nonsense.)
312        (c) The pcredemo.c sample program did not have any code at all to handle
313            the cases when CRLF is a valid newline sequence.
315    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
316        as a starting offset was within the subject string. There is now a new
317        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
318        negative or greater than the length of the string. In order to test this,
319        pcretest is extended to allow the setting of negative starting offsets.
321    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
322        starting offset points to the beginning of a UTF-8 character was
323        unnecessarily clumsy. I tidied it up.
325    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
326        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
328    17. Nobody had reported that the --include_dir option, which was added in
329        release 7.7 should have been called --include-dir (hyphen, not underscore)
330        for compatibility with GNU grep. I have changed it to --include-dir, but
331        left --include_dir as an undocumented synonym, and the same for
332        --exclude-dir, though that is not available in GNU grep, at least as of
333        release 2.5.4.
335    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
336        characters from a string of bytes) have been redefined so as not to use
337        loops, in order to improve performance in some environments. At the same
338        time, I abstracted some of the common code into auxiliary macros to save
339        repetition (this should not affect the compiled code).
341    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
342        compile-time error is now given if \c is not followed by an ASCII
343        character, that is, a byte less than 128. (In EBCDIC mode, the code is
344        different, and any byte value is allowed.)
346    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
347        START_OPTIMIZE option, which is now allowed at compile time - but just
348        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
349        to pcregrep and other applications that have no direct access to PCRE
350        options. The new /Y option in pcretest sets this option when calling
351        pcre_compile().
353    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
354        back references. Groups containing recursive back references were forced to
355        be atomic by that change, but in the case of named groups, the amount of
356        memory required was incorrectly computed, leading to "Failed: internal
357        error: code overflow". This has been fixed.
359    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
360        pcretest.c, to avoid build problems in some Borland environments.
363    Version 8.10 25-Jun-2010
364    ------------------------
366    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
367        THEN.
369    2.  (*ACCEPT) was not working when inside an atomic group.
371    3.  Inside a character class, \B is treated as a literal by default, but
372        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
373        causes the error). The code is unchanged, but I tidied the documentation.
375    4.  Inside a character class, PCRE always treated \R and \X as literals,
376        whereas Perl faults them if its -w option is set. I have changed PCRE so
377        that it faults them when PCRE_EXTRA is set.
379    5.  Added support for \N, which always matches any character other than
380        newline. (It is the same as "." when PCRE_DOTALL is not set.)
382    6.  When compiling pcregrep with newer versions of gcc which may have
383        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
384        declared with attribute warn_unused_result" were given. Just casting the
385        result to (void) does not stop the warnings; a more elaborate fudge is
386        needed. I've used a macro to implement this.
388    7.  Minor change to pcretest.c to avoid a compiler warning.
390    8.  Added four artifical Unicode properties to help with an option to make
391        \s etc use properties (see next item). The new properties are: Xan
392        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
394    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
395        use Unicode properties. (*UCP) at the start of a pattern can be used to set
396        this option. Modified pcretest to add /W to test this facility. Added
397        REG_UCP to make it available via the POSIX interface.
399    10. Added --line-buffered to pcregrep.
401    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
402        studied, and the match started with a letter with a code point greater than
403        127 whose first byte was different to the first byte of the other case of
404        the letter, the other case of this starting letter was not recognized
405        (#976).
407    12. If a pattern that was studied started with a repeated Unicode property
408        test, for example, \p{Nd}+, there was the theoretical possibility of
409        setting up an incorrect bitmap of starting bytes, but fortunately it could
410        not have actually happened in practice until change 8 above was made (it
411        added property types that matched character-matching opcodes).
413    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
414        possible starting bytes for non-anchored patterns.
416    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
417        \R, and also a number of cases that involve Unicode properties, both
418        explicit and implicit when PCRE_UCP is set.
420    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
421        input, it could crash or give wrong results if characters with values
422        greater than 0xc0 were present in the subject string. (Detail: it assumed
423        UTF-8 input when processing these items.)
425    16. Added a lot of (int) casts to avoid compiler warnings in systems where
426        size_t is 64-bit (#991).
428    17. Added a check for running out of memory when PCRE is compiled with
429        --disable-stack-for-recursion (#990).
431    18. If the last data line in a file for pcretest does not have a newline on
432        the end, a newline was missing in the output.
434    19. The default pcre_chartables.c file recognizes only ASCII characters (values
435        less than 128) in its various bitmaps. However, there is a facility for
436        generating tables according to the current locale when PCRE is compiled. It
437        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
438        characters, are recognized by isspace() and therefore were getting set in
439        these tables, and indeed these tables seem to approximate to ISO 8859. This
440        caused a problem in UTF-8 mode when pcre_study() was used to create a list
441        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
442        which of course cannot start UTF-8 characters. I have changed the code so
443        that only real ASCII characters (less than 128) and the correct starting
444        bytes for UTF-8 encodings are set for characters greater than 127 when in
445        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
446        altogether.)
448    20. Added the /T option to pcretest so as to be able to run tests with non-
449        standard character tables, thus making it possible to include the tests
450        used for 19 above in the standard set of tests.
452    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
453        reference to a subpattern the other side of a comment that contains an
454        opening parenthesis caused either an internal compiling error, or a
455        reference to the wrong subpattern.
458    Version 8.02 19-Mar-2010
459    ------------------------
461    1.  The Unicode data tables have been updated to Unicode 5.2.0.
463    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
464        configured.
466    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
467        original author of that file, following a query about its status.
469    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
470        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
472    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
473        quantifier applied to a forward-referencing subroutine call, could compile
474        incorrect code or give the error "internal error: previously-checked
475        referenced subpattern not found".
477    6.  Both MS Visual Studio and Symbian OS have problems with initializing
478        variables to point to external functions. For these systems, therefore,
479        pcre_malloc etc. are now initialized to local functions that call the
480        relevant global functions.
482    7.  There were two entries missing in the vectors called coptable and poptable
483        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
484        I've fixed the data, and added a kludgy way of testing at compile time that
485        the lengths are correct (equal to the number of opcodes).
487    8.  Following on from 7, I added a similar kludge to check the length of the
488        eint vector in pcreposix.c.
490    9.  Error texts for pcre_compile() are held as one long string to avoid too
491        much relocation at load time. To find a text, the string is searched,
492        counting zeros. There was no check for running off the end of the string,
493        which could happen if a new error number was added without updating the
494        string.
496    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
498    11. \K was not working if it appeared in an atomic group or in a group that
499        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
500        \K is "not well defined" if used in an assertion. PCRE now accepts it if
501        the assertion is positive, but not if it is negative.
503    12. Change 11 fortuitously reduced the size of the stack frame used in the
504        "match()" function of pcre_exec.c by one pointer. Forthcoming
505        implementation of support for (*MARK) will need an extra pointer on the
506        stack; I have reserved it now, so that the stack frame size does not
507        decrease.
509    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
510        item in branch that calls a recursion is a subroutine call - as in the
511        second branch in the above example - was incorrectly given the compile-
512        time error "recursive call could loop indefinitely" because pcre_compile()
513        was not correctly checking the subroutine for matching a non-empty string.
515    14. The checks for overrunning compiling workspace could trigger after an
516        overrun had occurred. This is a "should never occur" error, but it can be
517        triggered by pathological patterns such as hundreds of nested parentheses.
518        The checks now trigger 100 bytes before the end of the workspace.
520    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
523    Version 8.01 19-Jan-2010
524    ------------------------
526    1.  If a pattern contained a conditional subpattern with only one branch (in
527        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
528        computed the wrong minimum data length (which is of course zero for such
529        subpatterns). This could cause incorrect "no match" results.
531    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
532        the pattern is reset in the first branch, pcre_compile() failed with
533        "internal error: code overflow at offset...". This happened only when
534        the reset was to the original external option setting. (An optimization
535        abstracts leading options settings into an external setting, which was the
536        cause of this.)
538    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
539        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
540        assertion pattern did not match (meaning that the assertion was true), it
541        was incorrectly treated as false if the SKIP had been reached during the
542        matching. This also applied to assertions used as conditions.
544    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
545        assertion subpattern, including such a pattern used as a condition,
546        unpredictable results occurred, instead of the error return
549    5.  The C++ GlobalReplace function was not working like Perl for the special
550        situation when an empty string is matched. It now does the fancy magic
551        stuff that is necessary.
553    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
554        removed. (These were left over from very, very early versions of PCRE.)
556    7.  Some cosmetic changes to the code to make life easier when compiling it
557        as part of something else:
559        (a) Change DEBUG to PCRE_DEBUG.
561        (b) In pcre_compile(), rename the member of the "branch_chain" structure
562            called "current" as "current_branch", to prevent a collision with the
563            Linux macro when compiled as a kernel module.
565        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
566            prevent a collision with the Linux macro when compiled as a kernel
567            module.
569    8.  In pcre_compile() there are some checks for integer overflows that used to
570        cast potentially large values to (double). This has been changed to that
571        when building, a check for int64_t is made, and if it is found, it is used
572        instead, thus avoiding the use of floating point arithmetic. (There is no
573        other use of FP in PCRE.) If int64_t is not found, the fallback is to
574        double.
576    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
577        2005 (difference between two addresses compared to an unsigned value).
579    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
580        custom one, because of the following reported problem in Windows:
582          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
583              under Win32.
584          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
585              therefore missing the function definition.
586          - The compiler thus generates a "C" signature for the test function.
587          - The linker fails to find the "C" function.
588          - PCRE fails to configure if asked to do so against libbz2.
590    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
591        messages were output:
593          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
594          rerunning libtoolize, to keep the correct libtool macros in-tree.
595          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
597        I have done both of these things.
599    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
600        most of the time, it *can* run out if it is given a pattern that contains a
601        runaway infinite recursion. I updated the discussion in the pcrestack man
602        page.
604    13. Now that we have gone to the x.xx style of version numbers, the minor
605        version may start with zero. Using 08 or 09 is a bad idea because users
606        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
607        interpreted as invalid octal numbers. I've updated the previous comment in
608        configure.ac, and also added a check that gives an error if 08 or 09 are
609        used.
611    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
612        causing partial matching to fail when the end of the subject matched \W
613        in a UTF-8 pattern where \W was quantified with a minimum of 3.
615    15. There were some discrepancies between the declarations in pcre_internal.h
616        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
617        their definitions. The declarations used "const uschar *" and the
618        definitions used USPTR. Even though USPTR is normally defined as "const
619        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
620        reported that: "This difference in casting confuses some C++ compilers, for
621        example, SunCC recognizes above declarations as different functions and
622        generates broken code for hbpcre." I have changed the declarations to use
623        USPTR.
625    16. GNU libtool is named differently on some systems. The autogen.sh script now
626        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
627        (FreeBSD).
629    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
630        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
631        comment: "Figure out how to create a longlong from a string: strtoll and
632        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
633        instance, but it only takes 2 args instead of 3!"
635    18. A subtle bug concerned with back references has been fixed by a change of
636        specification, with a corresponding code fix. A pattern such as
637        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
638        refers, was giving matches when it shouldn't. For example, xa=xaaa would
639        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
640        same bug. Such groups have to be quantified to be useful, or contained
641        inside another quantified group. (If there's no repetition, the reference
642        can never match.) The problem arises because, having left the group and
643        moved on to the rest of the pattern, a later failure that backtracks into
644        the group uses the captured value from the final iteration of the group
645        rather than the correct earlier one. I have fixed this in PCRE by forcing
646        any group that contains a reference to itself to be an atomic group; that
647        is, there cannot be any backtracking into it once it has completed. This is
648        similar to recursive and subroutine calls.
651    Version 8.00 19-Oct-09
652    ----------------------
654    1.  The table for translating pcre_compile() error codes into POSIX error codes
655        was out-of-date, and there was no check on the pcre_compile() error code
656        being within the table. This could lead to an OK return being given in
657        error.
659    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
660        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
661        in a Windows environment.
663    3.  The pcregrep --count option prints the count for each file even when it is
664        zero, as does GNU grep. However, pcregrep was also printing all files when
665        --files-with-matches was added. Now, when both options are given, it prints
666        counts only for those files that have at least one match. (GNU grep just
667        prints the file name in this circumstance, but including the count seems
668        more useful - otherwise, why use --count?) Also ensured that the
669        combination -clh just lists non-zero counts, with no names.
671    4.  The long form of the pcregrep -F option was incorrectly implemented as
672        --fixed_strings instead of --fixed-strings. This is an incompatible change,
673        but it seems right to fix it, and I didn't think it was worth preserving
674        the old behaviour.
676    5.  The command line items --regex=pattern and --regexp=pattern were not
677        recognized by pcregrep, which required --regex pattern or --regexp pattern
678        (with a space rather than an '='). The man page documented the '=' forms,
679        which are compatible with GNU grep; these now work.
681    6.  No libpcreposix.pc file was created for pkg-config; there was just
682        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
684    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
685        when UCP support is not needed, by modifying the Python script that
686        generates it from Unicode data files. This should not matter if the module
687        is correctly used as a library, but I received one complaint about 50K of
688        unwanted data. My guess is that the person linked everything into his
689        program rather than using a library. Anyway, it does no harm.
691    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
692        was a minimum greater than 1 for a wide character in a possessive
693        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
694        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
695        character. Chaos in the form of incorrect output or a compiling loop could
696        result.
698    9.  The restrictions on what a pattern can contain when partial matching is
699        requested for pcre_exec() have been removed. All patterns can now be
700        partially matched by this function. In addition, if there are at least two
701        slots in the offset vector, the offset of the earliest inspected character
702        for the match and the offset of the end of the subject are set in them when
703        PCRE_ERROR_PARTIAL is returned.
705    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
706        synonymous with PCRE_PARTIAL, for backwards compatibility, and
707        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
708        and may be more useful for multi-segment matching.
710    11. Partial matching with pcre_exec() is now more intuitive. A partial match
711        used to be given if ever the end of the subject was reached; now it is
712        given only if matching could not proceed because another character was
713        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
714        string "Z", which now yields "no match" instead of "partial match". In the
715        case of pcre_dfa_exec(), "no match" is given if every matching path for the
716        final character ended with (*FAIL).
718    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
719        if the pattern had a "must contain" character that was already found in the
720        earlier partial match, unless partial matching was again requested. For
721        example, with the pattern /dog.(body)?/, the "must contain" character is
722        "g". If the first part-match was for the string "dog", restarting with
723        "sbody" failed. This bug has been fixed.
725    13. The string returned by pcre_dfa_exec() after a partial match has been
726        changed so that it starts at the first inspected character rather than the
727        first character of the match. This makes a difference only if the pattern
728        starts with a lookbehind assertion or \b or \B (\K is not supported by
729        pcre_dfa_exec()). It's an incompatible change, but it makes the two
730        matching functions compatible, and I think it's the right thing to do.
732    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
733        so that the demonstration program is easily available in environments where
734        PCRE has not been installed from source.
736    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
737        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
738        library.
740    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
741        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
742        is not the first non-POSIX option to be added. Clearly some people find
743        these options useful.
745    17. If a caller to the POSIX matching function regexec() passes a non-zero
746        value for nmatch with a NULL value for pmatch, the value of
747        nmatch is forced to zero.
749    18. RunGrepTest did not have a test for the availability of the -u option of
750        the diff command, as RunTest does. It now checks in the same way as
751        RunTest, and also checks for the -b option.
753    19. If an odd number of negated classes containing just a single character
754        interposed, within parentheses, between a forward reference to a named
755        subpattern and the definition of the subpattern, compilation crashed with
756        an internal error, complaining that it could not find the referenced
757        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
758        [The bug was that it was starting one character too far in when skipping
759        over the character class, thus treating the ] as data rather than
760        terminating the class. This meant it could skip too much.]
762    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
763        /g option in pcretest when the pattern contains \K, which makes it possible
764        to have an empty string match not at the start, even when the pattern is
765        anchored. Updated pcretest and pcredemo to use this option.
767    21. If the maximum number of capturing subpatterns in a recursion was greater
768        than the maximum at the outer level, the higher number was returned, but
769        with unset values at the outer level. The correct (outer level) value is
770        now given.
772    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
773        PCRE did not set those parentheses (unlike Perl). I have now found a way to
774        make it do so. The string so far is captured, making this feature
775        compatible with Perl.
777    23. The tests have been re-organized, adding tests 11 and 12, to make it
778        possible to check the Perl 5.10 features against Perl 5.10.
780    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
781        pattern matches a fixed length string. PCRE did not allow this; now it
782        does. Neither allows recursion.
784    25. I finally figured out how to implement a request to provide the minimum
785        length of subject string that was needed in order to match a given pattern.
786        (It was back references and recursion that I had previously got hung up
787        on.) This code has now been added to pcre_study(); it finds a lower bound
788        to the length of subject needed. It is not necessarily the greatest lower
789        bound, but using it to avoid searching strings that are too short does give
790        some useful speed-ups. The value is available to calling programs via
791        pcre_fullinfo().
793    26. While implementing 25, I discovered to my embarrassment that pcretest had
794        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
795        study optimizations had never been tested with that matching function.
796        Oops. What is worse, even when it was passed study data, there was a bug in
797        pcre_dfa_exec() that meant it never actually used it. Double oops. There
798        were also very few tests of studied patterns with pcre_dfa_exec().
800    27. If (?| is used to create subpatterns with duplicate numbers, they are now
801        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
802        on the other side of the coin, they are no longer allowed to have different
803        names, because these cannot be distinguished in PCRE, and this has caused
804        confusion. (This is a difference from Perl.)
806    28. When duplicate subpattern names are present (necessarily with different
807        numbers, as required by 27 above), and a test is made by name in a
808        conditional pattern, either for a subpattern having been matched, or for
809        recursion in such a pattern, all the associated numbered subpatterns are
810        tested, and the overall condition is true if the condition is true for any
811        one of them. This is the way Perl works, and is also more like the way
812        testing by number works.
815    Version 7.9 11-Apr-09
816    ---------------------
818    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
819        (pcretest), all targets were linked against these libraries. This included
820        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
821        libraries. This caused unwanted dependencies to be created. This problem
822        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
823        pcretest is linked with readline.
825    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
826        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
827        moved outside it again, because FALSE and TRUE are already defined in AIX,
828        but BOOL is not.
830    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
831        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
833    4.  The pcregrep documentation said spaces were inserted as well as colons (or
834        hyphens) following file names and line numbers when outputting matching
835        lines. This is not true; no spaces are inserted. I have also clarified the
836        wording for the --colour (or --color) option.
838    5.  In pcregrep, when --colour was used with -o, the list of matching strings
839        was not coloured; this is different to GNU grep, so I have changed it to be
840        the same.
842    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
843        each matching line was coloured. Now it goes on to look for further matches
844        of any of the test patterns, which is the same behaviour as GNU grep.
846    7.  A pattern that could match an empty string could cause pcregrep to loop; it
847        doesn't make sense to accept an empty string match in pcregrep, so I have
848        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
849        seems to be how GNU grep behaves.
851    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
852        start or after a newline", because the conditional assertion was not being
853        correctly handled. The rule now is that both the assertion and what follows
854        in the first alternative must satisfy the test.
856    9.  If auto-callout was enabled in a pattern with a conditional group whose
857        condition was an assertion, PCRE could crash during matching, both with
858        pcre_exec() and pcre_dfa_exec().
860    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
861        used for matching.
863    11. Unicode property support in character classes was not working for
864        characters (bytes) greater than 127 when not in UTF-8 mode.
866    12. Added the -M command line option to pcretest.
868    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
870    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
872    16. Added comments and documentation about mis-use of no_arg in the C++
873        wrapper.
875    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
876        from Martin Jerabek that uses macro names for all relevant character and
877        string constants.
879    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
880        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
881        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
882        these, but not everybody uses configure.
884    19. A conditional group that had only one branch was not being correctly
885        recognized as an item that could match an empty string. This meant that an
886        enclosing group might also not be so recognized, causing infinite looping
887        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
888        with the subject "ab", where knowledge that the repeated group can match
889        nothing is needed in order to break the loop.
891    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
892        exec(), but without supplying a callout function, matching went wrong.
894    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
895        leak if the size of the offset vector was greater than 30. When the vector
896        is smaller, the saved offsets during recursion go onto a local stack
897        vector, but for larger vectors malloc() is used. It was failing to free
898        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
899        error, in fact).
901    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
902        heapframe that is used only when UTF-8 support is enabled. This caused no
903        problem, but was untidy.
905    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
906        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
907        included within another project.
909    24. Steven Van Ingelgem's patches to add more options to the CMake support,
910        slightly modified by me:
912          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
913              not building pcregrep.
915          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
916              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
918    25. Forward references, both numeric and by name, in patterns that made use of
919        duplicate group numbers, could behave incorrectly or give incorrect errors,
920        because when scanning forward to find the reference group, PCRE was not
921        taking into account the duplicate group numbers. A pattern such as
922        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
924    26. Changed a few more instances of "const unsigned char *" to USPTR, making
925        the feature of a custom pointer more persuasive (as requested by a user).
927    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
928        pcretest.c, inside #ifndefs, because it seems they are sometimes already
929        pre-defined.
931    28. Added support for (*UTF8) at the start of a pattern.
933    29. Arrange for flags added by the "release type" setting in CMake to be shown
934        in the configuration summary.
937    Version 7.8 05-Sep-08
938    ---------------------
940    1.  Replaced UCP searching code with optimized version as implemented for Ad
941        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
942        stage table and inline lookup instead of a function, giving speed ups of 2
943        to 5 times on some simple patterns that I tested. Permission was given to
944        distribute the MultiStage2.py script that generates the tables (it's not in
945        the tarball, but is in the Subversion repository).
947    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
948        scripts.
950    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
951        a group with a zero qualifier. The result of the study could be incorrect,
952        or the function might crash, depending on the pattern.
954    4.  Caseless matching was not working for non-ASCII characters in back
955        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
956        It now works when Unicode Property Support is available.
958    5.  In pcretest, an escape such as \x{de} in the data was always generating
959        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
960        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
961        truncation.
963    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
965    7.  Added two (int) casts to pcregrep when printing the difference of two
966        pointers, in case they are 64-bit values.
968    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
969        test 2 if it fails.
971    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
972        and a #define of that name to empty if it is not externally set. This is to
973        allow users of MSVC to set it if necessary.
975    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
976        the convenience functions in the pcre_get.c source file.
978    11. An option change at the start of a pattern that had top-level alternatives
979        could cause overwriting and/or a crash. This command provoked a crash in
980        some environments:
982          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
984        This potential security problem was recorded as CVE-2008-2371.
986    12. For a pattern where the match had to start at the beginning or immediately
987        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
988        pcre_dfa_exec() could read past the end of the passed subject if there was
989        no match. To help with detecting such bugs (e.g. with valgrind), I modified
990        pcretest so that it places the subject at the end of its malloc-ed buffer.
992    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
993        exec() might read past the end of the data buffer in UTF-8 mode.
995    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
996        the data contained the byte 0x85 as part of a UTF-8 character within its
997        first line. This applied both to normal and DFA matching.
999    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
1000        /^[^d]*?$/8 failed to match "abc".
1002    16. Added a missing copyright notice to pcrecpp_internal.h.
1004    17. Make it more clear in the documentation that values returned from
1005        pcre_exec() in ovector are byte offsets, not character counts.
1007    18. Tidied a few places to stop certain compilers from issuing warnings.
1009    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
1010        supplied by Stefan Weber. I made a further small update for 7.8 because
1011        there is a change of source arrangements: the pcre_searchfuncs.c module is
1012        replaced by pcre_ucd.c.
1015    Version 7.7 07-May-08
1016    ---------------------
1018    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
1019        a string to a long long, pretend we don't even have a long long." This is
1020        done by checking for the strtoq, strtoll, and _strtoi64 functions.
1022    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
1023        pre-7.6 versions, which defined a global no_arg variable instead of putting
1024        it in the RE class. (See also #8 below.)
1026    3.  Remove a line of dead code, identified by coverity and reported by Nuno
1027        Lopes.
1029    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
1031        (1) The include/exclude patterns were being applied to the whole pathnames
1032            of files, instead of just to the final components.
1034        (2) If there was more than one level of directory, the subdirectories were
1035            skipped unless they satisfied the include/exclude conditions. This is
1036            inconsistent with GNU grep (and could even be seen as contrary to the
1037            pcregrep specification - which I improved to make it absolutely clear).
1038            The action now is always to scan all levels of directory, and just
1039            apply the include/exclude patterns to regular files.
1041    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
1042        --exclude_dir in the tests to avoid scanning .svn directories.
1044    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
1045        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
1046        doesn't support NULs in patterns.
1048    7.  Added some missing "const"s to declarations of static tables in
1049        pcre_compile.c and pcre_dfa_exec.c.
1051    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
1052        caused by fix #2  above. (Subsequently also a second patch to fix the
1053        first patch. And a third patch - this was a messy problem.)
1055    9.  Applied Craig's patch to remove the use of push_back().
1057    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
1058        matching function regexec().
1060    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
1061        which, however, unlike Perl's \g{...}, are subroutine calls, not back
1062        references. PCRE supports relative numbers with this syntax (I don't think
1063        Oniguruma does).
1065    12. Previously, a group with a zero repeat such as (...){0} was completely
1066        omitted from the compiled regex. However, this means that if the group
1067        was called as a subroutine from elsewhere in the pattern, things went wrong
1068        (an internal error was given). Such groups are now left in the compiled
1069        pattern, with a new opcode that causes them to be skipped at execution
1070        time.
1072    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
1073        to the way PCRE behaves:
1075        (a) A lone ] character is dis-allowed (Perl treats it as data).
1077        (b) A back reference to an unmatched subpattern matches an empty string
1078            (Perl fails the current match path).
1080        (c) A data ] in a character class must be notated as \] because if the
1081            first data character in a class is ], it defines an empty class. (In
1082            Perl it is not possible to have an empty class.) The empty class []
1083            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
1084            The negative empty class [^] matches any one character, independently
1085            of the DOTALL setting.
1087    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
1088        non-existent subpattern following a character class starting with ']' and
1089        containing () gave an internal compiling error instead of "reference to
1090        non-existent subpattern". Fortunately, when the pattern did exist, the
1091        compiled code was correct. (When scanning forwards to check for the
1092        existencd of the subpattern, it was treating the data ']' as terminating
1093        the class, so got the count wrong. When actually compiling, the reference
1094        was subsequently set up correctly.)
1096    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
1097        it was being rejected as not supported by pcre_dfa_exec(), even though
1098        other assertions are supported. I have made pcre_dfa_exec() support
1099        (*FAIL).
1101    16. The implementation of 13c above involved the invention of a new opcode,
1102        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
1103        cannot be changed at match time, I realized I could make a small
1104        improvement to matching performance by compiling OP_ALLANY instead of
1105        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
1106        on the OP_ANY path.
1108    17. Compiling pcretest on Windows with readline support failed without the
1109        following two fixes: (1) Make the unistd.h include conditional on
1110        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
1112    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
1113        ncurses library to be included for pcretest when ReadLine support is
1114        requested, but also to allow for it to be overridden. This patch came from
1115        Daniel Bergström.
1117    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
1118        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
1119        any errors with the current Unicode tables. Thanks to Peter Kankowski for
1120        spotting this.
1123    Version 7.6 28-Jan-08
1124    ---------------------
1126    1.  A character class containing a very large number of characters with
1127        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
1128        overflow.
1130    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
1131        HAVE_LONG_LONG is not defined.
1133    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
1134        bring them up to date and include new features. This patch includes:
1136        - Fixed PH's badly added libz and libbz2 support.
1137        - Fixed a problem with static linking.
1138        - Added pcredemo. [But later removed - see 7 below.]
1139        - Fixed dftables problem and added an option.
1140        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
1141            HAVE_LONG_LONG.
1142        - Added readline support for pcretest.
1143        - Added an listing of the option settings after cmake has run.
1145    4.  A user submitted a patch to Makefile that makes it easy to create
1146        "pcre.dll" under mingw when using Configure/Make. I added stuff to
1147        Makefile.am that cause it to include this special target, without
1148        affecting anything else. Note that the same mingw target plus all
1149        the other distribution libraries and programs are now supported
1150        when configuring with CMake (see 6 below) instead of with
1151        Configure/Make.
1153    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
1154        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
1155        exported in the Windows port". It has not yet been confirmed that the patch
1156        solves the problem, but it does no harm.
1158    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
1159        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
1160        with CMake, and also correct the comment about stack recursion.
1162    7.  Remove the automatic building of pcredemo from the ./configure system and
1163        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
1164        of a program that users should build themselves after PCRE is installed, so
1165        building it automatically is not really right. What is more, it gave
1166        trouble in some build environments.
1168    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
1171    Version 7.5 10-Jan-08
1172    ---------------------
1174    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
1175        values in parens when parsing an RE using the C++ wrapper."
1177    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
1178        Characters greater than 255 were excluded from the class instead of being
1179        included.
1181    3.  The same bug as (2) above applied to negated POSIX classes such as
1182        [:^space:].
1184    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
1185        defined or documented. It seems to have been a typo for PCRE_STATIC, so
1186        I have changed it.
1188    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
1189        first named subpattern) and a construct such as (?&a) would reference the
1190        first named subpattern whose name started with "a" (in other words, the
1191        length check was missing). Both these problems are fixed. "Subpattern name
1192        expected" is now given for (?&) (a zero-length name), and this patch also
1193        makes it give the same error for \k'' (previously it complained that that
1194        was a reference to a non-existent subpattern).
1196    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
1197        this is right because (?- can be followed by option settings as well as by
1198        digits. I have, however, made the messages clearer.
1200    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
1201        than the number used in the conditional) now cause a compile-time error.
1202        This is actually not compatible with Perl, which accepts such patterns, but
1203        treats the conditional as always being FALSE (as PCRE used to), but it
1204        seems to me that giving a diagnostic is better.
1206    8.  Change "alphameric" to the more common word "alphanumeric" in comments
1207        and messages.
1209    9.  Fix two occurrences of "backslash" in comments that should have been
1210        "backspace".
1212    10. Remove two redundant lines of code that can never be obeyed (their function
1213        was moved elsewhere).
1215    11. The program that makes PCRE's Unicode character property table had a bug
1216        which caused it to generate incorrect table entries for sequences of
1217        characters that have the same character type, but are in different scripts.
1218        It amalgamated them into a single range, with the script of the first of
1219        them. In other words, some characters were in the wrong script. There were
1220        thirteen such cases, affecting characters in the following ranges:
1222          U+002b0 - U+002c1
1223          U+0060c - U+0060d
1224          U+0061e - U+00612
1225          U+0064b - U+0065e
1226          U+0074d - U+0076d
1227          U+01800 - U+01805
1228          U+01d00 - U+01d77
1229          U+01d9b - U+01dbf
1230          U+0200b - U+0200f
1231          U+030fc - U+030fe
1232          U+03260 - U+0327f
1233          U+0fb46 - U+0fbb1
1234          U+10450 - U+1049d
1236    12. The -o option (show only the matching part of a line) for pcregrep was not
1237        compatible with GNU grep in that, if there was more than one match in a
1238        line, it showed only the first of them. It now behaves in the same way as
1239        GNU grep.
1241    13. If the -o and -v options were combined for pcregrep, it printed a blank
1242        line for every non-matching line. GNU grep prints nothing, and pcregrep now
1243        does the same. The return code can be used to tell if there were any
1244        non-matching lines.
1246    14. Added --file-offsets and --line-offsets to pcregrep.
1248    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
1249        infinitely looping recursion. The bug was that positive lookaheads were not
1250        being skipped when checking for a possible empty match (negative lookaheads
1251        and both kinds of lookbehind were skipped).
1253    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
1254        inclusion of <windows.h> to before rather than after the definition of
1255        INVALID_FILE_ATTRIBUTES (patch from David Byron).
1257    17. Specifying a possessive quantifier with a specific limit for a Unicode
1258        character property caused pcre_compile() to compile bad code, which led at
1259        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
1260        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
1261        caused the error; without that there was no problem.
1263    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
1265    19. Added --enable-pcretest-libreadline.
1267    20. In pcrecpp.cc, the variable 'count' was incremented twice in
1268        RE::GlobalReplace(). As a result, the number of replacements returned was
1269        double what it should be. I removed one of the increments, but Craig sent a
1270        later patch that removed the other one (the right fix) and added unit tests
1271        that check the return values (which was not done before).
1273    21. Several CMake things:
1275        (1) Arranged that, when cmake is used on Unix, the libraries end up with
1276            the names libpcre and libpcreposix, not just pcre and pcreposix.
1278        (2) The above change means that pcretest and pcregrep are now correctly
1279            linked with the newly-built libraries, not previously installed ones.
1283    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
1284        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
1285        UTF-8 newline character). The key issue is that the pattern starts .*;
1286        this means that the match must be either at the beginning, or after a
1287        newline. The bug was in the code for advancing after a failed match and
1288        checking that the new position followed a newline. It was not taking
1289        account of UTF-8 characters correctly.
1291    23. PCRE was behaving differently from Perl in the way it recognized POSIX
1292        character classes. PCRE was not treating the sequence [:...:] as a
1293        character class unless the ... were all letters. Perl, however, seems to
1294        allow any characters between [: and :], though of course it rejects as
1295        unknown any "names" that contain non-letters, because all the known class
1296        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
1297        for example, whereas PCRE did not - it did not recognize a POSIX character
1298        class. This seemed a bit dangerous, so the code has been changed to be
1299        closer to Perl. The behaviour is not identical to Perl, because PCRE will
1300        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
1301        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
1302        Perl does, and where it didn't before.
1304    24. Rewrite so as to remove the single use of %n from pcregrep because in some
1305        Windows environments %n is disabled by default.
1308    Version 7.4 21-Sep-07
1309    ---------------------
1311    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
1312        means that a class such as [\s] counted as "explicit reference to CR or
1313        LF". That isn't really right - the whole point of the change was to try to
1314        help when there was an actual mention of one of the two characters. So now
1315        the change happens only if \r or \n (or a literal CR or LF) character is
1316        encountered.
1318    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
1319        of both had grown to the point where there were only 3 bits left.
1320        Fortunately, there was spare space in the data structure, and so I have
1321        moved the internal flags into a new 16-bit field to free up more option
1322        bits.
1324    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
1325        but did not set the internal JCHANGED flag - either of these is enough to
1326        control the way the "get" function works - but the PCRE_INFO_JCHANGED
1327        facility is supposed to tell if (?J) was ever used, so now (?J) at the
1328        start sets both bits.
1330    4.  Added options (at build time, compile time, exec time) to change \R from
1331        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
1333    5.  doc/pcresyntax.html was missing from the distribution.
1335    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
1336        compatibility, even though it is no longer used.
1338    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
1339        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
1340        windows.h file is present (where different names are used). [This was
1341        reversed later after testing - see 16 below.]
1343    8.  Changed all #include <config.h> to #include "config.h". There were also
1344        some further <pcre.h> cases that I changed to "pcre.h".
1346    9.  When pcregrep was used with the --colour option, it missed the line ending
1347        sequence off the lines that it output.
1349    10. It was pointed out to me that arrays of string pointers cause lots of
1350        relocations when a shared library is dynamically loaded. A technique of
1351        using a single long string with a table of offsets can drastically reduce
1352        these. I have refactored PCRE in four places to do this. The result is
1353        dramatic:
1355          Originally:                          290
1356          After changing UCP table:            187
1357          After changing error message table:   43
1358          After changing table of "verbs"       36
1359          After changing table of Posix names   22
1361        Thanks to the folks working on Gregex for glib for this insight.
1363    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
1364        unicode-properties was also set.
1366    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
1368    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
1369        checked only for CRLF.
1371    14. Added casts to pcretest.c to avoid compiler warnings.
1373    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
1375    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
1376        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
1377        entirely. This removes changes made in 7 above.
1379    17. The CMake files have been updated, and there is now more information about
1380        building with CMake in the NON-UNIX-USE document.
1383    Version 7.3 28-Aug-07
1384    ---------------------
1386     1. In the rejigging of the build system that eventually resulted in 7.1, the
1387        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
1388        brackets there is not right, since it causes compilers to look for an
1389        installed pcre.h, not the version that is in the source that is being
1390        compiled (which of course may be different). I have changed it back to:
1392          #include "pcre.h"
1394        I have a vague recollection that the change was concerned with compiling in
1395        different directories, but in the new build system, that is taken care of
1396        by the VPATH setting the Makefile.
1398     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
1399        when the subject happened to end in the byte 0x85 (e.g. if the last
1400        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
1401        characters but of course it shouldn't be taken as a newline when it is part
1402        of another character. The bug was that, for an unlimited repeat of . in
1403        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
1404        characters when looking for a newline.
1406     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
1408     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
1409        in debug output.
1411     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
1412        long printing in the pcrecpp unittest when running under MinGW.
1414     6. ESC_K was left out of the EBCDIC table.
1416     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
1417        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
1418        limit also applies to "virtual nesting" when a pattern is recursive, and in
1419        this case 1000 isn't so big. I have been able to remove this limit at the
1420        expense of backing off one optimization in certain circumstances. Normally,
1421        when pcre_exec() would call its internal match() function recursively and
1422        immediately return the result unconditionally, it uses a "tail recursion"
1423        feature to save stack. However, when a subpattern that can match an empty
1424        string has an unlimited repetition quantifier, it no longer makes this
1425        optimization. That gives it a stack frame in which to save the data for
1426        checking that an empty string has been matched. Previously this was taken
1427        from the 1000-entry workspace that had been reserved. So now there is no
1428        explicit limit, but more stack is used.
1430     8. Applied Daniel's patches to solve problems with the import/export magic
1431        syntax that is required for Windows, and which was going wrong for the
1432        pcreposix and pcrecpp parts of the library. These were overlooked when this
1433        problem was solved for the main library.
1435     9. There were some crude static tests to avoid integer overflow when computing
1436        the size of patterns that contain repeated groups with explicit upper
1437        limits. As the maximum quantifier is 65535, the maximum group length was
1438        set at 30,000 so that the product of these two numbers did not overflow a
1439        32-bit integer. However, it turns out that people want to use groups that
1440        are longer than 30,000 bytes (though not repeat them that many times).
1441        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
1442        made it possible to implement the integer overflow checks in a much more
1443        dynamic way, which I have now done. The artificial limitation on group
1444        length has been removed - we now have only the limit on the total length of
1445        the compiled pattern, which depends on the LINK_SIZE setting.
1447    10. Fixed a bug in the documentation for get/copy named substring when
1448        duplicate names are permitted. If none of the named substrings are set, the
1449        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
1450        empty string.
1452    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
1453        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
1454        because the ] is interpreted as the first data character and the
1455        terminating ] is not found. PCRE has been made compatible with Perl in this
1456        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
1457        cause memory overwriting.
1459    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
1460        string has been matched (to stop an infinite loop). It was not recognizing
1461        a conditional subpattern that could match an empty string if that
1462        subpattern was within another subpattern. For example, it looped when
1463        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
1464        condition was not nested. This bug has been fixed.
1466    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
1467        past the start of the subject in the presence of bytes with the top bit
1468        set, for example "\x8aBCD".
1470    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
1471        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
1473    14. Optimized (?!) to (*FAIL).
1475    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
1476        This restricts code points to be within the range 0 to 0x10FFFF, excluding
1477        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
1478        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
1479        does: it's just the validity check that is more restrictive.
1481    16. Inserted checks for integer overflows during escape sequence (backslash)
1482        processing, and also fixed erroneous offset values for syntax errors during
1483        backslash processing.
1485    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
1486        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
1488    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
1489        caused an overrun.
1491    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
1492        something other than just ASCII characters) inside a group that had an
1493        unlimited repeat caused a loop at compile time (while checking to see
1494        whether the group could match an empty string).
1496    20. Debugging a pattern containing \p or \P could cause a crash. For example,
1497        [\P{Any}] did so. (Error in the code for printing property names.)
1499    21. An orphan \E inside a character class could cause a crash.
1501    22. A repeated capturing bracket such as (A)? could cause a wild memory
1502        reference during compilation.
1504    23. There are several functions in pcre_compile() that scan along a compiled
1505        expression for various reasons (e.g. to see if it's fixed length for look
1506        behind). There were bugs in these functions when a repeated \p or \P was
1507        present in the pattern. These operators have additional parameters compared
1508        with \d, etc, and these were not being taken into account when moving along
1509        the compiled data. Specifically:
1511        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
1512            length.
1514        (b) An item such as \pL+ within a repeated group could cause crashes or
1515            loops.
1517        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
1518            "reference to non-existent subpattern" error.
1520        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
1522    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
1523        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
1525    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
1527    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
1528        character were causing crashes (broken optimization).
1530    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
1531        \p or \P) caused a compile-time loop.
1533    28. More problems have arisen in unanchored patterns when CRLF is a valid line
1534        break. For example, the unstudied pattern [\r\n]A does not match the string
1535        "\r\nA" because change 7.0/46 below moves the current point on by two
1536        characters after failing to match at the start. However, the pattern \nA
1537        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
1538        the same is true. There doesn't seem any very clean way out of this, but
1539        what I have chosen to do makes the common cases work: PCRE now takes note
1540        of whether there can be an explicit match for \r or \n anywhere in the
1541        pattern, and if so, 7.0/46 no longer applies. As part of this change,
1542        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
1543        pattern has explicit CR or LF references.
1545    29. Added (*CR) etc for changing newline setting at start of pattern.
1548    Version 7.2 19-Jun-07
1549    ---------------------
1551     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
1552        which is apparently normally available under Windows.
1554     2. Re-jig the pcregrep tests with different newline settings in an attempt
1555        to make them independent of the local environment's newline setting.
1557     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
1559     4. Some of the "internals" tests were previously cut out when the link size
1560        was not 2, because the output contained actual offsets. The recent new
1561        "Z" feature of pcretest means that these can be cut out, making the tests
1562        usable with all link sizes.
1564     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
1565        stack recursion. This gives a massive performance boost under BSD, but just
1566        a small improvement under Linux. However, it saves one field in the frame
1567        in all cases.
1569     6. Added more features from the forthcoming Perl 5.10:
1571        (a) (?-n) (where n is a string of digits) is a relative subroutine or
1572            recursion call. It refers to the nth most recently opened parentheses.
1574        (b) (?+n) is also a relative subroutine call; it refers to the nth next
1575            to be opened parentheses.
1577        (c) Conditions that refer to capturing parentheses can be specified
1578            relatively, for example, (?(-2)... or (?(+3)...
1580        (d) \K resets the start of the current match so that everything before
1581            is not part of it.
1583        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
1585        (f) \g{name} is another synonym - part of Perl 5.10's unification of
1586            reference syntax.
1588        (g) (?| introduces a group in which the numbering of parentheses in each
1589            alternative starts with the same number.
1591        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
1593     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
1596     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
1597        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
1598        for detecting groups that can match an empty string.
1600     9. A pattern with a very large number of alternatives (more than several
1601        hundred) was running out of internal workspace during the pre-compile
1602        phase, where pcre_compile() figures out how much memory will be needed. A
1603        bit of new cunning has reduced the workspace needed for groups with
1604        alternatives. The 1000-alternative test pattern now uses 12 bytes of
1605        workspace instead of running out of the 4096 that are available.
1607    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
1609    11. Applied patch from Google to remove an optimization that didn't quite work.
1610        The report of the bug said:
1612          pcrecpp::RE("a*").FullMatch("aaa") matches, while
1613          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
1614          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
1616    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
1617        it matched the wrong number of bytes.
1620    Version 7.1 24-Apr-07
1621  ---------------------  ---------------------
1623   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
# Line 149  Version 7.1 12-Mar-07 Line 1765  Version 7.1 12-Mar-07
1766  23. Added some casts to kill warnings from HP-UX ia64 compiler.  23. Added some casts to kill warnings from HP-UX ia64 compiler.
1768    24. Added a man page for pcre-config.
1771  Version 7.0 19-Dec-06  Version 7.0 19-Dec-06
1772  ---------------------  ---------------------

Removed from v.152  
changed lines
  Added in v.641

  ViewVC Help
Powered by ViewVC 1.1.5