ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 399 by ph10, Sat Mar 21 12:34:15 2009 UTC revision 932 by ph10, Fri Feb 24 18:54:43 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.9 xx-xxx-09  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.)
53    Version 8.30 04-February-2012
54    -----------------------------
56    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
57        name is defined in ctype.h.
59    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
60        only in quite long subpatterns.
62    3.  Removed the function pcre_info(), which has been obsolete and deprecated
63        since it was replaced by pcre_fullinfo() in February 2000.
65    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
66        match a (*MARK), and the match failed at the start of the subject, a
67        reference to memory before the start of the subject could occur. This bug
68        was introduced by fix 17 of release 8.21.
70    5.  A reference to an unset group with zero minimum repetition was giving
71        totally wrong answers (in non-JavaScript-compatibility mode). For example,
72        /(another)?(\1?)test/ matched against "hello world test". This bug was
73        introduced in release 8.13.
75    6.  Add support for 16-bit character strings (a large amount of work involving
76        many changes and refactorings).
78    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
79        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
80        from a file.
82    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
83        rounding is not applied in this particular case).
85    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
86        if they appear, or are escaped, in patterns.
88    10. Get rid of a number of -Wunused-but-set-variable warnings.
90    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
91        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
92        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
93        also returns the mark "x". This bug applied to capturing parentheses,
94        non-capturing parentheses, and atomic parentheses. It also applied to some
95        assertions.
97    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
98        information out of configure.ac instead of relying on pcre.h.generic, which
99        is not stored in the repository.
101    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
102        -lreadline.
104    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
106    15. Applied Graycode's patch to put the top-level frame on the stack rather
107        than the heap when not using the stack for recursion. This gives a
108        performance improvement in many cases when recursion is not deep.
110    16. Experimental code added to "pcretest -C" to output the stack frame size.
113    Version 8.21 12-Dec-2011
114    ------------------------
116    1.  Updating the JIT compiler.
118    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
119        are added as well.
121    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
122        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
123        calling _pcre_jit_exec. Some extra comments are added.
125    4.  (*MARK) settings inside atomic groups that do not contain any capturing
126        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
127        was introduced by change 18 for 8.20.
129    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
130        ECMA-262 standard.
132    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
133        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
134        This bug was probably introduced by change 9 of 8.13.
136    7.  While fixing 6 above, I noticed that a number of other items were being
137        incorrectly rejected as "not fixed length". This arose partly because newer
138        opcodes had not been added to the fixed-length checking code. I have (a)
139        corrected the bug and added tests for these items, and (b) arranged for an
140        error to occur if an unknown opcode is encountered while checking for fixed
141        length instead of just assuming "not fixed length". The items that were
142        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
143        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
144        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
146    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
147        being incorrectly compiled and would have given unpredicatble results.
149    9.  A possessively repeated subpattern with minimum repeat count greater than
150        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
151        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
152        the first (A) could occur when it should not.
154    10. Add a cast and remove a redundant test from the code.
156    11. JIT should use pcre_malloc/pcre_free for allocation.
158    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
159        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
160        is anything other than /usr, -L is still shown).
162    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
164    14. Perl does not support \N without a following name in a [] class; PCRE now
165        also gives an error.
167    15. If a forward reference was repeated with an upper limit of around 2000,
168        it caused the error "internal error: overran compiling workspace". The
169        maximum number of forward references (including repeats) was limited by the
170        internal workspace, and dependent on the LINK_SIZE. The code has been
171        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
172        the default depends on LINK_SIZE. There is a new upper limit (for safety)
173        of around 200,000 forward references. While doing this, I also speeded up
174        the filling in of repeated forward references.
176    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
177        incorrectly expecting the subject to contain another "a" after the start.
179    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
180        in the match, the SKIP should be ignored. This was not happening; instead
181        the SKIP was being treated as NOMATCH. For patterns such as
182        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
183        tested.
185    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
186        now much more compatible with Perl, in particular in cases where the result
187        is a non-match for a non-anchored pattern. For example, if
188        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
189        "m", where previously it did not return a name. A side effect of this
190        change is that for partial matches, the last encountered mark name is
191        returned, as for non matches. A number of tests that were previously not
192        Perl-compatible have been moved into the Perl-compatible test files. The
193        refactoring has had the pleasing side effect of removing one argument from
194        the match() function, thus reducing its stack requirements.
196    19. If the /S+ option was used in pcretest to study a pattern using JIT,
197        subsequent uses of /S (without +) incorrectly behaved like /S+.
199    21. Retrieve executable code size support for the JIT compiler and fixing
200        some warnings.
202    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
203        not work when the shorter character appeared right at the end of the
204        subject string.
206    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
207        systems.
209    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
210        output it when the /M option is used in pcretest.
212    25. The CheckMan script was not being included in the distribution. Also, added
213        an explicit "perl" to run Perl scripts from the PrepareRelease script
214        because this is reportedly needed in Windows.
216    26. If study data was being save in a file and studying had not found a set of
217        "starts with" bytes for the pattern, the data written to the file (though
218        never used) was taken from uninitialized memory and so caused valgrind to
219        complain.
221    27. Updated RunTest.bat as provided by Sheri Pierce.
223    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
225    29. Computation of memory usage for the table of capturing group names was
226        giving an unnecessarily large value.
229    Version 8.20 21-Oct-2011
230    ------------------------
232    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
233        a POSIX class. After further experiments with Perl, which convinced me that
234        Perl has bugs and confusions, a closing square bracket is no longer allowed
235        in a POSIX name. This bug also affected patterns with classes that started
236        with full stops.
238    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
239        captured substring, but while checking the failing first alternative,
240        substring 1 is temporarily captured. If the output vector supplied to
241        pcre_exec() was not big enough for this capture, the yield of the function
242        was still zero ("insufficient space for captured substrings"). This cannot
243        be totally fixed without adding another stack variable, which seems a lot
244        of expense for a edge case. However, I have improved the situation in cases
245        such as /(a)(b)x|abc/ matched against "abc", where the return code
246        indicates that fewer than the maximum number of slots in the ovector have
247        been set.
249    3.  Related to (2) above: when there are more back references in a pattern than
250        slots in the output vector, pcre_exec() uses temporary memory during
251        matching, and copies in the captures as far as possible afterwards. It was
252        using the entire output vector, but this conflicts with the specification
253        that only 2/3 is used for passing back captured substrings. Now it uses
254        only the first 2/3, for compatibility. This is, of course, another edge
255        case.
257    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
258        main code base, and can be used by building with --enable-jit. When this is
259        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
260        runtime --no-jit option is given.
262    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
263        ovector, the return from the function was zero, implying that there were
264        other matches that did not fit. The correct "exactly full" value is now
265        returned.
267    6.  If a subpattern that was called recursively or as a subroutine contained
268        (*PRUNE) or any other control that caused it to give a non-standard return,
269        invalid errors such as "Error -26 (nested recursion at the same subject
270        position)" or even infinite loops could occur.
272    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
273        computing the minimum length on reaching *ACCEPT, and so ended up with the
274        wrong value of 1 rather than 0. Further investigation indicates that
275        computing a minimum subject length in the presence of *ACCEPT is difficult
276        (think back references, subroutine calls), and so I have changed the code
277        so that no minimum is registered for a pattern that contains *ACCEPT.
279    8.  If (*THEN) was present in the first (true) branch of a conditional group,
280        it was not handled as intended. [But see 16 below.]
282    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
283        Sheri Pierce.
285    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
286        the first byte in a match must be "a".
288    11. Change 17 for 8.13 increased the recursion depth for patterns like
289        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
290        pattern contains any instances of (*THEN). If it does not, the old
291        optimizations are restored. It would be nice to do this on a per-group
292        basis, but at the moment that is not feasible.
294    12. In some environments, the output of pcretest -C is CRLF terminated. This
295        broke RunTest's code that checks for the link size. A single white space
296        character after the value is now allowed for.
298    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
299        For "fr", it uses the Windows-specific input and output files.
301    14. If (*THEN) appeared in a group that was called recursively or as a
302        subroutine, it did not work as intended. [But see next item.]
304    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
305        pattern fragments (but not containing any | characters). If A and B are
306        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
307        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
308        D. In other words, Perl considers parentheses that do not contain any |
309        characters to be part of a surrounding alternative, whereas PCRE was
310        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
311        differently. PCRE now behaves in the same way as Perl, except in the case
312        of subroutine/recursion calls such as (?1) which have in any case always
313        been different (but PCRE had them first :-).
315    16. Related to 15 above: Perl does not treat the | in a conditional group as
316        creating alternatives. Such a group is treated in the same way as an
317        ordinary group without any | characters when processing (*THEN). PCRE has
318        been changed to match Perl's behaviour.
320    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
321        RunGrepTest script failed.
323    18. Change 22 for version 13 caused atomic groups to use more stack. This is
324        inevitable for groups that contain captures, but it can lead to a lot of
325        stack use in large patterns. The old behaviour has been restored for atomic
326        groups that do not contain any capturing parentheses.
328    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
329        suppress the check for a minimum subject length at run time. (If it was
330        given to pcre_exec() or pcre_dfa_exec() it did work.)
332    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
333        fail to work when decoding hex characters in data strings in EBCDIC
334        environments.
336    21. It appears that in at least one Mac OS environment, the isxdigit() function
337        is implemented as a macro that evaluates to its argument more than once,
338        contravening the C 90 Standard (I haven't checked a later standard). There
339        was an instance in pcretest which caused it to go wrong when processing
340        \x{...} escapes in subject strings. The has been rewritten to avoid using
341        things like p++ in the argument of isxdigit().
344    Version 8.13 16-Aug-2011
345    ------------------------
347    1.  The Unicode data tables have been updated to Unicode 6.0.0.
349    2.  Two minor typos in pcre_internal.h have been fixed.
351    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
352        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
353        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
355    4.  There were a number of related bugs in the code for matching backrefences
356        caselessly in UTF-8 mode when codes for the characters concerned were
357        different numbers of bytes. For example, U+023A and U+2C65 are an upper
358        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
359        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
360        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
361        2-byte code at the end of the subject (it thought there wasn't enough data
362        left).
364    5.  Comprehensive information about what went wrong is now returned by
365        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
366        as the output vector has at least 2 elements. The offset of the start of
367        the failing character and a reason code are placed in the vector.
369    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
370        now returned is for the first byte of the failing character, instead of the
371        last byte inspected. This is an incompatible change, but I hope it is small
372        enough not to be a problem. It makes the returned offset consistent with
373        pcre_exec() and pcre_dfa_exec().
375    7.  pcretest now gives a text phrase as well as the error number when
376        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
377        failure, the offset and reason code are output.
379    8.  When \R was used with a maximizing quantifier it failed to skip backwards
380        over a \r\n pair if the subsequent match failed. Instead, it just skipped
381        back over a single character (\n). This seems wrong (because it treated the
382        two characters as a single entity when going forwards), conflicts with the
383        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
384        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
385        has been changed.
387    9.  Some internal refactoring has changed the processing so that the handling
388        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
389        time (the PCRE_DOTALL option was changed this way some time ago: version
390        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
391        which was always a bit of a fudge. It also means that there is one less
392        argument for the match() function, which reduces its stack requirements
393        slightly. This change also fixes an incompatibility with Perl: the pattern
394        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
396    10. More internal refactoring has drastically reduced the number of recursive
397        calls to match() for possessively repeated groups such as (abc)++ when
398        using pcre_exec().
400    11. While implementing 10, a number of bugs in the handling of groups were
401        discovered and fixed:
403        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
404        (a|)*(?1) gave a compile-time internal error.
405        ((a|)+)+  did not notice that the outer group could match an empty string.
406        (^a|^)+   was not marked as anchored.
407        (.*a|.*)+ was not marked as matching at start or after a newline.
409    12. Yet more internal refactoring has removed another argument from the match()
410        function. Special calls to this function are now indicated by setting a
411        value in a variable in the "match data" data block.
413    13. Be more explicit in pcre_study() instead of relying on "default" for
414        opcodes that mean there is no starting character; this means that when new
415        ones are added and accidentally left out of pcre_study(), testing should
416        pick them up.
418    14. The -s option of pcretest has been documented for ages as being an old
419        synonym of -m (show memory usage). I have changed it to mean "force study
420        for every regex", that is, assume /S for every regex. This is similar to -i
421        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
422        using it. It makes it easier to run collections of tests with and without
423        study enabled, and thereby test pcre_study() more easily. All the standard
424        tests are now run with and without -s (but some patterns can be marked as
425        "never study" - see 20 below).
427    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
428        restoration of the capturing data to the outer values was not happening
429        correctly.
431    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
432        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
433        pattern had matched an empty string, and so incorrectly returned a no
434        match.
436    17. There was optimizing code for the last branch of non-capturing parentheses,
437        and also for the obeyed branch of a conditional subexpression, which used
438        tail recursion to cut down on stack usage. Unfortunately, now that there is
439        the possibility of (*THEN) occurring in these branches, tail recursion is
440        no longer possible because the return has to be checked for (*THEN). These
441        two optimizations have therefore been removed. [But see 8.20/11 above.]
443    18. If a pattern containing \R was studied, it was assumed that \R always
444        matched two bytes, thus causing the minimum subject length to be
445        incorrectly computed because \R can also match just one byte.
447    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
448        was incorrectly computed.
450    20. If /S is present twice on a test pattern in pcretest input, it now
451        *disables* studying, thereby overriding the use of -s on the command line
452        (see 14 above). This is necessary for one or two tests to keep the output
453        identical in both cases.
455    21. When (*ACCEPT) was used in an assertion that matched an empty string and
456        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
458    22. When an atomic group that contained a capturing parenthesis was
459        successfully matched, but the branch in which it appeared failed, the
460        capturing was not being forgotten if a higher numbered group was later
461        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
462        group 1 to "a", when in fact it should be unset. This applied to multi-
463        branched capturing and non-capturing groups, repeated or not, and also to
464        positive assertions (capturing in negative assertions does not happen
465        in PCRE) and also to nested atomic groups.
467    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
468        subject after a captured substring, to make it easier to tell which of a
469        number of identical substrings has been captured.
471    24. The way atomic groups are processed by pcre_exec() has been changed so that
472        if they are repeated, backtracking one repetition now resets captured
473        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
474        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
475        "aaa". Previously, it would have been "a". As part of this code
476        refactoring, the way recursive calls are handled has also been changed.
478    25. If an assertion condition captured any substrings, they were not passed
479        back unless some other capturing happened later. For example, if
480        (?(?=(a))a) was matched against "a", no capturing was returned.
482    26. When studying a pattern that contained subroutine calls or assertions,
483        the code for finding the minimum length of a possible match was handling
484        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
485        group 1 called group 2 while simultaneously a separate group 2 called group
486        1). A stack overflow occurred in this case. I have fixed this by limiting
487        the recursion depth to 10.
489    27. Updated RunTest.bat in the distribution to the version supplied by Tom
490        Fortmann. This supports explicit test numbers on the command line, and has
491        argument validation and error reporting.
493    28. An instance of \X with an unlimited repeat could fail if at any point the
494        first character it looked at was a mark character.
496    29. Some minor code refactoring concerning Unicode properties and scripts
497        should reduce the stack requirement of match() slightly.
499    30. Added the '=' option to pcretest to check the setting of unused capturing
500        slots at the end of the pattern, which are documented as being -1, but are
501        not included in the return count.
503    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
504        compiled something random. Now it gives a compile-time error (as does
505        Perl).
507    32. A *MARK encountered during the processing of a positive assertion is now
508        recorded and passed back (compatible with Perl).
510    33. If --only-matching or --colour was set on a pcregrep call whose pattern
511        had alternative anchored branches, the search for a second match in a line
512        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
513        matched the line "0102" twice. The same bug affected patterns that started
514        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
515        twice.
517    34. Previously, PCRE did not allow quantification of assertions. However, Perl
518        does, and because of capturing effects, quantifying parenthesized
519        assertions may at times be useful. Quantifiers are now allowed for
520        parenthesized assertions.
522    35. A minor code tidy in pcre_compile() when checking options for \R usage.
524    36. \g was being checked for fancy things in a character class, when it should
525        just be a literal "g".
527    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
528        appearance of a nested POSIX class supersedes an apparent external class.
529        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
530        unescaped square brackets may also appear as part of class names. For
531        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
532        more like Perl. (But see 8.20/1 above.)
534    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
535        was because it thought it was \N{name}, which is not supported).
537    39. Add minix to OS list not supporting the -S option in pcretest.
539    40. PCRE tries to detect cases of infinite recursion at compile time, but it
540        cannot analyze patterns in sufficient detail to catch mutual recursions
541        such as ((?1))((?2)). There is now a runtime test that gives an error if a
542        subgroup is called recursively as a subpattern for a second time at the
543        same position in the subject string. In previous releases this might have
544        been caught by the recursion limit, or it might have run out of stack.
546    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
547        happen only once. PCRE was, however incorrectly giving a compile time error
548        "recursive call could loop indefinitely" because it cannot analyze the
549        pattern in sufficient detail. The compile time test no longer happens when
550        PCRE is compiling a conditional subpattern, but actual runaway loops are
551        now caught at runtime (see 40 above).
553    42. It seems that Perl allows any characters other than a closing parenthesis
554        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
555        has been changed to be the same.
557    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
558        as not to get warnings when autogen.sh is called. Also changed
559        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
561    44. To help people who use pcregrep to scan files containing exceedingly long
562        lines, the following changes have been made:
564        (a) The default value of the buffer size parameter has been increased from
565            8K to 20K. (The actual buffer used is three times this size.)
567        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
568            PCRE is built.
570        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
571            to be set at run time.
573        (d) Numerical values in pcregrep options can be followed by K or M, for
574            example --buffer-size=50K.
576        (e) If a line being scanned overflows pcregrep's buffer, an error is now
577            given and the return code is set to 2.
579    45. Add a pointer to the latest mark to the callout data block.
581    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
582        partial match of an empty string instead of no match. This was specific to
583        the use of ".".
585    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
586        complete match instead of a partial match. This bug was dependent on both
587        the PCRE_UTF8 and PCRE_DOTALL options being set.
589    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
590        starting byte set, because \b was not being ignored.
593    Version 8.12 15-Jan-2011
594    ------------------------
596    1.  Fixed some typos in the markup of the man pages, and wrote a script that
597        checks for such things as part of the documentation building process.
599    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
600        --match-limit and --recursion-limit options (added for 8.11). In
601        particular, this made one of the standard tests fail. (The integer value
602        went into the wrong half of a long int.)
604    3.  If the --colour option was given to pcregrep with -v (invert match), it
605        did strange things, either producing crazy output, or crashing. It should,
606        of course, ignore a request for colour when reporting lines that do not
607        match.
609    4.  Another pcregrep bug caused similar problems if --colour was specified with
610        -M (multiline) and the pattern match finished with a line ending.
612    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
613        matched in multiline mode, the following line was shown as part of the
614        match. This seems wrong, so I have changed it.
616    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
617        the check for further matches in the same line (so they could be coloured)
618        to overrun the end of the current line. If another match was found, it was
619        incorrectly shown (and then shown again when found in the next line).
621    7.  If pcregrep was compiled under Windows, there was a reference to the
622        function pcregrep_exit() before it was defined. I am assuming this was
623        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
624        reported by a user. I've moved the definition above the reference.
627    Version 8.11 10-Dec-2010
628    ------------------------
630    1.  (*THEN) was not working properly if there were untried alternatives prior
631        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
632        backtracked to try for "b" instead of moving to the next alternative branch
633        at the same level (in this case, to look for "c"). The Perl documentation
634        is clear that when (*THEN) is backtracked onto, it goes to the "next
635        alternative in the innermost enclosing group".
637    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
638        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
639        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
640        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
641        (*THEN).
643    3.  If \s appeared in a character class, it removed the VT character from
644        the class, even if it had been included by some previous item, for example
645        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
646        of \s, but is part of the POSIX "space" class.)
648    4.  A partial match never returns an empty string (because you can always
649        match an empty string at the end of the subject); however the checking for
650        an empty string was starting at the "start of match" point. This has been
651        changed to the "earliest inspected character" point, because the returned
652        data for a partial match starts at this character. This means that, for
653        example, /(?<=abc)def/ gives a partial match for the subject "abc"
654        (previously it gave "no match").
656    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
657        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
658        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
659        has an implication that the given string is incomplete (because a partial
660        match is preferred over a full match). For this reason, these items now
661        give a partial match in this situation. [Aside: previously, the one case
662        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
663        match rather than a full match, which was wrong by the old rules, but is
664        now correct.]
666    6.  There was a bug in the handling of #-introduced comments, recognized when
667        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
668        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
669        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
670        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
671        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
672        places in pcre_compile().
674    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
675        comments when looking ahead for named forward references to subpatterns,
676        the only newline sequence it recognized was NL. It now handles newlines
677        according to the set newline convention.
679    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
680        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
681        cater for a lack of strerror(). These oversights have been fixed.
683    9.  Added --match-limit and --recursion-limit to pcregrep.
685    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
687    11. When the -o option was used, pcregrep was setting a return code of 1, even
688        when matches were found, and --line-buffered was not being honoured.
690    12. Added an optional parentheses number to the -o and --only-matching options
691        of pcregrep.
693    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
694        can match an empty string. The code to do it in pcretest and pcredemo
695        needed fixing:
697        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
698            only one byte after an empty string match just before CRLF (this case
699            just got forgotten; "any" and "anycrlf" were OK).
701        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
702            mode when an empty string match preceded an ASCII character followed by
703            a non-ASCII character. (The code for advancing by one character rather
704            than one byte was nonsense.)
706        (c) The pcredemo.c sample program did not have any code at all to handle
707            the cases when CRLF is a valid newline sequence.
709    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
710        as a starting offset was within the subject string. There is now a new
711        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
712        negative or greater than the length of the string. In order to test this,
713        pcretest is extended to allow the setting of negative starting offsets.
715    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
716        starting offset points to the beginning of a UTF-8 character was
717        unnecessarily clumsy. I tidied it up.
719    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
720        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
722    17. Nobody had reported that the --include_dir option, which was added in
723        release 7.7 should have been called --include-dir (hyphen, not underscore)
724        for compatibility with GNU grep. I have changed it to --include-dir, but
725        left --include_dir as an undocumented synonym, and the same for
726        --exclude-dir, though that is not available in GNU grep, at least as of
727        release 2.5.4.
729    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
730        characters from a string of bytes) have been redefined so as not to use
731        loops, in order to improve performance in some environments. At the same
732        time, I abstracted some of the common code into auxiliary macros to save
733        repetition (this should not affect the compiled code).
735    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
736        compile-time error is now given if \c is not followed by an ASCII
737        character, that is, a byte less than 128. (In EBCDIC mode, the code is
738        different, and any byte value is allowed.)
740    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
741        START_OPTIMIZE option, which is now allowed at compile time - but just
742        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
743        to pcregrep and other applications that have no direct access to PCRE
744        options. The new /Y option in pcretest sets this option when calling
745        pcre_compile().
747    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
748        back references. Groups containing recursive back references were forced to
749        be atomic by that change, but in the case of named groups, the amount of
750        memory required was incorrectly computed, leading to "Failed: internal
751        error: code overflow". This has been fixed.
753    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
754        pcretest.c, to avoid build problems in some Borland environments.
757    Version 8.10 25-Jun-2010
758    ------------------------
760    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
761        THEN.
763    2.  (*ACCEPT) was not working when inside an atomic group.
765    3.  Inside a character class, \B is treated as a literal by default, but
766        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
767        causes the error). The code is unchanged, but I tidied the documentation.
769    4.  Inside a character class, PCRE always treated \R and \X as literals,
770        whereas Perl faults them if its -w option is set. I have changed PCRE so
771        that it faults them when PCRE_EXTRA is set.
773    5.  Added support for \N, which always matches any character other than
774        newline. (It is the same as "." when PCRE_DOTALL is not set.)
776    6.  When compiling pcregrep with newer versions of gcc which may have
777        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
778        declared with attribute warn_unused_result" were given. Just casting the
779        result to (void) does not stop the warnings; a more elaborate fudge is
780        needed. I've used a macro to implement this.
782    7.  Minor change to pcretest.c to avoid a compiler warning.
784    8.  Added four artifical Unicode properties to help with an option to make
785        \s etc use properties (see next item). The new properties are: Xan
786        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
788    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
789        use Unicode properties. (*UCP) at the start of a pattern can be used to set
790        this option. Modified pcretest to add /W to test this facility. Added
791        REG_UCP to make it available via the POSIX interface.
793    10. Added --line-buffered to pcregrep.
795    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
796        studied, and the match started with a letter with a code point greater than
797        127 whose first byte was different to the first byte of the other case of
798        the letter, the other case of this starting letter was not recognized
799        (#976).
801    12. If a pattern that was studied started with a repeated Unicode property
802        test, for example, \p{Nd}+, there was the theoretical possibility of
803        setting up an incorrect bitmap of starting bytes, but fortunately it could
804        not have actually happened in practice until change 8 above was made (it
805        added property types that matched character-matching opcodes).
807    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
808        possible starting bytes for non-anchored patterns.
810    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
811        \R, and also a number of cases that involve Unicode properties, both
812        explicit and implicit when PCRE_UCP is set.
814    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
815        input, it could crash or give wrong results if characters with values
816        greater than 0xc0 were present in the subject string. (Detail: it assumed
817        UTF-8 input when processing these items.)
819    16. Added a lot of (int) casts to avoid compiler warnings in systems where
820        size_t is 64-bit (#991).
822    17. Added a check for running out of memory when PCRE is compiled with
823        --disable-stack-for-recursion (#990).
825    18. If the last data line in a file for pcretest does not have a newline on
826        the end, a newline was missing in the output.
828    19. The default pcre_chartables.c file recognizes only ASCII characters (values
829        less than 128) in its various bitmaps. However, there is a facility for
830        generating tables according to the current locale when PCRE is compiled. It
831        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
832        characters, are recognized by isspace() and therefore were getting set in
833        these tables, and indeed these tables seem to approximate to ISO 8859. This
834        caused a problem in UTF-8 mode when pcre_study() was used to create a list
835        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
836        which of course cannot start UTF-8 characters. I have changed the code so
837        that only real ASCII characters (less than 128) and the correct starting
838        bytes for UTF-8 encodings are set for characters greater than 127 when in
839        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
840        altogether.)
842    20. Added the /T option to pcretest so as to be able to run tests with non-
843        standard character tables, thus making it possible to include the tests
844        used for 19 above in the standard set of tests.
846    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
847        reference to a subpattern the other side of a comment that contains an
848        opening parenthesis caused either an internal compiling error, or a
849        reference to the wrong subpattern.
852    Version 8.02 19-Mar-2010
853    ------------------------
855    1.  The Unicode data tables have been updated to Unicode 5.2.0.
857    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
858        configured.
860    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
861        original author of that file, following a query about its status.
863    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
864        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
866    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
867        quantifier applied to a forward-referencing subroutine call, could compile
868        incorrect code or give the error "internal error: previously-checked
869        referenced subpattern not found".
871    6.  Both MS Visual Studio and Symbian OS have problems with initializing
872        variables to point to external functions. For these systems, therefore,
873        pcre_malloc etc. are now initialized to local functions that call the
874        relevant global functions.
876    7.  There were two entries missing in the vectors called coptable and poptable
877        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
878        I've fixed the data, and added a kludgy way of testing at compile time that
879        the lengths are correct (equal to the number of opcodes).
881    8.  Following on from 7, I added a similar kludge to check the length of the
882        eint vector in pcreposix.c.
884    9.  Error texts for pcre_compile() are held as one long string to avoid too
885        much relocation at load time. To find a text, the string is searched,
886        counting zeros. There was no check for running off the end of the string,
887        which could happen if a new error number was added without updating the
888        string.
890    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
892    11. \K was not working if it appeared in an atomic group or in a group that
893        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
894        \K is "not well defined" if used in an assertion. PCRE now accepts it if
895        the assertion is positive, but not if it is negative.
897    12. Change 11 fortuitously reduced the size of the stack frame used in the
898        "match()" function of pcre_exec.c by one pointer. Forthcoming
899        implementation of support for (*MARK) will need an extra pointer on the
900        stack; I have reserved it now, so that the stack frame size does not
901        decrease.
903    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
904        item in branch that calls a recursion is a subroutine call - as in the
905        second branch in the above example - was incorrectly given the compile-
906        time error "recursive call could loop indefinitely" because pcre_compile()
907        was not correctly checking the subroutine for matching a non-empty string.
909    14. The checks for overrunning compiling workspace could trigger after an
910        overrun had occurred. This is a "should never occur" error, but it can be
911        triggered by pathological patterns such as hundreds of nested parentheses.
912        The checks now trigger 100 bytes before the end of the workspace.
914    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
917    Version 8.01 19-Jan-2010
918    ------------------------
920    1.  If a pattern contained a conditional subpattern with only one branch (in
921        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
922        computed the wrong minimum data length (which is of course zero for such
923        subpatterns). This could cause incorrect "no match" results.
925    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
926        the pattern is reset in the first branch, pcre_compile() failed with
927        "internal error: code overflow at offset...". This happened only when
928        the reset was to the original external option setting. (An optimization
929        abstracts leading options settings into an external setting, which was the
930        cause of this.)
932    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
933        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
934        assertion pattern did not match (meaning that the assertion was true), it
935        was incorrectly treated as false if the SKIP had been reached during the
936        matching. This also applied to assertions used as conditions.
938    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
939        assertion subpattern, including such a pattern used as a condition,
940        unpredictable results occurred, instead of the error return
943    5.  The C++ GlobalReplace function was not working like Perl for the special
944        situation when an empty string is matched. It now does the fancy magic
945        stuff that is necessary.
947    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
948        removed. (These were left over from very, very early versions of PCRE.)
950    7.  Some cosmetic changes to the code to make life easier when compiling it
951        as part of something else:
953        (a) Change DEBUG to PCRE_DEBUG.
955        (b) In pcre_compile(), rename the member of the "branch_chain" structure
956            called "current" as "current_branch", to prevent a collision with the
957            Linux macro when compiled as a kernel module.
959        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
960            prevent a collision with the Linux macro when compiled as a kernel
961            module.
963    8.  In pcre_compile() there are some checks for integer overflows that used to
964        cast potentially large values to (double). This has been changed to that
965        when building, a check for int64_t is made, and if it is found, it is used
966        instead, thus avoiding the use of floating point arithmetic. (There is no
967        other use of FP in PCRE.) If int64_t is not found, the fallback is to
968        double.
970    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
971        2005 (difference between two addresses compared to an unsigned value).
973    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
974        custom one, because of the following reported problem in Windows:
976          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
977              under Win32.
978          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
979              therefore missing the function definition.
980          - The compiler thus generates a "C" signature for the test function.
981          - The linker fails to find the "C" function.
982          - PCRE fails to configure if asked to do so against libbz2.
984    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
985        messages were output:
987          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
988          rerunning libtoolize, to keep the correct libtool macros in-tree.
989          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
991        I have done both of these things.
993    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
994        most of the time, it *can* run out if it is given a pattern that contains a
995        runaway infinite recursion. I updated the discussion in the pcrestack man
996        page.
998    13. Now that we have gone to the x.xx style of version numbers, the minor
999        version may start with zero. Using 08 or 09 is a bad idea because users
1000        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
1001        interpreted as invalid octal numbers. I've updated the previous comment in
1002        configure.ac, and also added a check that gives an error if 08 or 09 are
1003        used.
1005    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
1006        causing partial matching to fail when the end of the subject matched \W
1007        in a UTF-8 pattern where \W was quantified with a minimum of 3.
1009    15. There were some discrepancies between the declarations in pcre_internal.h
1010        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
1011        their definitions. The declarations used "const uschar *" and the
1012        definitions used USPTR. Even though USPTR is normally defined as "const
1013        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
1014        reported that: "This difference in casting confuses some C++ compilers, for
1015        example, SunCC recognizes above declarations as different functions and
1016        generates broken code for hbpcre." I have changed the declarations to use
1017        USPTR.
1019    16. GNU libtool is named differently on some systems. The autogen.sh script now
1020        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
1021        (FreeBSD).
1023    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
1024        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
1025        comment: "Figure out how to create a longlong from a string: strtoll and
1026        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
1027        instance, but it only takes 2 args instead of 3!"
1029    18. A subtle bug concerned with back references has been fixed by a change of
1030        specification, with a corresponding code fix. A pattern such as
1031        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
1032        refers, was giving matches when it shouldn't. For example, xa=xaaa would
1033        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
1034        same bug. Such groups have to be quantified to be useful, or contained
1035        inside another quantified group. (If there's no repetition, the reference
1036        can never match.) The problem arises because, having left the group and
1037        moved on to the rest of the pattern, a later failure that backtracks into
1038        the group uses the captured value from the final iteration of the group
1039        rather than the correct earlier one. I have fixed this in PCRE by forcing
1040        any group that contains a reference to itself to be an atomic group; that
1041        is, there cannot be any backtracking into it once it has completed. This is
1042        similar to recursive and subroutine calls.
1045    Version 8.00 19-Oct-09
1046    ----------------------
1048    1.  The table for translating pcre_compile() error codes into POSIX error codes
1049        was out-of-date, and there was no check on the pcre_compile() error code
1050        being within the table. This could lead to an OK return being given in
1051        error.
1053    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
1054        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
1055        in a Windows environment.
1057    3.  The pcregrep --count option prints the count for each file even when it is
1058        zero, as does GNU grep. However, pcregrep was also printing all files when
1059        --files-with-matches was added. Now, when both options are given, it prints
1060        counts only for those files that have at least one match. (GNU grep just
1061        prints the file name in this circumstance, but including the count seems
1062        more useful - otherwise, why use --count?) Also ensured that the
1063        combination -clh just lists non-zero counts, with no names.
1065    4.  The long form of the pcregrep -F option was incorrectly implemented as
1066        --fixed_strings instead of --fixed-strings. This is an incompatible change,
1067        but it seems right to fix it, and I didn't think it was worth preserving
1068        the old behaviour.
1070    5.  The command line items --regex=pattern and --regexp=pattern were not
1071        recognized by pcregrep, which required --regex pattern or --regexp pattern
1072        (with a space rather than an '='). The man page documented the '=' forms,
1073        which are compatible with GNU grep; these now work.
1075    6.  No libpcreposix.pc file was created for pkg-config; there was just
1076        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
1078    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
1079        when UCP support is not needed, by modifying the Python script that
1080        generates it from Unicode data files. This should not matter if the module
1081        is correctly used as a library, but I received one complaint about 50K of
1082        unwanted data. My guess is that the person linked everything into his
1083        program rather than using a library. Anyway, it does no harm.
1085    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
1086        was a minimum greater than 1 for a wide character in a possessive
1087        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
1088        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
1089        character. Chaos in the form of incorrect output or a compiling loop could
1090        result.
1092    9.  The restrictions on what a pattern can contain when partial matching is
1093        requested for pcre_exec() have been removed. All patterns can now be
1094        partially matched by this function. In addition, if there are at least two
1095        slots in the offset vector, the offset of the earliest inspected character
1096        for the match and the offset of the end of the subject are set in them when
1097        PCRE_ERROR_PARTIAL is returned.
1099    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
1100        synonymous with PCRE_PARTIAL, for backwards compatibility, and
1101        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
1102        and may be more useful for multi-segment matching.
1104    11. Partial matching with pcre_exec() is now more intuitive. A partial match
1105        used to be given if ever the end of the subject was reached; now it is
1106        given only if matching could not proceed because another character was
1107        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
1108        string "Z", which now yields "no match" instead of "partial match". In the
1109        case of pcre_dfa_exec(), "no match" is given if every matching path for the
1110        final character ended with (*FAIL).
1112    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
1113        if the pattern had a "must contain" character that was already found in the
1114        earlier partial match, unless partial matching was again requested. For
1115        example, with the pattern /dog.(body)?/, the "must contain" character is
1116        "g". If the first part-match was for the string "dog", restarting with
1117        "sbody" failed. This bug has been fixed.
1119    13. The string returned by pcre_dfa_exec() after a partial match has been
1120        changed so that it starts at the first inspected character rather than the
1121        first character of the match. This makes a difference only if the pattern
1122        starts with a lookbehind assertion or \b or \B (\K is not supported by
1123        pcre_dfa_exec()). It's an incompatible change, but it makes the two
1124        matching functions compatible, and I think it's the right thing to do.
1126    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
1127        so that the demonstration program is easily available in environments where
1128        PCRE has not been installed from source.
1130    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
1131        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
1132        library.
1134    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
1135        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
1136        is not the first non-POSIX option to be added. Clearly some people find
1137        these options useful.
1139    17. If a caller to the POSIX matching function regexec() passes a non-zero
1140        value for nmatch with a NULL value for pmatch, the value of
1141        nmatch is forced to zero.
1143    18. RunGrepTest did not have a test for the availability of the -u option of
1144        the diff command, as RunTest does. It now checks in the same way as
1145        RunTest, and also checks for the -b option.
1147    19. If an odd number of negated classes containing just a single character
1148        interposed, within parentheses, between a forward reference to a named
1149        subpattern and the definition of the subpattern, compilation crashed with
1150        an internal error, complaining that it could not find the referenced
1151        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
1152        [The bug was that it was starting one character too far in when skipping
1153        over the character class, thus treating the ] as data rather than
1154        terminating the class. This meant it could skip too much.]
1156    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
1157        /g option in pcretest when the pattern contains \K, which makes it possible
1158        to have an empty string match not at the start, even when the pattern is
1159        anchored. Updated pcretest and pcredemo to use this option.
1161    21. If the maximum number of capturing subpatterns in a recursion was greater
1162        than the maximum at the outer level, the higher number was returned, but
1163        with unset values at the outer level. The correct (outer level) value is
1164        now given.
1166    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
1167        PCRE did not set those parentheses (unlike Perl). I have now found a way to
1168        make it do so. The string so far is captured, making this feature
1169        compatible with Perl.
1171    23. The tests have been re-organized, adding tests 11 and 12, to make it
1172        possible to check the Perl 5.10 features against Perl 5.10.
1174    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
1175        pattern matches a fixed length string. PCRE did not allow this; now it
1176        does. Neither allows recursion.
1178    25. I finally figured out how to implement a request to provide the minimum
1179        length of subject string that was needed in order to match a given pattern.
1180        (It was back references and recursion that I had previously got hung up
1181        on.) This code has now been added to pcre_study(); it finds a lower bound
1182        to the length of subject needed. It is not necessarily the greatest lower
1183        bound, but using it to avoid searching strings that are too short does give
1184        some useful speed-ups. The value is available to calling programs via
1185        pcre_fullinfo().
1187    26. While implementing 25, I discovered to my embarrassment that pcretest had
1188        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
1189        study optimizations had never been tested with that matching function.
1190        Oops. What is worse, even when it was passed study data, there was a bug in
1191        pcre_dfa_exec() that meant it never actually used it. Double oops. There
1192        were also very few tests of studied patterns with pcre_dfa_exec().
1194    27. If (?| is used to create subpatterns with duplicate numbers, they are now
1195        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
1196        on the other side of the coin, they are no longer allowed to have different
1197        names, because these cannot be distinguished in PCRE, and this has caused
1198        confusion. (This is a difference from Perl.)
1200    28. When duplicate subpattern names are present (necessarily with different
1201        numbers, as required by 27 above), and a test is made by name in a
1202        conditional pattern, either for a subpattern having been matched, or for
1203        recursion in such a pattern, all the associated numbered subpatterns are
1204        tested, and the overall condition is true if the condition is true for any
1205        one of them. This is the way Perl works, and is also more like the way
1206        testing by number works.
1209    Version 7.9 11-Apr-09
1210  ---------------------  ---------------------
1212  1.  When building with support for bzlib/zlib (pcregrep) and/or readline  1.  When building with support for bzlib/zlib (pcregrep) and/or readline
# Line 17  Version 7.9 xx-xxx-09 Line 1222  Version 7.9 xx-xxx-09
1222      but BOOL is not.      but BOOL is not.
1224  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
1225      PCRE_MATCH_LIMIT_RETURSION values as ints, when they should be long ints.      PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
1227  4.  The pcregrep documentation said spaces were inserted as well as colons (or  4.  The pcregrep documentation said spaces were inserted as well as colons (or
1228      hyphens) following file names and line numbers when outputting matching      hyphens) following file names and line numbers when outputting matching
# Line 42  Version 7.9 xx-xxx-09 Line 1247  Version 7.9 xx-xxx-09
1247      correctly handled. The rule now is that both the assertion and what follows      correctly handled. The rule now is that both the assertion and what follows
1248      in the first alternative must satisfy the test.      in the first alternative must satisfy the test.
1250  9.  If auto-callout was enabled in a pattern with a conditional group whose  9.  If auto-callout was enabled in a pattern with a conditional group whose
1251      condition was an assertion, PCRE could crash during matching, both with      condition was an assertion, PCRE could crash during matching, both with
1252      pcre_exec() and pcre_dfa_exec().      pcre_exec() and pcre_dfa_exec().
# Line 64  Version 7.9 xx-xxx-09 Line 1269  Version 7.9 xx-xxx-09
1269  17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch  17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
1270      from Martin Jerabek that uses macro names for all relevant character and      from Martin Jerabek that uses macro names for all relevant character and
1271      string constants.      string constants.
1273  18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and  18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
1274      SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without      SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
1275      SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of      SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
1276      these, but not everybody uses configure.      these, but not everybody uses configure.
1278  19. A conditional group that had only one branch was not being correctly  19. A conditional group that had only one branch was not being correctly
1279      recognized as an item that could match an empty string. This meant that an      recognized as an item that could match an empty string. This meant that an
1280      enclosing group might also not be so recognized, causing infinite looping      enclosing group might also not be so recognized, causing infinite looping
1281      (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$      (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
1282      with the subject "ab", where knowledge that the repeated group can match      with the subject "ab", where knowledge that the repeated group can match
1283      nothing is needed in order to break the loop.      nothing is needed in order to break the loop.
1285  20. If a pattern that was compiled with callouts was matched using pcre_dfa_  20. If a pattern that was compiled with callouts was matched using pcre_dfa_
1286      exec(), but without supplying a callout function, matching went wrong.      exec(), but without supplying a callout function, matching went wrong.
1288    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
1289        leak if the size of the offset vector was greater than 30. When the vector
1290        is smaller, the saved offsets during recursion go onto a local stack
1291        vector, but for larger vectors malloc() is used. It was failing to free
1292        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
1293        error, in fact).
1295    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
1296        heapframe that is used only when UTF-8 support is enabled. This caused no
1297        problem, but was untidy.
1299    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
1300        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
1301        included within another project.
1303    24. Steven Van Ingelgem's patches to add more options to the CMake support,
1304        slightly modified by me:
1306          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
1307              not building pcregrep.
1309          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
1310              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
1312    25. Forward references, both numeric and by name, in patterns that made use of
1313        duplicate group numbers, could behave incorrectly or give incorrect errors,
1314        because when scanning forward to find the reference group, PCRE was not
1315        taking into account the duplicate group numbers. A pattern such as
1316        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
1318    26. Changed a few more instances of "const unsigned char *" to USPTR, making
1319        the feature of a custom pointer more persuasive (as requested by a user).
1321    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
1322        pcretest.c, inside #ifndefs, because it seems they are sometimes already
1323        pre-defined.
1325    28. Added support for (*UTF8) at the start of a pattern.
1327    29. Arrange for flags added by the "release type" setting in CMake to be shown
1328        in the configuration summary.
1331  Version 7.8 05-Sep-08  Version 7.8 05-Sep-08

Removed from v.399  
changed lines
  Added in v.932

  ViewVC Help
Powered by ViewVC 1.1.5