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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.605  
changed lines
  Added in v.1053

  ViewVC Help
Powered by ViewVC 1.1.5