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

Diff of /code/trunk/ChangeLog

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

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

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

  ViewVC Help
Powered by ViewVC 1.1.5