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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.539  
changed lines
  Added in v.991

  ViewVC Help
Powered by ViewVC 1.1.5