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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.659  
changed lines
  Added in v.1260

  ViewVC Help
Powered by ViewVC 1.1.5