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

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

  ViewVC Help
Powered by ViewVC 1.1.5