ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.285  
changed lines
  Added in v.931

  ViewVC Help
Powered by ViewVC 1.1.5