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

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

  ViewVC Help
Powered by ViewVC 1.1.5