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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.622  
changed lines
  Added in v.1190

  ViewVC Help
Powered by ViewVC 1.1.5