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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.608  
changed lines
  Added in v.1172

  ViewVC Help
Powered by ViewVC 1.1.5