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

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

  ViewVC Help
Powered by ViewVC 1.1.5