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

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

  ViewVC Help
Powered by ViewVC 1.1.5