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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.723  
changed lines
  Added in v.1265

  ViewVC Help
Powered by ViewVC 1.1.5