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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.780  
changed lines
  Added in v.1284

  ViewVC Help
Powered by ViewVC 1.1.5