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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.620  
changed lines
  Added in v.1239

  ViewVC Help
Powered by ViewVC 1.1.5