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

Diff of /code/trunk/ChangeLog

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

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

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

  ViewVC Help
Powered by ViewVC 1.1.5