ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 269 by ph10, Fri Nov 16 16:22:24 2007 UTC revision 979 by ph10, Sun Jun 17 19:08:41 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.5 12-Nov-07  Version 8.31 02-June-2012
5    -------------------------
7    1.  Fixing a wrong JIT test case and some compiler warnings.
9    2.  Removed a bashism from the RunTest script.
11    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
12        to unsigned type, result still unsigned" that was given by an MS compiler
13        on encountering the code "-sizeof(xxx)".
15    4.  Partial matching support is added to the JIT compiler.
17    5.  Fixed several bugs concerned with partial matching of items that consist
18        of more than one character:
20        (a) /^(..)\1/ did not partially match "aba" because checking references was
21            done on an "all or nothing" basis. This also applied to repeated
22            references.
24        (b) \R did not give a hard partial match if \r was found at the end of the
25            subject.
27        (c) \X did not give a hard partial match after matching one or more
28            characters at the end of the subject.
30        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
31            a partial match for the string "\r".
33        (e) When newline was set to CRLF, the metacharacter "." did not recognize
34            a partial match for a CR character at the end of the subject string.
36    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
37        running pcretest, the text "(JIT)" added to the output whenever JIT is
38        actually used to run the match.
40    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
41        or /S+[+] with a digit between 1 and 7.
43    8.  OP_NOT now supports any UTF character not just single-byte ones.
45    9.  (*MARK) control verb is now supported by the JIT compiler.
47    10. The command "./RunTest list" lists the available tests without actually
48        running any of them. (Because I keep forgetting what they all are.)
52    12. Applied a (slightly modified) user-supplied patch that improves performance
53        when the heap is used for recursion (compiled with --disable-stack-for-
54        recursion). Instead of malloc and free for each heap frame each time a
55        logical recursion happens, frames are retained on a chain and re-used where
56        possible. This sometimes gives as much as 30% improvement.
58    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
59        call.
61    14. As documented, (*COMMIT) is now confined to within a positive assertion.
63    15. It is now possible to link pcretest with libedit as an alternative to
64        libreadline.
66    16. (*COMMIT) control verb is now supported by the JIT compiler.
68    17. The Unicode data tables have been updated to Unicode 6.1.0.
70    18. Added --file-list option to pcregrep.
72    19. Added binary file support to pcregrep, including the -a, --binary-files,
73        -I, and --text options.
75    20. The madvise function is renamed for posix_madvise for QNX compatibility
76        reasons. Fixed by Giuseppe D'Angelo.
78    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
80    22. Changed the option for creating symbolic links for 16-bit man pages from
81        -s to -sf so that re-installing does not cause issues.
83    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
85    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
86        matches in certain environments (the workspace was not being correctly
87        retained). Also added to pcre_dfa_exec() a simple plausibility check on
88        some of the workspace data at the beginning of a restart.
90    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
91        was not doing so when it should - probably a typo introduced by SVN 528
92        (change 8.10/14).
94    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
95        \w+ when the character tables indicated that \x{c4} was a word character.
96        There were several related cases, all because the tests for doing a table
97        lookup were testing for characters less than 127 instead of 255.
99    27. If a pattern contains capturing parentheses that are not used in a match,
100        their slots in the ovector are set to -1. For those that are higher than
101        any matched groups, this happens at the end of processing. In the case when
102        there were back references that the ovector was too small to contain
103        (causing temporary malloc'd memory to be used during matching), and the
104        highest capturing number was not used, memory off the end of the ovector
105        was incorrectly being set to -1. (It was using the size of the temporary
106        memory instead of the true size.)
108    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
109        ovector size, it uses memory at the end of the block that it has got.
111    29. Check for an overlong MARK name and give an error at compile time. The
112        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
114    30. JIT compiler update.
116    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
117        Rill for the patch.
119    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
121    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
123    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
124        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
125        was enabled.
127    35. Improve JIT code generation for greedy plus quantifier.
129    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
130        1 to "aa" instead of to an empty string. The bug affected repeated groups
131        that could potentially match an empty string.
133    37. Optimizing single character iterators in JIT.
135    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
136        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
137        codepoints that are too big for the mode are faulted, and in a UTF mode,
138        disallowed codepoints are also faulted.
140    39. If PCRE was compiled with UTF support, in three places in the DFA
141        matcher there was code that should only have been obeyed in UTF mode, but
142        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
143        processing when bytes with values greater than 127 were present. In 16-bit
144        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
145        both cases the values are those that cannot be the first data item in a UTF
146        character. The three items that might have provoked this were recursions,
147        possessively repeated groups, and atomic groups.
150    Version 8.30 04-February-2012
151    -----------------------------
153    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
154        name is defined in ctype.h.
156    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
157        only in quite long subpatterns.
159    3.  Removed the function pcre_info(), which has been obsolete and deprecated
160        since it was replaced by pcre_fullinfo() in February 2000.
162    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
163        match a (*MARK), and the match failed at the start of the subject, a
164        reference to memory before the start of the subject could occur. This bug
165        was introduced by fix 17 of release 8.21.
167    5.  A reference to an unset group with zero minimum repetition was giving
168        totally wrong answers (in non-JavaScript-compatibility mode). For example,
169        /(another)?(\1?)test/ matched against "hello world test". This bug was
170        introduced in release 8.13.
172    6.  Add support for 16-bit character strings (a large amount of work involving
173        many changes and refactorings).
175    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
176        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
177        from a file.
179    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
180        rounding is not applied in this particular case).
182    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
183        if they appear, or are escaped, in patterns.
185    10. Get rid of a number of -Wunused-but-set-variable warnings.
187    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
188        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
189        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
190        also returns the mark "x". This bug applied to capturing parentheses,
191        non-capturing parentheses, and atomic parentheses. It also applied to some
192        assertions.
194    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
195        information out of configure.ac instead of relying on pcre.h.generic, which
196        is not stored in the repository.
198    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
199        -lreadline.
201    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
203    15. Applied Graycode's patch to put the top-level frame on the stack rather
204        than the heap when not using the stack for recursion. This gives a
205        performance improvement in many cases when recursion is not deep.
207    16. Experimental code added to "pcretest -C" to output the stack frame size.
210    Version 8.21 12-Dec-2011
211    ------------------------
213    1.  Updating the JIT compiler.
215    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
216        are added as well.
218    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
219        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
220        calling _pcre_jit_exec. Some extra comments are added.
222    4.  (*MARK) settings inside atomic groups that do not contain any capturing
223        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
224        was introduced by change 18 for 8.20.
226    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
227        ECMA-262 standard.
229    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
230        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
231        This bug was probably introduced by change 9 of 8.13.
233    7.  While fixing 6 above, I noticed that a number of other items were being
234        incorrectly rejected as "not fixed length". This arose partly because newer
235        opcodes had not been added to the fixed-length checking code. I have (a)
236        corrected the bug and added tests for these items, and (b) arranged for an
237        error to occur if an unknown opcode is encountered while checking for fixed
238        length instead of just assuming "not fixed length". The items that were
239        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
240        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
241        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
243    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
244        being incorrectly compiled and would have given unpredicatble results.
246    9.  A possessively repeated subpattern with minimum repeat count greater than
247        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
248        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
249        the first (A) could occur when it should not.
251    10. Add a cast and remove a redundant test from the code.
253    11. JIT should use pcre_malloc/pcre_free for allocation.
255    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
256        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
257        is anything other than /usr, -L is still shown).
259    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
261    14. Perl does not support \N without a following name in a [] class; PCRE now
262        also gives an error.
264    15. If a forward reference was repeated with an upper limit of around 2000,
265        it caused the error "internal error: overran compiling workspace". The
266        maximum number of forward references (including repeats) was limited by the
267        internal workspace, and dependent on the LINK_SIZE. The code has been
268        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
269        the default depends on LINK_SIZE. There is a new upper limit (for safety)
270        of around 200,000 forward references. While doing this, I also speeded up
271        the filling in of repeated forward references.
273    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
274        incorrectly expecting the subject to contain another "a" after the start.
276    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
277        in the match, the SKIP should be ignored. This was not happening; instead
278        the SKIP was being treated as NOMATCH. For patterns such as
279        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
280        tested.
282    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
283        now much more compatible with Perl, in particular in cases where the result
284        is a non-match for a non-anchored pattern. For example, if
285        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
286        "m", where previously it did not return a name. A side effect of this
287        change is that for partial matches, the last encountered mark name is
288        returned, as for non matches. A number of tests that were previously not
289        Perl-compatible have been moved into the Perl-compatible test files. The
290        refactoring has had the pleasing side effect of removing one argument from
291        the match() function, thus reducing its stack requirements.
293    19. If the /S+ option was used in pcretest to study a pattern using JIT,
294        subsequent uses of /S (without +) incorrectly behaved like /S+.
296    21. Retrieve executable code size support for the JIT compiler and fixing
297        some warnings.
299    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
300        not work when the shorter character appeared right at the end of the
301        subject string.
303    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
304        systems.
306    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
307        output it when the /M option is used in pcretest.
309    25. The CheckMan script was not being included in the distribution. Also, added
310        an explicit "perl" to run Perl scripts from the PrepareRelease script
311        because this is reportedly needed in Windows.
313    26. If study data was being save in a file and studying had not found a set of
314        "starts with" bytes for the pattern, the data written to the file (though
315        never used) was taken from uninitialized memory and so caused valgrind to
316        complain.
318    27. Updated RunTest.bat as provided by Sheri Pierce.
320    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
322    29. Computation of memory usage for the table of capturing group names was
323        giving an unnecessarily large value.
326    Version 8.20 21-Oct-2011
327    ------------------------
329    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
330        a POSIX class. After further experiments with Perl, which convinced me that
331        Perl has bugs and confusions, a closing square bracket is no longer allowed
332        in a POSIX name. This bug also affected patterns with classes that started
333        with full stops.
335    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
336        captured substring, but while checking the failing first alternative,
337        substring 1 is temporarily captured. If the output vector supplied to
338        pcre_exec() was not big enough for this capture, the yield of the function
339        was still zero ("insufficient space for captured substrings"). This cannot
340        be totally fixed without adding another stack variable, which seems a lot
341        of expense for a edge case. However, I have improved the situation in cases
342        such as /(a)(b)x|abc/ matched against "abc", where the return code
343        indicates that fewer than the maximum number of slots in the ovector have
344        been set.
346    3.  Related to (2) above: when there are more back references in a pattern than
347        slots in the output vector, pcre_exec() uses temporary memory during
348        matching, and copies in the captures as far as possible afterwards. It was
349        using the entire output vector, but this conflicts with the specification
350        that only 2/3 is used for passing back captured substrings. Now it uses
351        only the first 2/3, for compatibility. This is, of course, another edge
352        case.
354    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
355        main code base, and can be used by building with --enable-jit. When this is
356        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
357        runtime --no-jit option is given.
359    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
360        ovector, the return from the function was zero, implying that there were
361        other matches that did not fit. The correct "exactly full" value is now
362        returned.
364    6.  If a subpattern that was called recursively or as a subroutine contained
365        (*PRUNE) or any other control that caused it to give a non-standard return,
366        invalid errors such as "Error -26 (nested recursion at the same subject
367        position)" or even infinite loops could occur.
369    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
370        computing the minimum length on reaching *ACCEPT, and so ended up with the
371        wrong value of 1 rather than 0. Further investigation indicates that
372        computing a minimum subject length in the presence of *ACCEPT is difficult
373        (think back references, subroutine calls), and so I have changed the code
374        so that no minimum is registered for a pattern that contains *ACCEPT.
376    8.  If (*THEN) was present in the first (true) branch of a conditional group,
377        it was not handled as intended. [But see 16 below.]
379    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
380        Sheri Pierce.
382    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
383        the first byte in a match must be "a".
385    11. Change 17 for 8.13 increased the recursion depth for patterns like
386        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
387        pattern contains any instances of (*THEN). If it does not, the old
388        optimizations are restored. It would be nice to do this on a per-group
389        basis, but at the moment that is not feasible.
391    12. In some environments, the output of pcretest -C is CRLF terminated. This
392        broke RunTest's code that checks for the link size. A single white space
393        character after the value is now allowed for.
395    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
396        For "fr", it uses the Windows-specific input and output files.
398    14. If (*THEN) appeared in a group that was called recursively or as a
399        subroutine, it did not work as intended. [But see next item.]
401    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
402        pattern fragments (but not containing any | characters). If A and B are
403        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
404        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
405        D. In other words, Perl considers parentheses that do not contain any |
406        characters to be part of a surrounding alternative, whereas PCRE was
407        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
408        differently. PCRE now behaves in the same way as Perl, except in the case
409        of subroutine/recursion calls such as (?1) which have in any case always
410        been different (but PCRE had them first :-).
412    16. Related to 15 above: Perl does not treat the | in a conditional group as
413        creating alternatives. Such a group is treated in the same way as an
414        ordinary group without any | characters when processing (*THEN). PCRE has
415        been changed to match Perl's behaviour.
417    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
418        RunGrepTest script failed.
420    18. Change 22 for version 13 caused atomic groups to use more stack. This is
421        inevitable for groups that contain captures, but it can lead to a lot of
422        stack use in large patterns. The old behaviour has been restored for atomic
423        groups that do not contain any capturing parentheses.
425    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
426        suppress the check for a minimum subject length at run time. (If it was
427        given to pcre_exec() or pcre_dfa_exec() it did work.)
429    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
430        fail to work when decoding hex characters in data strings in EBCDIC
431        environments.
433    21. It appears that in at least one Mac OS environment, the isxdigit() function
434        is implemented as a macro that evaluates to its argument more than once,
435        contravening the C 90 Standard (I haven't checked a later standard). There
436        was an instance in pcretest which caused it to go wrong when processing
437        \x{...} escapes in subject strings. The has been rewritten to avoid using
438        things like p++ in the argument of isxdigit().
441    Version 8.13 16-Aug-2011
442    ------------------------
444    1.  The Unicode data tables have been updated to Unicode 6.0.0.
446    2.  Two minor typos in pcre_internal.h have been fixed.
448    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
449        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
450        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
452    4.  There were a number of related bugs in the code for matching backrefences
453        caselessly in UTF-8 mode when codes for the characters concerned were
454        different numbers of bytes. For example, U+023A and U+2C65 are an upper
455        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
456        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
457        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
458        2-byte code at the end of the subject (it thought there wasn't enough data
459        left).
461    5.  Comprehensive information about what went wrong is now returned by
462        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
463        as the output vector has at least 2 elements. The offset of the start of
464        the failing character and a reason code are placed in the vector.
466    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
467        now returned is for the first byte of the failing character, instead of the
468        last byte inspected. This is an incompatible change, but I hope it is small
469        enough not to be a problem. It makes the returned offset consistent with
470        pcre_exec() and pcre_dfa_exec().
472    7.  pcretest now gives a text phrase as well as the error number when
473        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
474        failure, the offset and reason code are output.
476    8.  When \R was used with a maximizing quantifier it failed to skip backwards
477        over a \r\n pair if the subsequent match failed. Instead, it just skipped
478        back over a single character (\n). This seems wrong (because it treated the
479        two characters as a single entity when going forwards), conflicts with the
480        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
481        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
482        has been changed.
484    9.  Some internal refactoring has changed the processing so that the handling
485        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
486        time (the PCRE_DOTALL option was changed this way some time ago: version
487        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
488        which was always a bit of a fudge. It also means that there is one less
489        argument for the match() function, which reduces its stack requirements
490        slightly. This change also fixes an incompatibility with Perl: the pattern
491        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
493    10. More internal refactoring has drastically reduced the number of recursive
494        calls to match() for possessively repeated groups such as (abc)++ when
495        using pcre_exec().
497    11. While implementing 10, a number of bugs in the handling of groups were
498        discovered and fixed:
500        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
501        (a|)*(?1) gave a compile-time internal error.
502        ((a|)+)+  did not notice that the outer group could match an empty string.
503        (^a|^)+   was not marked as anchored.
504        (.*a|.*)+ was not marked as matching at start or after a newline.
506    12. Yet more internal refactoring has removed another argument from the match()
507        function. Special calls to this function are now indicated by setting a
508        value in a variable in the "match data" data block.
510    13. Be more explicit in pcre_study() instead of relying on "default" for
511        opcodes that mean there is no starting character; this means that when new
512        ones are added and accidentally left out of pcre_study(), testing should
513        pick them up.
515    14. The -s option of pcretest has been documented for ages as being an old
516        synonym of -m (show memory usage). I have changed it to mean "force study
517        for every regex", that is, assume /S for every regex. This is similar to -i
518        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
519        using it. It makes it easier to run collections of tests with and without
520        study enabled, and thereby test pcre_study() more easily. All the standard
521        tests are now run with and without -s (but some patterns can be marked as
522        "never study" - see 20 below).
524    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
525        restoration of the capturing data to the outer values was not happening
526        correctly.
528    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
529        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
530        pattern had matched an empty string, and so incorrectly returned a no
531        match.
533    17. There was optimizing code for the last branch of non-capturing parentheses,
534        and also for the obeyed branch of a conditional subexpression, which used
535        tail recursion to cut down on stack usage. Unfortunately, now that there is
536        the possibility of (*THEN) occurring in these branches, tail recursion is
537        no longer possible because the return has to be checked for (*THEN). These
538        two optimizations have therefore been removed. [But see 8.20/11 above.]
540    18. If a pattern containing \R was studied, it was assumed that \R always
541        matched two bytes, thus causing the minimum subject length to be
542        incorrectly computed because \R can also match just one byte.
544    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
545        was incorrectly computed.
547    20. If /S is present twice on a test pattern in pcretest input, it now
548        *disables* studying, thereby overriding the use of -s on the command line
549        (see 14 above). This is necessary for one or two tests to keep the output
550        identical in both cases.
552    21. When (*ACCEPT) was used in an assertion that matched an empty string and
553        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
555    22. When an atomic group that contained a capturing parenthesis was
556        successfully matched, but the branch in which it appeared failed, the
557        capturing was not being forgotten if a higher numbered group was later
558        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
559        group 1 to "a", when in fact it should be unset. This applied to multi-
560        branched capturing and non-capturing groups, repeated or not, and also to
561        positive assertions (capturing in negative assertions does not happen
562        in PCRE) and also to nested atomic groups.
564    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
565        subject after a captured substring, to make it easier to tell which of a
566        number of identical substrings has been captured.
568    24. The way atomic groups are processed by pcre_exec() has been changed so that
569        if they are repeated, backtracking one repetition now resets captured
570        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
571        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
572        "aaa". Previously, it would have been "a". As part of this code
573        refactoring, the way recursive calls are handled has also been changed.
575    25. If an assertion condition captured any substrings, they were not passed
576        back unless some other capturing happened later. For example, if
577        (?(?=(a))a) was matched against "a", no capturing was returned.
579    26. When studying a pattern that contained subroutine calls or assertions,
580        the code for finding the minimum length of a possible match was handling
581        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
582        group 1 called group 2 while simultaneously a separate group 2 called group
583        1). A stack overflow occurred in this case. I have fixed this by limiting
584        the recursion depth to 10.
586    27. Updated RunTest.bat in the distribution to the version supplied by Tom
587        Fortmann. This supports explicit test numbers on the command line, and has
588        argument validation and error reporting.
590    28. An instance of \X with an unlimited repeat could fail if at any point the
591        first character it looked at was a mark character.
593    29. Some minor code refactoring concerning Unicode properties and scripts
594        should reduce the stack requirement of match() slightly.
596    30. Added the '=' option to pcretest to check the setting of unused capturing
597        slots at the end of the pattern, which are documented as being -1, but are
598        not included in the return count.
600    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
601        compiled something random. Now it gives a compile-time error (as does
602        Perl).
604    32. A *MARK encountered during the processing of a positive assertion is now
605        recorded and passed back (compatible with Perl).
607    33. If --only-matching or --colour was set on a pcregrep call whose pattern
608        had alternative anchored branches, the search for a second match in a line
609        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
610        matched the line "0102" twice. The same bug affected patterns that started
611        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
612        twice.
614    34. Previously, PCRE did not allow quantification of assertions. However, Perl
615        does, and because of capturing effects, quantifying parenthesized
616        assertions may at times be useful. Quantifiers are now allowed for
617        parenthesized assertions.
619    35. A minor code tidy in pcre_compile() when checking options for \R usage.
621    36. \g was being checked for fancy things in a character class, when it should
622        just be a literal "g".
624    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
625        appearance of a nested POSIX class supersedes an apparent external class.
626        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
627        unescaped square brackets may also appear as part of class names. For
628        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
629        more like Perl. (But see 8.20/1 above.)
631    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
632        was because it thought it was \N{name}, which is not supported).
634    39. Add minix to OS list not supporting the -S option in pcretest.
636    40. PCRE tries to detect cases of infinite recursion at compile time, but it
637        cannot analyze patterns in sufficient detail to catch mutual recursions
638        such as ((?1))((?2)). There is now a runtime test that gives an error if a
639        subgroup is called recursively as a subpattern for a second time at the
640        same position in the subject string. In previous releases this might have
641        been caught by the recursion limit, or it might have run out of stack.
643    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
644        happen only once. PCRE was, however incorrectly giving a compile time error
645        "recursive call could loop indefinitely" because it cannot analyze the
646        pattern in sufficient detail. The compile time test no longer happens when
647        PCRE is compiling a conditional subpattern, but actual runaway loops are
648        now caught at runtime (see 40 above).
650    42. It seems that Perl allows any characters other than a closing parenthesis
651        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
652        has been changed to be the same.
654    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
655        as not to get warnings when autogen.sh is called. Also changed
656        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
658    44. To help people who use pcregrep to scan files containing exceedingly long
659        lines, the following changes have been made:
661        (a) The default value of the buffer size parameter has been increased from
662            8K to 20K. (The actual buffer used is three times this size.)
664        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
665            PCRE is built.
667        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
668            to be set at run time.
670        (d) Numerical values in pcregrep options can be followed by K or M, for
671            example --buffer-size=50K.
673        (e) If a line being scanned overflows pcregrep's buffer, an error is now
674            given and the return code is set to 2.
676    45. Add a pointer to the latest mark to the callout data block.
678    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
679        partial match of an empty string instead of no match. This was specific to
680        the use of ".".
682    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
683        complete match instead of a partial match. This bug was dependent on both
684        the PCRE_UTF8 and PCRE_DOTALL options being set.
686    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
687        starting byte set, because \b was not being ignored.
690    Version 8.12 15-Jan-2011
691    ------------------------
693    1.  Fixed some typos in the markup of the man pages, and wrote a script that
694        checks for such things as part of the documentation building process.
696    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
697        --match-limit and --recursion-limit options (added for 8.11). In
698        particular, this made one of the standard tests fail. (The integer value
699        went into the wrong half of a long int.)
701    3.  If the --colour option was given to pcregrep with -v (invert match), it
702        did strange things, either producing crazy output, or crashing. It should,
703        of course, ignore a request for colour when reporting lines that do not
704        match.
706    4.  Another pcregrep bug caused similar problems if --colour was specified with
707        -M (multiline) and the pattern match finished with a line ending.
709    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
710        matched in multiline mode, the following line was shown as part of the
711        match. This seems wrong, so I have changed it.
713    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
714        the check for further matches in the same line (so they could be coloured)
715        to overrun the end of the current line. If another match was found, it was
716        incorrectly shown (and then shown again when found in the next line).
718    7.  If pcregrep was compiled under Windows, there was a reference to the
719        function pcregrep_exit() before it was defined. I am assuming this was
720        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
721        reported by a user. I've moved the definition above the reference.
724    Version 8.11 10-Dec-2010
725    ------------------------
727    1.  (*THEN) was not working properly if there were untried alternatives prior
728        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
729        backtracked to try for "b" instead of moving to the next alternative branch
730        at the same level (in this case, to look for "c"). The Perl documentation
731        is clear that when (*THEN) is backtracked onto, it goes to the "next
732        alternative in the innermost enclosing group".
734    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
735        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
736        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
737        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
738        (*THEN).
740    3.  If \s appeared in a character class, it removed the VT character from
741        the class, even if it had been included by some previous item, for example
742        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
743        of \s, but is part of the POSIX "space" class.)
745    4.  A partial match never returns an empty string (because you can always
746        match an empty string at the end of the subject); however the checking for
747        an empty string was starting at the "start of match" point. This has been
748        changed to the "earliest inspected character" point, because the returned
749        data for a partial match starts at this character. This means that, for
750        example, /(?<=abc)def/ gives a partial match for the subject "abc"
751        (previously it gave "no match").
753    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
754        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
755        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
756        has an implication that the given string is incomplete (because a partial
757        match is preferred over a full match). For this reason, these items now
758        give a partial match in this situation. [Aside: previously, the one case
759        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
760        match rather than a full match, which was wrong by the old rules, but is
761        now correct.]
763    6.  There was a bug in the handling of #-introduced comments, recognized when
764        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
765        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
766        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
767        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
768        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
769        places in pcre_compile().
771    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
772        comments when looking ahead for named forward references to subpatterns,
773        the only newline sequence it recognized was NL. It now handles newlines
774        according to the set newline convention.
776    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
777        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
778        cater for a lack of strerror(). These oversights have been fixed.
780    9.  Added --match-limit and --recursion-limit to pcregrep.
782    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
784    11. When the -o option was used, pcregrep was setting a return code of 1, even
785        when matches were found, and --line-buffered was not being honoured.
787    12. Added an optional parentheses number to the -o and --only-matching options
788        of pcregrep.
790    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
791        can match an empty string. The code to do it in pcretest and pcredemo
792        needed fixing:
794        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
795            only one byte after an empty string match just before CRLF (this case
796            just got forgotten; "any" and "anycrlf" were OK).
798        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
799            mode when an empty string match preceded an ASCII character followed by
800            a non-ASCII character. (The code for advancing by one character rather
801            than one byte was nonsense.)
803        (c) The pcredemo.c sample program did not have any code at all to handle
804            the cases when CRLF is a valid newline sequence.
806    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
807        as a starting offset was within the subject string. There is now a new
808        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
809        negative or greater than the length of the string. In order to test this,
810        pcretest is extended to allow the setting of negative starting offsets.
812    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
813        starting offset points to the beginning of a UTF-8 character was
814        unnecessarily clumsy. I tidied it up.
816    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
817        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
819    17. Nobody had reported that the --include_dir option, which was added in
820        release 7.7 should have been called --include-dir (hyphen, not underscore)
821        for compatibility with GNU grep. I have changed it to --include-dir, but
822        left --include_dir as an undocumented synonym, and the same for
823        --exclude-dir, though that is not available in GNU grep, at least as of
824        release 2.5.4.
826    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
827        characters from a string of bytes) have been redefined so as not to use
828        loops, in order to improve performance in some environments. At the same
829        time, I abstracted some of the common code into auxiliary macros to save
830        repetition (this should not affect the compiled code).
832    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
833        compile-time error is now given if \c is not followed by an ASCII
834        character, that is, a byte less than 128. (In EBCDIC mode, the code is
835        different, and any byte value is allowed.)
837    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
838        START_OPTIMIZE option, which is now allowed at compile time - but just
839        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
840        to pcregrep and other applications that have no direct access to PCRE
841        options. The new /Y option in pcretest sets this option when calling
842        pcre_compile().
844    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
845        back references. Groups containing recursive back references were forced to
846        be atomic by that change, but in the case of named groups, the amount of
847        memory required was incorrectly computed, leading to "Failed: internal
848        error: code overflow". This has been fixed.
850    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
851        pcretest.c, to avoid build problems in some Borland environments.
854    Version 8.10 25-Jun-2010
855    ------------------------
857    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
858        THEN.
860    2.  (*ACCEPT) was not working when inside an atomic group.
862    3.  Inside a character class, \B is treated as a literal by default, but
863        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
864        causes the error). The code is unchanged, but I tidied the documentation.
866    4.  Inside a character class, PCRE always treated \R and \X as literals,
867        whereas Perl faults them if its -w option is set. I have changed PCRE so
868        that it faults them when PCRE_EXTRA is set.
870    5.  Added support for \N, which always matches any character other than
871        newline. (It is the same as "." when PCRE_DOTALL is not set.)
873    6.  When compiling pcregrep with newer versions of gcc which may have
874        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
875        declared with attribute warn_unused_result" were given. Just casting the
876        result to (void) does not stop the warnings; a more elaborate fudge is
877        needed. I've used a macro to implement this.
879    7.  Minor change to pcretest.c to avoid a compiler warning.
881    8.  Added four artifical Unicode properties to help with an option to make
882        \s etc use properties (see next item). The new properties are: Xan
883        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
885    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
886        use Unicode properties. (*UCP) at the start of a pattern can be used to set
887        this option. Modified pcretest to add /W to test this facility. Added
888        REG_UCP to make it available via the POSIX interface.
890    10. Added --line-buffered to pcregrep.
892    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
893        studied, and the match started with a letter with a code point greater than
894        127 whose first byte was different to the first byte of the other case of
895        the letter, the other case of this starting letter was not recognized
896        (#976).
898    12. If a pattern that was studied started with a repeated Unicode property
899        test, for example, \p{Nd}+, there was the theoretical possibility of
900        setting up an incorrect bitmap of starting bytes, but fortunately it could
901        not have actually happened in practice until change 8 above was made (it
902        added property types that matched character-matching opcodes).
904    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
905        possible starting bytes for non-anchored patterns.
907    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
908        \R, and also a number of cases that involve Unicode properties, both
909        explicit and implicit when PCRE_UCP is set.
911    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
912        input, it could crash or give wrong results if characters with values
913        greater than 0xc0 were present in the subject string. (Detail: it assumed
914        UTF-8 input when processing these items.)
916    16. Added a lot of (int) casts to avoid compiler warnings in systems where
917        size_t is 64-bit (#991).
919    17. Added a check for running out of memory when PCRE is compiled with
920        --disable-stack-for-recursion (#990).
922    18. If the last data line in a file for pcretest does not have a newline on
923        the end, a newline was missing in the output.
925    19. The default pcre_chartables.c file recognizes only ASCII characters (values
926        less than 128) in its various bitmaps. However, there is a facility for
927        generating tables according to the current locale when PCRE is compiled. It
928        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
929        characters, are recognized by isspace() and therefore were getting set in
930        these tables, and indeed these tables seem to approximate to ISO 8859. This
931        caused a problem in UTF-8 mode when pcre_study() was used to create a list
932        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
933        which of course cannot start UTF-8 characters. I have changed the code so
934        that only real ASCII characters (less than 128) and the correct starting
935        bytes for UTF-8 encodings are set for characters greater than 127 when in
936        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
937        altogether.)
939    20. Added the /T option to pcretest so as to be able to run tests with non-
940        standard character tables, thus making it possible to include the tests
941        used for 19 above in the standard set of tests.
943    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
944        reference to a subpattern the other side of a comment that contains an
945        opening parenthesis caused either an internal compiling error, or a
946        reference to the wrong subpattern.
949    Version 8.02 19-Mar-2010
950    ------------------------
952    1.  The Unicode data tables have been updated to Unicode 5.2.0.
954    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
955        configured.
957    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
958        original author of that file, following a query about its status.
960    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
961        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
963    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
964        quantifier applied to a forward-referencing subroutine call, could compile
965        incorrect code or give the error "internal error: previously-checked
966        referenced subpattern not found".
968    6.  Both MS Visual Studio and Symbian OS have problems with initializing
969        variables to point to external functions. For these systems, therefore,
970        pcre_malloc etc. are now initialized to local functions that call the
971        relevant global functions.
973    7.  There were two entries missing in the vectors called coptable and poptable
974        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
975        I've fixed the data, and added a kludgy way of testing at compile time that
976        the lengths are correct (equal to the number of opcodes).
978    8.  Following on from 7, I added a similar kludge to check the length of the
979        eint vector in pcreposix.c.
981    9.  Error texts for pcre_compile() are held as one long string to avoid too
982        much relocation at load time. To find a text, the string is searched,
983        counting zeros. There was no check for running off the end of the string,
984        which could happen if a new error number was added without updating the
985        string.
987    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
989    11. \K was not working if it appeared in an atomic group or in a group that
990        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
991        \K is "not well defined" if used in an assertion. PCRE now accepts it if
992        the assertion is positive, but not if it is negative.
994    12. Change 11 fortuitously reduced the size of the stack frame used in the
995        "match()" function of pcre_exec.c by one pointer. Forthcoming
996        implementation of support for (*MARK) will need an extra pointer on the
997        stack; I have reserved it now, so that the stack frame size does not
998        decrease.
1000    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
1001        item in branch that calls a recursion is a subroutine call - as in the
1002        second branch in the above example - was incorrectly given the compile-
1003        time error "recursive call could loop indefinitely" because pcre_compile()
1004        was not correctly checking the subroutine for matching a non-empty string.
1006    14. The checks for overrunning compiling workspace could trigger after an
1007        overrun had occurred. This is a "should never occur" error, but it can be
1008        triggered by pathological patterns such as hundreds of nested parentheses.
1009        The checks now trigger 100 bytes before the end of the workspace.
1011    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
1014    Version 8.01 19-Jan-2010
1015    ------------------------
1017    1.  If a pattern contained a conditional subpattern with only one branch (in
1018        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
1019        computed the wrong minimum data length (which is of course zero for such
1020        subpatterns). This could cause incorrect "no match" results.
1022    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
1023        the pattern is reset in the first branch, pcre_compile() failed with
1024        "internal error: code overflow at offset...". This happened only when
1025        the reset was to the original external option setting. (An optimization
1026        abstracts leading options settings into an external setting, which was the
1027        cause of this.)
1029    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
1030        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
1031        assertion pattern did not match (meaning that the assertion was true), it
1032        was incorrectly treated as false if the SKIP had been reached during the
1033        matching. This also applied to assertions used as conditions.
1035    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
1036        assertion subpattern, including such a pattern used as a condition,
1037        unpredictable results occurred, instead of the error return
1040    5.  The C++ GlobalReplace function was not working like Perl for the special
1041        situation when an empty string is matched. It now does the fancy magic
1042        stuff that is necessary.
1044    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
1045        removed. (These were left over from very, very early versions of PCRE.)
1047    7.  Some cosmetic changes to the code to make life easier when compiling it
1048        as part of something else:
1050        (a) Change DEBUG to PCRE_DEBUG.
1052        (b) In pcre_compile(), rename the member of the "branch_chain" structure
1053            called "current" as "current_branch", to prevent a collision with the
1054            Linux macro when compiled as a kernel module.
1056        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
1057            prevent a collision with the Linux macro when compiled as a kernel
1058            module.
1060    8.  In pcre_compile() there are some checks for integer overflows that used to
1061        cast potentially large values to (double). This has been changed to that
1062        when building, a check for int64_t is made, and if it is found, it is used
1063        instead, thus avoiding the use of floating point arithmetic. (There is no
1064        other use of FP in PCRE.) If int64_t is not found, the fallback is to
1065        double.
1067    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
1068        2005 (difference between two addresses compared to an unsigned value).
1070    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
1071        custom one, because of the following reported problem in Windows:
1073          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
1074              under Win32.
1075          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
1076              therefore missing the function definition.
1077          - The compiler thus generates a "C" signature for the test function.
1078          - The linker fails to find the "C" function.
1079          - PCRE fails to configure if asked to do so against libbz2.
1081    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
1082        messages were output:
1084          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
1085          rerunning libtoolize, to keep the correct libtool macros in-tree.
1086          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
1088        I have done both of these things.
1090    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
1091        most of the time, it *can* run out if it is given a pattern that contains a
1092        runaway infinite recursion. I updated the discussion in the pcrestack man
1093        page.
1095    13. Now that we have gone to the x.xx style of version numbers, the minor
1096        version may start with zero. Using 08 or 09 is a bad idea because users
1097        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
1098        interpreted as invalid octal numbers. I've updated the previous comment in
1099        configure.ac, and also added a check that gives an error if 08 or 09 are
1100        used.
1102    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
1103        causing partial matching to fail when the end of the subject matched \W
1104        in a UTF-8 pattern where \W was quantified with a minimum of 3.
1106    15. There were some discrepancies between the declarations in pcre_internal.h
1107        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
1108        their definitions. The declarations used "const uschar *" and the
1109        definitions used USPTR. Even though USPTR is normally defined as "const
1110        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
1111        reported that: "This difference in casting confuses some C++ compilers, for
1112        example, SunCC recognizes above declarations as different functions and
1113        generates broken code for hbpcre." I have changed the declarations to use
1114        USPTR.
1116    16. GNU libtool is named differently on some systems. The autogen.sh script now
1117        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
1118        (FreeBSD).
1120    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
1121        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
1122        comment: "Figure out how to create a longlong from a string: strtoll and
1123        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
1124        instance, but it only takes 2 args instead of 3!"
1126    18. A subtle bug concerned with back references has been fixed by a change of
1127        specification, with a corresponding code fix. A pattern such as
1128        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
1129        refers, was giving matches when it shouldn't. For example, xa=xaaa would
1130        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
1131        same bug. Such groups have to be quantified to be useful, or contained
1132        inside another quantified group. (If there's no repetition, the reference
1133        can never match.) The problem arises because, having left the group and
1134        moved on to the rest of the pattern, a later failure that backtracks into
1135        the group uses the captured value from the final iteration of the group
1136        rather than the correct earlier one. I have fixed this in PCRE by forcing
1137        any group that contains a reference to itself to be an atomic group; that
1138        is, there cannot be any backtracking into it once it has completed. This is
1139        similar to recursive and subroutine calls.
1142    Version 8.00 19-Oct-09
1143    ----------------------
1145    1.  The table for translating pcre_compile() error codes into POSIX error codes
1146        was out-of-date, and there was no check on the pcre_compile() error code
1147        being within the table. This could lead to an OK return being given in
1148        error.
1150    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
1151        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
1152        in a Windows environment.
1154    3.  The pcregrep --count option prints the count for each file even when it is
1155        zero, as does GNU grep. However, pcregrep was also printing all files when
1156        --files-with-matches was added. Now, when both options are given, it prints
1157        counts only for those files that have at least one match. (GNU grep just
1158        prints the file name in this circumstance, but including the count seems
1159        more useful - otherwise, why use --count?) Also ensured that the
1160        combination -clh just lists non-zero counts, with no names.
1162    4.  The long form of the pcregrep -F option was incorrectly implemented as
1163        --fixed_strings instead of --fixed-strings. This is an incompatible change,
1164        but it seems right to fix it, and I didn't think it was worth preserving
1165        the old behaviour.
1167    5.  The command line items --regex=pattern and --regexp=pattern were not
1168        recognized by pcregrep, which required --regex pattern or --regexp pattern
1169        (with a space rather than an '='). The man page documented the '=' forms,
1170        which are compatible with GNU grep; these now work.
1172    6.  No libpcreposix.pc file was created for pkg-config; there was just
1173        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
1175    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
1176        when UCP support is not needed, by modifying the Python script that
1177        generates it from Unicode data files. This should not matter if the module
1178        is correctly used as a library, but I received one complaint about 50K of
1179        unwanted data. My guess is that the person linked everything into his
1180        program rather than using a library. Anyway, it does no harm.
1182    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
1183        was a minimum greater than 1 for a wide character in a possessive
1184        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
1185        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
1186        character. Chaos in the form of incorrect output or a compiling loop could
1187        result.
1189    9.  The restrictions on what a pattern can contain when partial matching is
1190        requested for pcre_exec() have been removed. All patterns can now be
1191        partially matched by this function. In addition, if there are at least two
1192        slots in the offset vector, the offset of the earliest inspected character
1193        for the match and the offset of the end of the subject are set in them when
1194        PCRE_ERROR_PARTIAL is returned.
1196    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
1197        synonymous with PCRE_PARTIAL, for backwards compatibility, and
1198        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
1199        and may be more useful for multi-segment matching.
1201    11. Partial matching with pcre_exec() is now more intuitive. A partial match
1202        used to be given if ever the end of the subject was reached; now it is
1203        given only if matching could not proceed because another character was
1204        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
1205        string "Z", which now yields "no match" instead of "partial match". In the
1206        case of pcre_dfa_exec(), "no match" is given if every matching path for the
1207        final character ended with (*FAIL).
1209    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
1210        if the pattern had a "must contain" character that was already found in the
1211        earlier partial match, unless partial matching was again requested. For
1212        example, with the pattern /dog.(body)?/, the "must contain" character is
1213        "g". If the first part-match was for the string "dog", restarting with
1214        "sbody" failed. This bug has been fixed.
1216    13. The string returned by pcre_dfa_exec() after a partial match has been
1217        changed so that it starts at the first inspected character rather than the
1218        first character of the match. This makes a difference only if the pattern
1219        starts with a lookbehind assertion or \b or \B (\K is not supported by
1220        pcre_dfa_exec()). It's an incompatible change, but it makes the two
1221        matching functions compatible, and I think it's the right thing to do.
1223    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
1224        so that the demonstration program is easily available in environments where
1225        PCRE has not been installed from source.
1227    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
1228        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
1229        library.
1231    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
1232        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
1233        is not the first non-POSIX option to be added. Clearly some people find
1234        these options useful.
1236    17. If a caller to the POSIX matching function regexec() passes a non-zero
1237        value for nmatch with a NULL value for pmatch, the value of
1238        nmatch is forced to zero.
1240    18. RunGrepTest did not have a test for the availability of the -u option of
1241        the diff command, as RunTest does. It now checks in the same way as
1242        RunTest, and also checks for the -b option.
1244    19. If an odd number of negated classes containing just a single character
1245        interposed, within parentheses, between a forward reference to a named
1246        subpattern and the definition of the subpattern, compilation crashed with
1247        an internal error, complaining that it could not find the referenced
1248        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
1249        [The bug was that it was starting one character too far in when skipping
1250        over the character class, thus treating the ] as data rather than
1251        terminating the class. This meant it could skip too much.]
1253    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
1254        /g option in pcretest when the pattern contains \K, which makes it possible
1255        to have an empty string match not at the start, even when the pattern is
1256        anchored. Updated pcretest and pcredemo to use this option.
1258    21. If the maximum number of capturing subpatterns in a recursion was greater
1259        than the maximum at the outer level, the higher number was returned, but
1260        with unset values at the outer level. The correct (outer level) value is
1261        now given.
1263    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
1264        PCRE did not set those parentheses (unlike Perl). I have now found a way to
1265        make it do so. The string so far is captured, making this feature
1266        compatible with Perl.
1268    23. The tests have been re-organized, adding tests 11 and 12, to make it
1269        possible to check the Perl 5.10 features against Perl 5.10.
1271    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
1272        pattern matches a fixed length string. PCRE did not allow this; now it
1273        does. Neither allows recursion.
1275    25. I finally figured out how to implement a request to provide the minimum
1276        length of subject string that was needed in order to match a given pattern.
1277        (It was back references and recursion that I had previously got hung up
1278        on.) This code has now been added to pcre_study(); it finds a lower bound
1279        to the length of subject needed. It is not necessarily the greatest lower
1280        bound, but using it to avoid searching strings that are too short does give
1281        some useful speed-ups. The value is available to calling programs via
1282        pcre_fullinfo().
1284    26. While implementing 25, I discovered to my embarrassment that pcretest had
1285        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
1286        study optimizations had never been tested with that matching function.
1287        Oops. What is worse, even when it was passed study data, there was a bug in
1288        pcre_dfa_exec() that meant it never actually used it. Double oops. There
1289        were also very few tests of studied patterns with pcre_dfa_exec().
1291    27. If (?| is used to create subpatterns with duplicate numbers, they are now
1292        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
1293        on the other side of the coin, they are no longer allowed to have different
1294        names, because these cannot be distinguished in PCRE, and this has caused
1295        confusion. (This is a difference from Perl.)
1297    28. When duplicate subpattern names are present (necessarily with different
1298        numbers, as required by 27 above), and a test is made by name in a
1299        conditional pattern, either for a subpattern having been matched, or for
1300        recursion in such a pattern, all the associated numbered subpatterns are
1301        tested, and the overall condition is true if the condition is true for any
1302        one of them. This is the way Perl works, and is also more like the way
1303        testing by number works.
1306    Version 7.9 11-Apr-09
1307    ---------------------
1309    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
1310        (pcretest), all targets were linked against these libraries. This included
1311        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
1312        libraries. This caused unwanted dependencies to be created. This problem
1313        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
1314        pcretest is linked with readline.
1316    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
1317        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
1318        moved outside it again, because FALSE and TRUE are already defined in AIX,
1319        but BOOL is not.
1321    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
1322        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
1324    4.  The pcregrep documentation said spaces were inserted as well as colons (or
1325        hyphens) following file names and line numbers when outputting matching
1326        lines. This is not true; no spaces are inserted. I have also clarified the
1327        wording for the --colour (or --color) option.
1329    5.  In pcregrep, when --colour was used with -o, the list of matching strings
1330        was not coloured; this is different to GNU grep, so I have changed it to be
1331        the same.
1333    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
1334        each matching line was coloured. Now it goes on to look for further matches
1335        of any of the test patterns, which is the same behaviour as GNU grep.
1337    7.  A pattern that could match an empty string could cause pcregrep to loop; it
1338        doesn't make sense to accept an empty string match in pcregrep, so I have
1339        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1340        seems to be how GNU grep behaves.
1342    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
1343        start or after a newline", because the conditional assertion was not being
1344        correctly handled. The rule now is that both the assertion and what follows
1345        in the first alternative must satisfy the test.
1347    9.  If auto-callout was enabled in a pattern with a conditional group whose
1348        condition was an assertion, PCRE could crash during matching, both with
1349        pcre_exec() and pcre_dfa_exec().
1351    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
1352        used for matching.
1354    11. Unicode property support in character classes was not working for
1355        characters (bytes) greater than 127 when not in UTF-8 mode.
1357    12. Added the -M command line option to pcretest.
1359    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
1361    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
1363    16. Added comments and documentation about mis-use of no_arg in the C++
1364        wrapper.
1366    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
1367        from Martin Jerabek that uses macro names for all relevant character and
1368        string constants.
1370    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
1371        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
1372        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
1373        these, but not everybody uses configure.
1375    19. A conditional group that had only one branch was not being correctly
1376        recognized as an item that could match an empty string. This meant that an
1377        enclosing group might also not be so recognized, causing infinite looping
1378        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
1379        with the subject "ab", where knowledge that the repeated group can match
1380        nothing is needed in order to break the loop.
1382    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
1383        exec(), but without supplying a callout function, matching went wrong.
1385    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
1386        leak if the size of the offset vector was greater than 30. When the vector
1387        is smaller, the saved offsets during recursion go onto a local stack
1388        vector, but for larger vectors malloc() is used. It was failing to free
1389        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
1390        error, in fact).
1392    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
1393        heapframe that is used only when UTF-8 support is enabled. This caused no
1394        problem, but was untidy.
1396    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
1397        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
1398        included within another project.
1400    24. Steven Van Ingelgem's patches to add more options to the CMake support,
1401        slightly modified by me:
1403          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
1404              not building pcregrep.
1406          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
1407              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
1409    25. Forward references, both numeric and by name, in patterns that made use of
1410        duplicate group numbers, could behave incorrectly or give incorrect errors,
1411        because when scanning forward to find the reference group, PCRE was not
1412        taking into account the duplicate group numbers. A pattern such as
1413        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
1415    26. Changed a few more instances of "const unsigned char *" to USPTR, making
1416        the feature of a custom pointer more persuasive (as requested by a user).
1418    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
1419        pcretest.c, inside #ifndefs, because it seems they are sometimes already
1420        pre-defined.
1422    28. Added support for (*UTF8) at the start of a pattern.
1424    29. Arrange for flags added by the "release type" setting in CMake to be shown
1425        in the configuration summary.
1428    Version 7.8 05-Sep-08
1429    ---------------------
1431    1.  Replaced UCP searching code with optimized version as implemented for Ad
1432        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
1433        stage table and inline lookup instead of a function, giving speed ups of 2
1434        to 5 times on some simple patterns that I tested. Permission was given to
1435        distribute the MultiStage2.py script that generates the tables (it's not in
1436        the tarball, but is in the Subversion repository).
1438    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
1439        scripts.
1441    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
1442        a group with a zero qualifier. The result of the study could be incorrect,
1443        or the function might crash, depending on the pattern.
1445    4.  Caseless matching was not working for non-ASCII characters in back
1446        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
1447        It now works when Unicode Property Support is available.
1449    5.  In pcretest, an escape such as \x{de} in the data was always generating
1450        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
1451        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
1452        truncation.
1454    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
1456    7.  Added two (int) casts to pcregrep when printing the difference of two
1457        pointers, in case they are 64-bit values.
1459    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
1460        test 2 if it fails.
1462    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
1463        and a #define of that name to empty if it is not externally set. This is to
1464        allow users of MSVC to set it if necessary.
1466    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
1467        the convenience functions in the pcre_get.c source file.
1469    11. An option change at the start of a pattern that had top-level alternatives
1470        could cause overwriting and/or a crash. This command provoked a crash in
1471        some environments:
1473          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
1475        This potential security problem was recorded as CVE-2008-2371.
1477    12. For a pattern where the match had to start at the beginning or immediately
1478        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
1479        pcre_dfa_exec() could read past the end of the passed subject if there was
1480        no match. To help with detecting such bugs (e.g. with valgrind), I modified
1481        pcretest so that it places the subject at the end of its malloc-ed buffer.
1483    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
1484        exec() might read past the end of the data buffer in UTF-8 mode.
1486    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
1487        the data contained the byte 0x85 as part of a UTF-8 character within its
1488        first line. This applied both to normal and DFA matching.
1490    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
1491        /^[^d]*?$/8 failed to match "abc".
1493    16. Added a missing copyright notice to pcrecpp_internal.h.
1495    17. Make it more clear in the documentation that values returned from
1496        pcre_exec() in ovector are byte offsets, not character counts.
1498    18. Tidied a few places to stop certain compilers from issuing warnings.
1500    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
1501        supplied by Stefan Weber. I made a further small update for 7.8 because
1502        there is a change of source arrangements: the pcre_searchfuncs.c module is
1503        replaced by pcre_ucd.c.
1506    Version 7.7 07-May-08
1507    ---------------------
1509    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
1510        a string to a long long, pretend we don't even have a long long." This is
1511        done by checking for the strtoq, strtoll, and _strtoi64 functions.
1513    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
1514        pre-7.6 versions, which defined a global no_arg variable instead of putting
1515        it in the RE class. (See also #8 below.)
1517    3.  Remove a line of dead code, identified by coverity and reported by Nuno
1518        Lopes.
1520    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
1522        (1) The include/exclude patterns were being applied to the whole pathnames
1523            of files, instead of just to the final components.
1525        (2) If there was more than one level of directory, the subdirectories were
1526            skipped unless they satisfied the include/exclude conditions. This is
1527            inconsistent with GNU grep (and could even be seen as contrary to the
1528            pcregrep specification - which I improved to make it absolutely clear).
1529            The action now is always to scan all levels of directory, and just
1530            apply the include/exclude patterns to regular files.
1532    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
1533        --exclude_dir in the tests to avoid scanning .svn directories.
1535    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
1536        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
1537        doesn't support NULs in patterns.
1539    7.  Added some missing "const"s to declarations of static tables in
1540        pcre_compile.c and pcre_dfa_exec.c.
1542    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
1543        caused by fix #2  above. (Subsequently also a second patch to fix the
1544        first patch. And a third patch - this was a messy problem.)
1546    9.  Applied Craig's patch to remove the use of push_back().
1548    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
1549        matching function regexec().
1551    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
1552        which, however, unlike Perl's \g{...}, are subroutine calls, not back
1553        references. PCRE supports relative numbers with this syntax (I don't think
1554        Oniguruma does).
1556    12. Previously, a group with a zero repeat such as (...){0} was completely
1557        omitted from the compiled regex. However, this means that if the group
1558        was called as a subroutine from elsewhere in the pattern, things went wrong
1559        (an internal error was given). Such groups are now left in the compiled
1560        pattern, with a new opcode that causes them to be skipped at execution
1561        time.
1563    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
1564        to the way PCRE behaves:
1566        (a) A lone ] character is dis-allowed (Perl treats it as data).
1568        (b) A back reference to an unmatched subpattern matches an empty string
1569            (Perl fails the current match path).
1571        (c) A data ] in a character class must be notated as \] because if the
1572            first data character in a class is ], it defines an empty class. (In
1573            Perl it is not possible to have an empty class.) The empty class []
1574            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
1575            The negative empty class [^] matches any one character, independently
1576            of the DOTALL setting.
1578    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
1579        non-existent subpattern following a character class starting with ']' and
1580        containing () gave an internal compiling error instead of "reference to
1581        non-existent subpattern". Fortunately, when the pattern did exist, the
1582        compiled code was correct. (When scanning forwards to check for the
1583        existencd of the subpattern, it was treating the data ']' as terminating
1584        the class, so got the count wrong. When actually compiling, the reference
1585        was subsequently set up correctly.)
1587    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
1588        it was being rejected as not supported by pcre_dfa_exec(), even though
1589        other assertions are supported. I have made pcre_dfa_exec() support
1590        (*FAIL).
1592    16. The implementation of 13c above involved the invention of a new opcode,
1593        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
1594        cannot be changed at match time, I realized I could make a small
1595        improvement to matching performance by compiling OP_ALLANY instead of
1596        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
1597        on the OP_ANY path.
1599    17. Compiling pcretest on Windows with readline support failed without the
1600        following two fixes: (1) Make the unistd.h include conditional on
1601        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
1603    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
1604        ncurses library to be included for pcretest when ReadLine support is
1605        requested, but also to allow for it to be overridden. This patch came from
1606        Daniel Bergström.
1608    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
1609        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
1610        any errors with the current Unicode tables. Thanks to Peter Kankowski for
1611        spotting this.
1614    Version 7.6 28-Jan-08
1615    ---------------------
1617    1.  A character class containing a very large number of characters with
1618        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
1619        overflow.
1621    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
1622        HAVE_LONG_LONG is not defined.
1624    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
1625        bring them up to date and include new features. This patch includes:
1627        - Fixed PH's badly added libz and libbz2 support.
1628        - Fixed a problem with static linking.
1629        - Added pcredemo. [But later removed - see 7 below.]
1630        - Fixed dftables problem and added an option.
1631        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
1632            HAVE_LONG_LONG.
1633        - Added readline support for pcretest.
1634        - Added an listing of the option settings after cmake has run.
1636    4.  A user submitted a patch to Makefile that makes it easy to create
1637        "pcre.dll" under mingw when using Configure/Make. I added stuff to
1638        Makefile.am that cause it to include this special target, without
1639        affecting anything else. Note that the same mingw target plus all
1640        the other distribution libraries and programs are now supported
1641        when configuring with CMake (see 6 below) instead of with
1642        Configure/Make.
1644    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
1645        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
1646        exported in the Windows port". It has not yet been confirmed that the patch
1647        solves the problem, but it does no harm.
1649    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
1650        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
1651        with CMake, and also correct the comment about stack recursion.
1653    7.  Remove the automatic building of pcredemo from the ./configure system and
1654        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
1655        of a program that users should build themselves after PCRE is installed, so
1656        building it automatically is not really right. What is more, it gave
1657        trouble in some build environments.
1659    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
1662    Version 7.5 10-Jan-08
1663  ---------------------  ---------------------
1665  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
1666      values in parens when parsing an RE using the C++ wrapper."      values in parens when parsing an RE using the C++ wrapper."
1668  2.  Negative specials like \S did not work in character classes in UTF-8 mode.  2.  Negative specials like \S did not work in character classes in UTF-8 mode.
1669      Characters greater than 255 were excluded from the class instead of being      Characters greater than 255 were excluded from the class instead of being
1670      included.      included.
1672  3.  The same bug as (2) above applied to negated POSIX classes such as  3.  The same bug as (2) above applied to negated POSIX classes such as
1673      [:^space:].      [:^space:].
1675  4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it  4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
1676      defined or documented. It seems to have been a typo for PCRE_STATIC, so      defined or documented. It seems to have been a typo for PCRE_STATIC, so
1677      I have changed it.      I have changed it.
1679  5.  The construct (?&) was not diagnosed as a syntax error (it referenced the  5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
1680      first named subpattern) and a construct such as (?&a) would reference the      first named subpattern) and a construct such as (?&a) would reference the
1681      first named subpattern whose name started with "a" (in other words, the      first named subpattern whose name started with "a" (in other words, the
1682      length check was missing).      length check was missing). Both these problems are fixed. "Subpattern name
1683        expected" is now given for (?&) (a zero-length name), and this patch also
1684        makes it give the same error for \k'' (previously it complained that that
1685        was a reference to a non-existent subpattern).
1687  6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;  6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
1688      this is right because (?- can be followed by option settings as well as by      this is right because (?- can be followed by option settings as well as by
1689      digits. I have, however, made the messages clearer.      digits. I have, however, made the messages clearer.
1691    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
1692        than the number used in the conditional) now cause a compile-time error.
1693        This is actually not compatible with Perl, which accepts such patterns, but
1694        treats the conditional as always being FALSE (as PCRE used to), but it
1695        seems to me that giving a diagnostic is better.
1697    8.  Change "alphameric" to the more common word "alphanumeric" in comments
1698        and messages.
1700    9.  Fix two occurrences of "backslash" in comments that should have been
1701        "backspace".
1703    10. Remove two redundant lines of code that can never be obeyed (their function
1704        was moved elsewhere).
1706    11. The program that makes PCRE's Unicode character property table had a bug
1707        which caused it to generate incorrect table entries for sequences of
1708        characters that have the same character type, but are in different scripts.
1709        It amalgamated them into a single range, with the script of the first of
1710        them. In other words, some characters were in the wrong script. There were
1711        thirteen such cases, affecting characters in the following ranges:
1713          U+002b0 - U+002c1
1714          U+0060c - U+0060d
1715          U+0061e - U+00612
1716          U+0064b - U+0065e
1717          U+0074d - U+0076d
1718          U+01800 - U+01805
1719          U+01d00 - U+01d77
1720          U+01d9b - U+01dbf
1721          U+0200b - U+0200f
1722          U+030fc - U+030fe
1723          U+03260 - U+0327f
1724          U+0fb46 - U+0fbb1
1725          U+10450 - U+1049d
1727    12. The -o option (show only the matching part of a line) for pcregrep was not
1728        compatible with GNU grep in that, if there was more than one match in a
1729        line, it showed only the first of them. It now behaves in the same way as
1730        GNU grep.
1732    13. If the -o and -v options were combined for pcregrep, it printed a blank
1733        line for every non-matching line. GNU grep prints nothing, and pcregrep now
1734        does the same. The return code can be used to tell if there were any
1735        non-matching lines.
1737    14. Added --file-offsets and --line-offsets to pcregrep.
1739    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
1740        infinitely looping recursion. The bug was that positive lookaheads were not
1741        being skipped when checking for a possible empty match (negative lookaheads
1742        and both kinds of lookbehind were skipped).
1744    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
1745        inclusion of <windows.h> to before rather than after the definition of
1746        INVALID_FILE_ATTRIBUTES (patch from David Byron).
1748    17. Specifying a possessive quantifier with a specific limit for a Unicode
1749        character property caused pcre_compile() to compile bad code, which led at
1750        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
1751        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
1752        caused the error; without that there was no problem.
1754    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
1756    19. Added --enable-pcretest-libreadline.
1758    20. In pcrecpp.cc, the variable 'count' was incremented twice in
1759        RE::GlobalReplace(). As a result, the number of replacements returned was
1760        double what it should be. I removed one of the increments, but Craig sent a
1761        later patch that removed the other one (the right fix) and added unit tests
1762        that check the return values (which was not done before).
1764    21. Several CMake things:
1766        (1) Arranged that, when cmake is used on Unix, the libraries end up with
1767            the names libpcre and libpcreposix, not just pcre and pcreposix.
1769        (2) The above change means that pcretest and pcregrep are now correctly
1770            linked with the newly-built libraries, not previously installed ones.
1774    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
1775        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
1776        UTF-8 newline character). The key issue is that the pattern starts .*;
1777        this means that the match must be either at the beginning, or after a
1778        newline. The bug was in the code for advancing after a failed match and
1779        checking that the new position followed a newline. It was not taking
1780        account of UTF-8 characters correctly.
1782    23. PCRE was behaving differently from Perl in the way it recognized POSIX
1783        character classes. PCRE was not treating the sequence [:...:] as a
1784        character class unless the ... were all letters. Perl, however, seems to
1785        allow any characters between [: and :], though of course it rejects as
1786        unknown any "names" that contain non-letters, because all the known class
1787        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
1788        for example, whereas PCRE did not - it did not recognize a POSIX character
1789        class. This seemed a bit dangerous, so the code has been changed to be
1790        closer to Perl. The behaviour is not identical to Perl, because PCRE will
1791        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
1792        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
1793        Perl does, and where it didn't before.
1795    24. Rewrite so as to remove the single use of %n from pcregrep because in some
1796        Windows environments %n is disabled by default.
1799  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07
1800  ---------------------  ---------------------

Removed from v.269  
changed lines
  Added in v.979

  ViewVC Help
Powered by ViewVC 1.1.5