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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.657  
changed lines
  Added in v.1328

  ViewVC Help
Powered by ViewVC 1.1.5