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

Diff of /code/trunk/ChangeLog

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

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

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

  ViewVC Help
Powered by ViewVC 1.1.5