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

  ViewVC Help
Powered by ViewVC 1.1.5