ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.175  
changed lines
  Added in v.691

  ViewVC Help
Powered by ViewVC 1.1.5