/[pcre]/code/trunk/ChangeLog
ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 564 by ph10, Sun Oct 31 16:07:24 2010 UTC revision 957 by ph10, Wed Apr 4 16:18:29 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.11 10-Oct-2010  Version 8.31
5    -----------------------------
6    
7    1.  Fixing a wrong JIT test case and some compiler warnings.
8    
9    2.  Removed a bashism from the RunTest script.
10    
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)".
14    
15    4.  Partial matching support is added to the JIT compiler.
16    
17    5.  Fixed several bugs concerned with partial matching of items that consist
18        of more than one character:
19    
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.
23    
24        (b) \R did not give a hard partial match if \r was found at the end of the
25            subject.
26    
27        (c) \X did not give a hard partial match after matching one or more
28            characters at the end of the subject.
29    
30        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
31            a partial match for the string "\r".
32    
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.
35    
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.
39    
40    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
41        or /S+[+] with a digit between 1 and 7.
42    
43    8.  OP_NOT now supports any UTF character not just single-byte ones.
44    
45    9.  (*MARK) control verb is now supported by the JIT compiler.
46    
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.)
49    
50    11. Add PCRE_INFO_MAXLOOKBEHIND.
51    
52    12. Applied a (slightly modified) user-supplied patch that improves performance
53        when the heap is used for recursion (compiled with --disable-stack-for-
54        recursion). Instead of malloc and free for each heap frame each time a
55        logical recursion happens, frames are retained on a chain and re-used where
56        possible. This sometimes gives as much as 30% improvement.
57    
58    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
59        call.
60    
61    14. As documented, (*COMMIT) is now confined to within a positive assertion.
62    
63    15. It is now possible to link pcretest with libedit as an alternative to
64        libreadline.
65    
66    16. (*COMMIT) control verb is now supported by the JIT compiler.
67    
68    17. The Unicode data tables have been updated to Unicode 6.1.0.
69    
70    18. Added --file-list option to pcregrep.
71    
72    19. Added binary file support to pcregrep, including the -a, --binary-files,
73        -I, and --text options.
74    
75    20. The madvise function is renamed for posix_madvise for QNX compatibility
76        reasons. Fixed by Giuseppe D'Angelo.
77    
78    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
79    
80    22. Changed the option for creating symbolic links for 16-bit man pages from
81        -s to -sf so that re-installing does not cause issues.
82    
83    
84    Version 8.30 04-February-2012
85    -----------------------------
86    
87    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
88        name is defined in ctype.h.
89    
90    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
91        only in quite long subpatterns.
92    
93    3.  Removed the function pcre_info(), which has been obsolete and deprecated
94        since it was replaced by pcre_fullinfo() in February 2000.
95    
96    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
97        match a (*MARK), and the match failed at the start of the subject, a
98        reference to memory before the start of the subject could occur. This bug
99        was introduced by fix 17 of release 8.21.
100    
101    5.  A reference to an unset group with zero minimum repetition was giving
102        totally wrong answers (in non-JavaScript-compatibility mode). For example,
103        /(another)?(\1?)test/ matched against "hello world test". This bug was
104        introduced in release 8.13.
105    
106    6.  Add support for 16-bit character strings (a large amount of work involving
107        many changes and refactorings).
108    
109    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
110        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
111        from a file.
112    
113    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
114        rounding is not applied in this particular case).
115    
116    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
117        if they appear, or are escaped, in patterns.
118    
119    10. Get rid of a number of -Wunused-but-set-variable warnings.
120    
121    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
122        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
123        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
124        also returns the mark "x". This bug applied to capturing parentheses,
125        non-capturing parentheses, and atomic parentheses. It also applied to some
126        assertions.
127    
128    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
129        information out of configure.ac instead of relying on pcre.h.generic, which
130        is not stored in the repository.
131    
132    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
133        -lreadline.
134    
135    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
136    
137    15. Applied Graycode's patch to put the top-level frame on the stack rather
138        than the heap when not using the stack for recursion. This gives a
139        performance improvement in many cases when recursion is not deep.
140    
141    16. Experimental code added to "pcretest -C" to output the stack frame size.
142    
143    
144    Version 8.21 12-Dec-2011
145    ------------------------
146    
147    1.  Updating the JIT compiler.
148    
149    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
150        are added as well.
151    
152    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
153        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
154        calling _pcre_jit_exec. Some extra comments are added.
155    
156    4.  (*MARK) settings inside atomic groups that do not contain any capturing
157        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
158        was introduced by change 18 for 8.20.
159    
160    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
161        ECMA-262 standard.
162    
163    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
164        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
165        This bug was probably introduced by change 9 of 8.13.
166    
167    7.  While fixing 6 above, I noticed that a number of other items were being
168        incorrectly rejected as "not fixed length". This arose partly because newer
169        opcodes had not been added to the fixed-length checking code. I have (a)
170        corrected the bug and added tests for these items, and (b) arranged for an
171        error to occur if an unknown opcode is encountered while checking for fixed
172        length instead of just assuming "not fixed length". The items that were
173        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
174        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
175        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
176    
177    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
178        being incorrectly compiled and would have given unpredicatble results.
179    
180    9.  A possessively repeated subpattern with minimum repeat count greater than
181        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
182        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
183        the first (A) could occur when it should not.
184    
185    10. Add a cast and remove a redundant test from the code.
186    
187    11. JIT should use pcre_malloc/pcre_free for allocation.
188    
189    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
190        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
191        is anything other than /usr, -L is still shown).
192    
193    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
194    
195    14. Perl does not support \N without a following name in a [] class; PCRE now
196        also gives an error.
197    
198    15. If a forward reference was repeated with an upper limit of around 2000,
199        it caused the error "internal error: overran compiling workspace". The
200        maximum number of forward references (including repeats) was limited by the
201        internal workspace, and dependent on the LINK_SIZE. The code has been
202        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
203        the default depends on LINK_SIZE. There is a new upper limit (for safety)
204        of around 200,000 forward references. While doing this, I also speeded up
205        the filling in of repeated forward references.
206    
207    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
208        incorrectly expecting the subject to contain another "a" after the start.
209    
210    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
211        in the match, the SKIP should be ignored. This was not happening; instead
212        the SKIP was being treated as NOMATCH. For patterns such as
213        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
214        tested.
215    
216    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
217        now much more compatible with Perl, in particular in cases where the result
218        is a non-match for a non-anchored pattern. For example, if
219        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
220        "m", where previously it did not return a name. A side effect of this
221        change is that for partial matches, the last encountered mark name is
222        returned, as for non matches. A number of tests that were previously not
223        Perl-compatible have been moved into the Perl-compatible test files. The
224        refactoring has had the pleasing side effect of removing one argument from
225        the match() function, thus reducing its stack requirements.
226    
227    19. If the /S+ option was used in pcretest to study a pattern using JIT,
228        subsequent uses of /S (without +) incorrectly behaved like /S+.
229    
230    21. Retrieve executable code size support for the JIT compiler and fixing
231        some warnings.
232    
233    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
234        not work when the shorter character appeared right at the end of the
235        subject string.
236    
237    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
238        systems.
239    
240    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
241        output it when the /M option is used in pcretest.
242    
243    25. The CheckMan script was not being included in the distribution. Also, added
244        an explicit "perl" to run Perl scripts from the PrepareRelease script
245        because this is reportedly needed in Windows.
246    
247    26. If study data was being save in a file and studying had not found a set of
248        "starts with" bytes for the pattern, the data written to the file (though
249        never used) was taken from uninitialized memory and so caused valgrind to
250        complain.
251    
252    27. Updated RunTest.bat as provided by Sheri Pierce.
253    
254    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
255    
256    29. Computation of memory usage for the table of capturing group names was
257        giving an unnecessarily large value.
258    
259    
260    Version 8.20 21-Oct-2011
261    ------------------------
262    
263    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
264        a POSIX class. After further experiments with Perl, which convinced me that
265        Perl has bugs and confusions, a closing square bracket is no longer allowed
266        in a POSIX name. This bug also affected patterns with classes that started
267        with full stops.
268    
269    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
270        captured substring, but while checking the failing first alternative,
271        substring 1 is temporarily captured. If the output vector supplied to
272        pcre_exec() was not big enough for this capture, the yield of the function
273        was still zero ("insufficient space for captured substrings"). This cannot
274        be totally fixed without adding another stack variable, which seems a lot
275        of expense for a edge case. However, I have improved the situation in cases
276        such as /(a)(b)x|abc/ matched against "abc", where the return code
277        indicates that fewer than the maximum number of slots in the ovector have
278        been set.
279    
280    3.  Related to (2) above: when there are more back references in a pattern than
281        slots in the output vector, pcre_exec() uses temporary memory during
282        matching, and copies in the captures as far as possible afterwards. It was
283        using the entire output vector, but this conflicts with the specification
284        that only 2/3 is used for passing back captured substrings. Now it uses
285        only the first 2/3, for compatibility. This is, of course, another edge
286        case.
287    
288    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
289        main code base, and can be used by building with --enable-jit. When this is
290        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
291        runtime --no-jit option is given.
292    
293    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
294        ovector, the return from the function was zero, implying that there were
295        other matches that did not fit. The correct "exactly full" value is now
296        returned.
297    
298    6.  If a subpattern that was called recursively or as a subroutine contained
299        (*PRUNE) or any other control that caused it to give a non-standard return,
300        invalid errors such as "Error -26 (nested recursion at the same subject
301        position)" or even infinite loops could occur.
302    
303    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
304        computing the minimum length on reaching *ACCEPT, and so ended up with the
305        wrong value of 1 rather than 0. Further investigation indicates that
306        computing a minimum subject length in the presence of *ACCEPT is difficult
307        (think back references, subroutine calls), and so I have changed the code
308        so that no minimum is registered for a pattern that contains *ACCEPT.
309    
310    8.  If (*THEN) was present in the first (true) branch of a conditional group,
311        it was not handled as intended. [But see 16 below.]
312    
313    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
314        Sheri Pierce.
315    
316    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
317        the first byte in a match must be "a".
318    
319    11. Change 17 for 8.13 increased the recursion depth for patterns like
320        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
321        pattern contains any instances of (*THEN). If it does not, the old
322        optimizations are restored. It would be nice to do this on a per-group
323        basis, but at the moment that is not feasible.
324    
325    12. In some environments, the output of pcretest -C is CRLF terminated. This
326        broke RunTest's code that checks for the link size. A single white space
327        character after the value is now allowed for.
328    
329    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
330        For "fr", it uses the Windows-specific input and output files.
331    
332    14. If (*THEN) appeared in a group that was called recursively or as a
333        subroutine, it did not work as intended. [But see next item.]
334    
335    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
336        pattern fragments (but not containing any | characters). If A and B are
337        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
338        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
339        D. In other words, Perl considers parentheses that do not contain any |
340        characters to be part of a surrounding alternative, whereas PCRE was
341        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
342        differently. PCRE now behaves in the same way as Perl, except in the case
343        of subroutine/recursion calls such as (?1) which have in any case always
344        been different (but PCRE had them first :-).
345    
346    16. Related to 15 above: Perl does not treat the | in a conditional group as
347        creating alternatives. Such a group is treated in the same way as an
348        ordinary group without any | characters when processing (*THEN). PCRE has
349        been changed to match Perl's behaviour.
350    
351    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
352        RunGrepTest script failed.
353    
354    18. Change 22 for version 13 caused atomic groups to use more stack. This is
355        inevitable for groups that contain captures, but it can lead to a lot of
356        stack use in large patterns. The old behaviour has been restored for atomic
357        groups that do not contain any capturing parentheses.
358    
359    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
360        suppress the check for a minimum subject length at run time. (If it was
361        given to pcre_exec() or pcre_dfa_exec() it did work.)
362    
363    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
364        fail to work when decoding hex characters in data strings in EBCDIC
365        environments.
366    
367    21. It appears that in at least one Mac OS environment, the isxdigit() function
368        is implemented as a macro that evaluates to its argument more than once,
369        contravening the C 90 Standard (I haven't checked a later standard). There
370        was an instance in pcretest which caused it to go wrong when processing
371        \x{...} escapes in subject strings. The has been rewritten to avoid using
372        things like p++ in the argument of isxdigit().
373    
374    
375    Version 8.13 16-Aug-2011
376    ------------------------
377    
378    1.  The Unicode data tables have been updated to Unicode 6.0.0.
379    
380    2.  Two minor typos in pcre_internal.h have been fixed.
381    
382    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
383        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
384        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
385    
386    4.  There were a number of related bugs in the code for matching backrefences
387        caselessly in UTF-8 mode when codes for the characters concerned were
388        different numbers of bytes. For example, U+023A and U+2C65 are an upper
389        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
390        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
391        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
392        2-byte code at the end of the subject (it thought there wasn't enough data
393        left).
394    
395    5.  Comprehensive information about what went wrong is now returned by
396        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
397        as the output vector has at least 2 elements. The offset of the start of
398        the failing character and a reason code are placed in the vector.
399    
400    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
401        now returned is for the first byte of the failing character, instead of the
402        last byte inspected. This is an incompatible change, but I hope it is small
403        enough not to be a problem. It makes the returned offset consistent with
404        pcre_exec() and pcre_dfa_exec().
405    
406    7.  pcretest now gives a text phrase as well as the error number when
407        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
408        failure, the offset and reason code are output.
409    
410    8.  When \R was used with a maximizing quantifier it failed to skip backwards
411        over a \r\n pair if the subsequent match failed. Instead, it just skipped
412        back over a single character (\n). This seems wrong (because it treated the
413        two characters as a single entity when going forwards), conflicts with the
414        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
415        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
416        has been changed.
417    
418    9.  Some internal refactoring has changed the processing so that the handling
419        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
420        time (the PCRE_DOTALL option was changed this way some time ago: version
421        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
422        which was always a bit of a fudge. It also means that there is one less
423        argument for the match() function, which reduces its stack requirements
424        slightly. This change also fixes an incompatibility with Perl: the pattern
425        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
426    
427    10. More internal refactoring has drastically reduced the number of recursive
428        calls to match() for possessively repeated groups such as (abc)++ when
429        using pcre_exec().
430    
431    11. While implementing 10, a number of bugs in the handling of groups were
432        discovered and fixed:
433    
434        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
435        (a|)*(?1) gave a compile-time internal error.
436        ((a|)+)+  did not notice that the outer group could match an empty string.
437        (^a|^)+   was not marked as anchored.
438        (.*a|.*)+ was not marked as matching at start or after a newline.
439    
440    12. Yet more internal refactoring has removed another argument from the match()
441        function. Special calls to this function are now indicated by setting a
442        value in a variable in the "match data" data block.
443    
444    13. Be more explicit in pcre_study() instead of relying on "default" for
445        opcodes that mean there is no starting character; this means that when new
446        ones are added and accidentally left out of pcre_study(), testing should
447        pick them up.
448    
449    14. The -s option of pcretest has been documented for ages as being an old
450        synonym of -m (show memory usage). I have changed it to mean "force study
451        for every regex", that is, assume /S for every regex. This is similar to -i
452        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
453        using it. It makes it easier to run collections of tests with and without
454        study enabled, and thereby test pcre_study() more easily. All the standard
455        tests are now run with and without -s (but some patterns can be marked as
456        "never study" - see 20 below).
457    
458    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
459        restoration of the capturing data to the outer values was not happening
460        correctly.
461    
462    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
463        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
464        pattern had matched an empty string, and so incorrectly returned a no
465        match.
466    
467    17. There was optimizing code for the last branch of non-capturing parentheses,
468        and also for the obeyed branch of a conditional subexpression, which used
469        tail recursion to cut down on stack usage. Unfortunately, now that there is
470        the possibility of (*THEN) occurring in these branches, tail recursion is
471        no longer possible because the return has to be checked for (*THEN). These
472        two optimizations have therefore been removed. [But see 8.20/11 above.]
473    
474    18. If a pattern containing \R was studied, it was assumed that \R always
475        matched two bytes, thus causing the minimum subject length to be
476        incorrectly computed because \R can also match just one byte.
477    
478    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
479        was incorrectly computed.
480    
481    20. If /S is present twice on a test pattern in pcretest input, it now
482        *disables* studying, thereby overriding the use of -s on the command line
483        (see 14 above). This is necessary for one or two tests to keep the output
484        identical in both cases.
485    
486    21. When (*ACCEPT) was used in an assertion that matched an empty string and
487        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
488    
489    22. When an atomic group that contained a capturing parenthesis was
490        successfully matched, but the branch in which it appeared failed, the
491        capturing was not being forgotten if a higher numbered group was later
492        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
493        group 1 to "a", when in fact it should be unset. This applied to multi-
494        branched capturing and non-capturing groups, repeated or not, and also to
495        positive assertions (capturing in negative assertions does not happen
496        in PCRE) and also to nested atomic groups.
497    
498    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
499        subject after a captured substring, to make it easier to tell which of a
500        number of identical substrings has been captured.
501    
502    24. The way atomic groups are processed by pcre_exec() has been changed so that
503        if they are repeated, backtracking one repetition now resets captured
504        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
505        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
506        "aaa". Previously, it would have been "a". As part of this code
507        refactoring, the way recursive calls are handled has also been changed.
508    
509    25. If an assertion condition captured any substrings, they were not passed
510        back unless some other capturing happened later. For example, if
511        (?(?=(a))a) was matched against "a", no capturing was returned.
512    
513    26. When studying a pattern that contained subroutine calls or assertions,
514        the code for finding the minimum length of a possible match was handling
515        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
516        group 1 called group 2 while simultaneously a separate group 2 called group
517        1). A stack overflow occurred in this case. I have fixed this by limiting
518        the recursion depth to 10.
519    
520    27. Updated RunTest.bat in the distribution to the version supplied by Tom
521        Fortmann. This supports explicit test numbers on the command line, and has
522        argument validation and error reporting.
523    
524    28. An instance of \X with an unlimited repeat could fail if at any point the
525        first character it looked at was a mark character.
526    
527    29. Some minor code refactoring concerning Unicode properties and scripts
528        should reduce the stack requirement of match() slightly.
529    
530    30. Added the '=' option to pcretest to check the setting of unused capturing
531        slots at the end of the pattern, which are documented as being -1, but are
532        not included in the return count.
533    
534    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
535        compiled something random. Now it gives a compile-time error (as does
536        Perl).
537    
538    32. A *MARK encountered during the processing of a positive assertion is now
539        recorded and passed back (compatible with Perl).
540    
541    33. If --only-matching or --colour was set on a pcregrep call whose pattern
542        had alternative anchored branches, the search for a second match in a line
543        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
544        matched the line "0102" twice. The same bug affected patterns that started
545        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
546        twice.
547    
548    34. Previously, PCRE did not allow quantification of assertions. However, Perl
549        does, and because of capturing effects, quantifying parenthesized
550        assertions may at times be useful. Quantifiers are now allowed for
551        parenthesized assertions.
552    
553    35. A minor code tidy in pcre_compile() when checking options for \R usage.
554    
555    36. \g was being checked for fancy things in a character class, when it should
556        just be a literal "g".
557    
558    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
559        appearance of a nested POSIX class supersedes an apparent external class.
560        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
561        unescaped square brackets may also appear as part of class names. For
562        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
563        more like Perl. (But see 8.20/1 above.)
564    
565    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
566        was because it thought it was \N{name}, which is not supported).
567    
568    39. Add minix to OS list not supporting the -S option in pcretest.
569    
570    40. PCRE tries to detect cases of infinite recursion at compile time, but it
571        cannot analyze patterns in sufficient detail to catch mutual recursions
572        such as ((?1))((?2)). There is now a runtime test that gives an error if a
573        subgroup is called recursively as a subpattern for a second time at the
574        same position in the subject string. In previous releases this might have
575        been caught by the recursion limit, or it might have run out of stack.
576    
577    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
578        happen only once. PCRE was, however incorrectly giving a compile time error
579        "recursive call could loop indefinitely" because it cannot analyze the
580        pattern in sufficient detail. The compile time test no longer happens when
581        PCRE is compiling a conditional subpattern, but actual runaway loops are
582        now caught at runtime (see 40 above).
583    
584    42. It seems that Perl allows any characters other than a closing parenthesis
585        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
586        has been changed to be the same.
587    
588    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
589        as not to get warnings when autogen.sh is called. Also changed
590        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
591    
592    44. To help people who use pcregrep to scan files containing exceedingly long
593        lines, the following changes have been made:
594    
595        (a) The default value of the buffer size parameter has been increased from
596            8K to 20K. (The actual buffer used is three times this size.)
597    
598        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
599            PCRE is built.
600    
601        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
602            to be set at run time.
603    
604        (d) Numerical values in pcregrep options can be followed by K or M, for
605            example --buffer-size=50K.
606    
607        (e) If a line being scanned overflows pcregrep's buffer, an error is now
608            given and the return code is set to 2.
609    
610    45. Add a pointer to the latest mark to the callout data block.
611    
612    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
613        partial match of an empty string instead of no match. This was specific to
614        the use of ".".
615    
616    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
617        complete match instead of a partial match. This bug was dependent on both
618        the PCRE_UTF8 and PCRE_DOTALL options being set.
619    
620    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
621        starting byte set, because \b was not being ignored.
622    
623    
624    Version 8.12 15-Jan-2011
625    ------------------------
626    
627    1.  Fixed some typos in the markup of the man pages, and wrote a script that
628        checks for such things as part of the documentation building process.
629    
630    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
631        --match-limit and --recursion-limit options (added for 8.11). In
632        particular, this made one of the standard tests fail. (The integer value
633        went into the wrong half of a long int.)
634    
635    3.  If the --colour option was given to pcregrep with -v (invert match), it
636        did strange things, either producing crazy output, or crashing. It should,
637        of course, ignore a request for colour when reporting lines that do not
638        match.
639    
640    4.  Another pcregrep bug caused similar problems if --colour was specified with
641        -M (multiline) and the pattern match finished with a line ending.
642    
643    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
644        matched in multiline mode, the following line was shown as part of the
645        match. This seems wrong, so I have changed it.
646    
647    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
648        the check for further matches in the same line (so they could be coloured)
649        to overrun the end of the current line. If another match was found, it was
650        incorrectly shown (and then shown again when found in the next line).
651    
652    7.  If pcregrep was compiled under Windows, there was a reference to the
653        function pcregrep_exit() before it was defined. I am assuming this was
654        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
655        reported by a user. I've moved the definition above the reference.
656    
657    
658    Version 8.11 10-Dec-2010
659  ------------------------  ------------------------
660    
661  1.  (*THEN) was not working properly if there were untried alternatives prior  1.  (*THEN) was not working properly if there were untried alternatives prior
662      to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it      to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
663      backtracked to try for "b" instead of moving to the next alternative branch      backtracked to try for "b" instead of moving to the next alternative branch
664      at the same level (in this case, to look for "c"). The Perl documentation      at the same level (in this case, to look for "c"). The Perl documentation
665      is clear that when (*THEN) is backtracked onto, it goes to the "next      is clear that when (*THEN) is backtracked onto, it goes to the "next
666      alternative in the innermost enclosing group".      alternative in the innermost enclosing group".
667    
668  2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern  2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
669      such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should      such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
670      result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and      result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
671      (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides      (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
672      (*THEN).      (*THEN).
673    
674  3.  If \s appeared in a character class, it removed the VT character from  3.  If \s appeared in a character class, it removed the VT character from
675      the class, even if it had been included by some previous item, for example      the class, even if it had been included by some previous item, for example
676      in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part      in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
677      of \s, but is part of the POSIX "space" class.)      of \s, but is part of the POSIX "space" class.)
678    
679  4.  A partial match never returns an empty string (because you can always  4.  A partial match never returns an empty string (because you can always
680      match an empty string at the end of the subject); however the checking for      match an empty string at the end of the subject); however the checking for
681      an empty string was starting at the "start of match" point. This has been      an empty string was starting at the "start of match" point. This has been
# Line 31  Version 8.11 10-Oct-2010 Line 685  Version 8.11 10-Oct-2010
685      (previously it gave "no match").      (previously it gave "no match").
686    
687  5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching  5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
688      of $, \z, \Z, \b, and \B. If the match point is at the end of the string,      of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
689      previously a full match would be given. However, setting PCRE_PARTIAL_HARD      previously a full match would be given. However, setting PCRE_PARTIAL_HARD
690      has an implication that the given string is incomplete (because a partial      has an implication that the given string is incomplete (because a partial
691      match is preferred over a full match). For this reason, these items now      match is preferred over a full match). For this reason, these items now
692      give a partial match in this situation. [Aside: previously, the one case      give a partial match in this situation. [Aside: previously, the one case
693      /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial      /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
694      match rather than a full match, which was wrong by the old rules, but is      match rather than a full match, which was wrong by the old rules, but is
695      now correct.]      now correct.]
696    
697  6.  There was a bug in the handling of #-introduced comments, recognized when  6.  There was a bug in the handling of #-introduced comments, recognized when
698      PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.      PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
699      If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose      If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
700      UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when      UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
701      scanning for the end of the comment. (*Character* 0x85 is an "any" newline,      scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
702      but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several      but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
703      places in pcre_compile().      places in pcre_compile().
704    
705  7.  Related to (6) above, when pcre_compile() was skipping #-introduced  7.  Related to (6) above, when pcre_compile() was skipping #-introduced
706      comments when looking ahead for named forward references to subpatterns,      comments when looking ahead for named forward references to subpatterns,
707      the only newline sequence it recognized was NL. It now handles newlines      the only newline sequence it recognized was NL. It now handles newlines
708      according to the set newline convention.      according to the set newline convention.
709    
710  8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the  8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
711      former, but used strtoul(), whereas pcretest avoided strtoul() but did not      former, but used strtoul(), whereas pcretest avoided strtoul() but did not
712      cater for a lack of strerror(). These oversights have been fixed.      cater for a lack of strerror(). These oversights have been fixed.
713    
714  9.  Added --match-limit and --recursion-limit to pcregrep.  9.  Added --match-limit and --recursion-limit to pcregrep.
715    
716  10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.  10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
717    
718  11. When the -o option was used, pcregrep was setting a return code of 1, even  11. When the -o option was used, pcregrep was setting a return code of 1, even
719      when matches were found, and --line-buffered was not being honoured.      when matches were found, and --line-buffered was not being honoured.
720    
721    12. Added an optional parentheses number to the -o and --only-matching options
722        of pcregrep.
723    
724    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
725        can match an empty string. The code to do it in pcretest and pcredemo
726        needed fixing:
727    
728        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
729            only one byte after an empty string match just before CRLF (this case
730            just got forgotten; "any" and "anycrlf" were OK).
731    
732        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
733            mode when an empty string match preceded an ASCII character followed by
734            a non-ASCII character. (The code for advancing by one character rather
735            than one byte was nonsense.)
736    
737        (c) The pcredemo.c sample program did not have any code at all to handle
738            the cases when CRLF is a valid newline sequence.
739    
740    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
741        as a starting offset was within the subject string. There is now a new
742        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
743        negative or greater than the length of the string. In order to test this,
744        pcretest is extended to allow the setting of negative starting offsets.
745    
746    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
747        starting offset points to the beginning of a UTF-8 character was
748        unnecessarily clumsy. I tidied it up.
749    
750    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
751        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
752    
753    17. Nobody had reported that the --include_dir option, which was added in
754        release 7.7 should have been called --include-dir (hyphen, not underscore)
755        for compatibility with GNU grep. I have changed it to --include-dir, but
756        left --include_dir as an undocumented synonym, and the same for
757        --exclude-dir, though that is not available in GNU grep, at least as of
758        release 2.5.4.
759    
760    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
761        characters from a string of bytes) have been redefined so as not to use
762        loops, in order to improve performance in some environments. At the same
763        time, I abstracted some of the common code into auxiliary macros to save
764        repetition (this should not affect the compiled code).
765    
766    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
767        compile-time error is now given if \c is not followed by an ASCII
768        character, that is, a byte less than 128. (In EBCDIC mode, the code is
769        different, and any byte value is allowed.)
770    
771    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
772        START_OPTIMIZE option, which is now allowed at compile time - but just
773        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
774        to pcregrep and other applications that have no direct access to PCRE
775        options. The new /Y option in pcretest sets this option when calling
776        pcre_compile().
777    
778    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
779        back references. Groups containing recursive back references were forced to
780        be atomic by that change, but in the case of named groups, the amount of
781        memory required was incorrectly computed, leading to "Failed: internal
782        error: code overflow". This has been fixed.
783    
784    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
785        pcretest.c, to avoid build problems in some Borland environments.
786    
787    
788  Version 8.10 25-Jun-2010  Version 8.10 25-Jun-2010
789  ------------------------  ------------------------

Legend:
Removed from v.564  
changed lines
  Added in v.957

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12