ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.253  
changed lines
  Added in v.936

  ViewVC Help
Powered by ViewVC 1.1.5