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

Diff of /code/trunk/ChangeLog

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

revision 564 by ph10, Sun Oct 31 16:07:24 2010 UTC revision 1322 by zherczeg, Wed May 1 19:42:31 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.11 10-Oct-2010  Version 8.33 28-April-2013
5    --------------------------
6    
7    1.  Added 'U' to some constants that are compared to unsigned integers, to
8        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
9        variables that are added to signed variables, to ensure the result is
10        signed and can be negated.
11    
12    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
13        CMake config files.
14    
15    3.  Revise the creation of config.h.generic so that all boolean macros are
16        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
17        overriding via -D on the command line possible.
18    
19    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
20        to unsigned int is reported to make a quite noticeable speed difference in
21        a specific Windows environment. Testing on Linux did also appear to show
22        some benefit (and it is clearly not harmful). Also fixed the definition of
23        Xop which should be unsigned.
24    
25    5.  Related to (4), changing the definition of the intermediate variable cc
26        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
27        improvements.
28    
29    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
30        unnecessary spaces.
31    
32    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
33        and later.
34    
35    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
36    
37    9.  Optimizing fast_forward_start_bits in JIT.
38    
39    10. Adding experimental support for callouts in JIT, and fixing some
40        issues revealed during this work. Namely:
41    
42        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
43    
44        (b) Minimum length was not checked before the matching is started.
45    
46    11. The value of capture_last that is passed to callouts was incorrect in some
47        cases when there was a capture on one path that was subsequently abandoned
48        after a backtrack. Also, the capture_last value is now reset after a
49        recursion, since all captures are also reset in this case.
50    
51    12. The interpreter no longer returns the "too many substrings" error in the
52        case when an overflowing capture is in a branch that is subsequently
53        abandoned after a backtrack.
54    
55    13. In the pathological case when an offset vector of size 2 is used, pcretest
56        now prints out the matched string after a yield of 0 or 1.
57    
58    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
59        Only supported by the JIT compiler at the moment.
60    
61    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
62    
63    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
64        offset of the starting point of the matching process, provided the offsets
65        vector is large enough.
66    
67    17. The \A escape now records a lookbehind value of 1, though its execution
68        does not actually inspect the previous character. This is to ensure that,
69        in partial multi-segment matching, at least one character from the old
70        segment is retained when a new segment is processed. Otherwise, if there
71        are no lookbehinds in the pattern, \A might match incorrectly at the start
72        of a new segment.
73    
74    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
75    
76    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
77        gives some modest performance improvement in 8-bit mode.
78    
79    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
80        be expressed in certain programming languages using Universal Character
81        Names.
82    
83    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
84        which points out that "non characters" are not "characters that may not
85        appear in Unicode strings" but rather "characters that are reserved for
86        internal use and have only local meaning".
87    
88    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
89        there was a conditional group that depended on an assertion, if the
90        assertion was false, the callout that immediately followed the alternation
91        in the condition was skipped when pcre_exec() was used for matching.
92    
93    23. Allow an explicit callout to be inserted before an assertion that is the
94        condition for a conditional group, for compatibility with automatic
95        callouts, which always insert a callout at this point.
96    
97    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
98        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
99    
100    25. (*PRUNE) is now supported by the JIT compiler.
101    
102    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
103    
104    27. Fix the case where there are two or more SKIPs with arguments that may be
105        ignored.
106    
107    28. (*SKIP) is now supported by the JIT compiler.
108    
109    29. (*THEN) is now supported by the JIT compiler.
110    
111    30. Update RunTest with additional test selector options.
112    
113    31. The way PCRE handles backtracking verbs has been changed in two ways.
114    
115        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
116        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
117        backtracking. In some cases this makes it more Perl-compatible, but Perl's
118        rather obscure rules do not always do the same thing.
119    
120        (2) Previously, backtracking verbs were confined within assertions. This is
121        no longer the case for positive assertions, except for (*ACCEPT). Again,
122        this sometimes improves Perl compatibility, and sometimes does not.
123    
124    32. A number of tests that were in test 2 because Perl did things differently
125        have been moved to test 1, because either Perl or PCRE has changed, and
126        these tests are now compatible.
127    
128    32. Control verbs are handled in the same way in JIT and interpreter.
129    
130    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
131        contained a forward subroutine reference caused a compile error.
132    
133    34. Auto-detect and optimize limited repetitions in JIT.
134    
135    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
136        blocking (*UTF) etc.
137    
138    36. In the interpreter, maximizing pattern repetitions for characters and
139        character types now use tail recursion, which reduces stack usage.
140    
141    37. The value of the max lookbehind was not correctly preserved if a compiled
142        and saved regex was reloaded on a host of different endianness.
143    
144    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
145        of the compiled pattern block, expand the flags field from 16 to 32 bits
146        because it was almost full.
147    
148    39. Try madvise first before posix_madvise.
149    
150    
151    Version 8.32 30-November-2012
152    -----------------------------
153    
154    1.  Improved JIT compiler optimizations for first character search and single
155        character iterators.
156    
157    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
158        Patch by Daniel Richard G.
159    
160    3.  Single character iterator optimizations in the JIT compiler.
161    
162    4.  Improved JIT compiler optimizations for character ranges.
163    
164    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
165        Reported by Giuseppe D'Angelo.
166    
167    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
168        of a line, was being set incorrectly in cases where .* appeared inside
169        atomic brackets at the start of a pattern, or where there was a subsequent
170        *PRUNE or *SKIP.
171    
172    7.  Improved instruction cache flush for POWER/PowerPC.
173        Patch by Daniel Richard G.
174    
175    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
176        grep:
177    
178        (a) There is now no limit to the number of patterns to be matched.
179    
180        (b) An error is given if a pattern is too long.
181    
182        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
183            are now supported.
184    
185        (d) --exclude-from and --include-from (multiple use) have been added.
186    
187        (e) Exclusions and inclusions now apply to all files and directories, not
188            just to those obtained from scanning a directory recursively.
189    
190        (f) Multiple uses of -f and --file-list are now supported.
191    
192        (g) In a Windows environment, the default for -d has been changed from
193            "read" (the GNU grep default) to "skip", because otherwise the presence
194            of a directory in the file list provokes an error.
195    
196        (h) The documentation has been revised and clarified in places.
197    
198    9.  Improve the matching speed of capturing brackets.
199    
200    10. Changed the meaning of \X so that it now matches a Unicode extended
201        grapheme cluster.
202    
203    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
204        out POSIX threads when JIT support is configured.
205    
206    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
207    
208    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
209        structure could go wrong in environments where size_t is not the same size
210        as int.
211    
212    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
213        set.
214    
215    15. The EBCDIC support had decayed; later updates to the code had included
216        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
217        general tidy up of EBCDIC-related issues, and the documentation was also
218        not quite right. There is now a test that can be run on ASCII systems to
219        check some of the EBCDIC-related things (but is it not a full test).
220    
221    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
222        in a small tidy to the code.
223    
224    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
225    
226    18. If the --only-matching (-o) option in pcregrep is specified multiple
227        times, each one causes appropriate output. For example, -o1 -o2 outputs the
228        substrings matched by the 1st and 2nd capturing parentheses. A separating
229        string can be specified by --om-separator (default empty).
230    
231    19. Improving the first n character searches.
232    
233    20. Turn case lists for horizontal and vertical white space into macros so that
234        they are defined only once.
235    
236    21. This set of changes together give more compatible Unicode case-folding
237        behaviour for characters that have more than one other case when UCP
238        support is available.
239    
240        (a) The Unicode property table now has offsets into a new table of sets of
241            three or more characters that are case-equivalent. The MultiStage2.py
242            script that generates these tables (the pcre_ucd.c file) now scans
243            CaseFolding.txt instead of UnicodeData.txt for character case
244            information.
245    
246        (b) The code for adding characters or ranges of characters to a character
247            class has been abstracted into a generalized function that also handles
248            case-independence. In UTF-mode with UCP support, this uses the new data
249            to handle characters with more than one other case.
250    
251        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
252            whose other case is greater than 256 are now correctly matched
253            caselessly. Previously, the high codepoint matched the low one, but not
254            vice versa.
255    
256        (d) The processing of \h, \H, \v, and \ in character classes now makes use
257            of the new class addition function, using character lists defined as
258            macros alongside the case definitions of 20 above.
259    
260        (e) Caseless back references now work with characters that have more than
261            one other case.
262    
263        (f) General caseless matching of characters with more than one other case
264            is supported.
265    
266    22. Unicode character properties were updated from Unicode 6.2.0
267    
268    23. Improved CMake support under Windows. Patch by Daniel Richard G.
269    
270    24. Add support for 32-bit character strings, and UTF-32
271    
272    25. Major JIT compiler update (code refactoring and bugfixing).
273        Experimental Sparc 32 support is added.
274    
275    26. Applied a modified version of Daniel Richard G's patch to create
276        pcre.h.generic and config.h.generic by "make" instead of in the
277        PrepareRelease script.
278    
279    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
280        pcre_compile.c when checking for a zero character.
281    
282    28. Introducing a native interface for JIT. Through this interface, the compiled
283        machine code can be directly executed. The purpose of this interface is to
284        provide fast pattern matching, so several sanity checks are not performed.
285        However, feature tests are still performed. The new interface provides
286        1.4x speedup compared to the old one.
287    
288    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
289        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
290        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
291    
292    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
293        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
294        the "old" RFC 2279). Instead, it ended up passing a negative length to
295        pcre_exec().
296    
297    31. Add support for GCC's visibility feature to hide internal functions.
298    
299    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
300        "unknown -C option" after outputting 0 or 1.
301    
302    33. There is now support for generating a code coverage report for the test
303        suite in environments where gcc is the compiler and lcov is installed. This
304        is mainly for the benefit of the developers.
305    
306    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
307        unaddressable using valgrind annotations, allowing valgrind to detect
308        invalid memory accesses. This is mainly for the benefit of the developers.
309    
310    25. (*UTF) can now be used to start a pattern in any of the three libraries.
311    
312    26. Give configure error if --enable-cpp but no C++ compiler found.
313    
314    
315    Version 8.31 06-July-2012
316    -------------------------
317    
318    1.  Fixing a wrong JIT test case and some compiler warnings.
319    
320    2.  Removed a bashism from the RunTest script.
321    
322    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
323        to unsigned type, result still unsigned" that was given by an MS compiler
324        on encountering the code "-sizeof(xxx)".
325    
326    4.  Partial matching support is added to the JIT compiler.
327    
328    5.  Fixed several bugs concerned with partial matching of items that consist
329        of more than one character:
330    
331        (a) /^(..)\1/ did not partially match "aba" because checking references was
332            done on an "all or nothing" basis. This also applied to repeated
333            references.
334    
335        (b) \R did not give a hard partial match if \r was found at the end of the
336            subject.
337    
338        (c) \X did not give a hard partial match after matching one or more
339            characters at the end of the subject.
340    
341        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
342            a partial match for the string "\r".
343    
344        (e) When newline was set to CRLF, the metacharacter "." did not recognize
345            a partial match for a CR character at the end of the subject string.
346    
347    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
348        running pcretest, the text "(JIT)" added to the output whenever JIT is
349        actually used to run the match.
350    
351    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
352        or /S+[+] with a digit between 1 and 7.
353    
354    8.  OP_NOT now supports any UTF character not just single-byte ones.
355    
356    9.  (*MARK) control verb is now supported by the JIT compiler.
357    
358    10. The command "./RunTest list" lists the available tests without actually
359        running any of them. (Because I keep forgetting what they all are.)
360    
361    11. Add PCRE_INFO_MAXLOOKBEHIND.
362    
363    12. Applied a (slightly modified) user-supplied patch that improves performance
364        when the heap is used for recursion (compiled with --disable-stack-for-
365        recursion). Instead of malloc and free for each heap frame each time a
366        logical recursion happens, frames are retained on a chain and re-used where
367        possible. This sometimes gives as much as 30% improvement.
368    
369    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
370        call.
371    
372    14. As documented, (*COMMIT) is now confined to within a positive assertion.
373    
374    15. It is now possible to link pcretest with libedit as an alternative to
375        libreadline.
376    
377    16. (*COMMIT) control verb is now supported by the JIT compiler.
378    
379    17. The Unicode data tables have been updated to Unicode 6.1.0.
380    
381    18. Added --file-list option to pcregrep.
382    
383    19. Added binary file support to pcregrep, including the -a, --binary-files,
384        -I, and --text options.
385    
386    20. The madvise function is renamed for posix_madvise for QNX compatibility
387        reasons. Fixed by Giuseppe D'Angelo.
388    
389    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
390    
391    22. Changed the option for creating symbolic links for 16-bit man pages from
392        -s to -sf so that re-installing does not cause issues.
393    
394    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
395    
396    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
397        matches in certain environments (the workspace was not being correctly
398        retained). Also added to pcre_dfa_exec() a simple plausibility check on
399        some of the workspace data at the beginning of a restart.
400    
401    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
402        was not doing so when it should - probably a typo introduced by SVN 528
403        (change 8.10/14).
404    
405    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
406        \w+ when the character tables indicated that \x{c4} was a word character.
407        There were several related cases, all because the tests for doing a table
408        lookup were testing for characters less than 127 instead of 255.
409    
410    27. If a pattern contains capturing parentheses that are not used in a match,
411        their slots in the ovector are set to -1. For those that are higher than
412        any matched groups, this happens at the end of processing. In the case when
413        there were back references that the ovector was too small to contain
414        (causing temporary malloc'd memory to be used during matching), and the
415        highest capturing number was not used, memory off the end of the ovector
416        was incorrectly being set to -1. (It was using the size of the temporary
417        memory instead of the true size.)
418    
419    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
420        ovector size, it uses memory at the end of the block that it has got.
421    
422    29. Check for an overlong MARK name and give an error at compile time. The
423        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
424    
425    30. JIT compiler update.
426    
427    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
428        Rill for the patch.
429    
430    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
431    
432    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
433    
434    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
435        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
436        was enabled.
437    
438    35. Improve JIT code generation for greedy plus quantifier.
439    
440    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
441        1 to "aa" instead of to an empty string. The bug affected repeated groups
442        that could potentially match an empty string.
443    
444    37. Optimizing single character iterators in JIT.
445    
446    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
447        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
448        codepoints that are too big for the mode are faulted, and in a UTF mode,
449        disallowed codepoints are also faulted.
450    
451    39. If PCRE was compiled with UTF support, in three places in the DFA
452        matcher there was code that should only have been obeyed in UTF mode, but
453        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
454        processing when bytes with values greater than 127 were present. In 16-bit
455        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
456        both cases the values are those that cannot be the first data item in a UTF
457        character. The three items that might have provoked this were recursions,
458        possessively repeated groups, and atomic groups.
459    
460    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
461        and pcregrep, because some OS require shared objects to be explicitly
462        passed to ld, causing the link step to fail if they are not.
463    
464    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
465        mode, patterns that started with \h* or \R* might be incorrectly matched.
466    
467    
468    Version 8.30 04-February-2012
469    -----------------------------
470    
471    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
472        name is defined in ctype.h.
473    
474    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
475        only in quite long subpatterns.
476    
477    3.  Removed the function pcre_info(), which has been obsolete and deprecated
478        since it was replaced by pcre_fullinfo() in February 2000.
479    
480    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
481        match a (*MARK), and the match failed at the start of the subject, a
482        reference to memory before the start of the subject could occur. This bug
483        was introduced by fix 17 of release 8.21.
484    
485    5.  A reference to an unset group with zero minimum repetition was giving
486        totally wrong answers (in non-JavaScript-compatibility mode). For example,
487        /(another)?(\1?)test/ matched against "hello world test". This bug was
488        introduced in release 8.13.
489    
490    6.  Add support for 16-bit character strings (a large amount of work involving
491        many changes and refactorings).
492    
493    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
494        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
495        from a file.
496    
497    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
498        rounding is not applied in this particular case).
499    
500    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
501        if they appear, or are escaped, in patterns.
502    
503    10. Get rid of a number of -Wunused-but-set-variable warnings.
504    
505    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
506        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
507        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
508        also returns the mark "x". This bug applied to capturing parentheses,
509        non-capturing parentheses, and atomic parentheses. It also applied to some
510        assertions.
511    
512    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
513        information out of configure.ac instead of relying on pcre.h.generic, which
514        is not stored in the repository.
515    
516    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
517        -lreadline.
518    
519    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
520    
521    15. Applied Graycode's patch to put the top-level frame on the stack rather
522        than the heap when not using the stack for recursion. This gives a
523        performance improvement in many cases when recursion is not deep.
524    
525    16. Experimental code added to "pcretest -C" to output the stack frame size.
526    
527    
528    Version 8.21 12-Dec-2011
529    ------------------------
530    
531    1.  Updating the JIT compiler.
532    
533    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
534        are added as well.
535    
536    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
537        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
538        calling _pcre_jit_exec. Some extra comments are added.
539    
540    4.  (*MARK) settings inside atomic groups that do not contain any capturing
541        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
542        was introduced by change 18 for 8.20.
543    
544    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
545        ECMA-262 standard.
546    
547    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
548        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
549        This bug was probably introduced by change 9 of 8.13.
550    
551    7.  While fixing 6 above, I noticed that a number of other items were being
552        incorrectly rejected as "not fixed length". This arose partly because newer
553        opcodes had not been added to the fixed-length checking code. I have (a)
554        corrected the bug and added tests for these items, and (b) arranged for an
555        error to occur if an unknown opcode is encountered while checking for fixed
556        length instead of just assuming "not fixed length". The items that were
557        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
558        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
559        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
560    
561    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
562        being incorrectly compiled and would have given unpredicatble results.
563    
564    9.  A possessively repeated subpattern with minimum repeat count greater than
565        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
566        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
567        the first (A) could occur when it should not.
568    
569    10. Add a cast and remove a redundant test from the code.
570    
571    11. JIT should use pcre_malloc/pcre_free for allocation.
572    
573    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
574        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
575        is anything other than /usr, -L is still shown).
576    
577    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
578    
579    14. Perl does not support \N without a following name in a [] class; PCRE now
580        also gives an error.
581    
582    15. If a forward reference was repeated with an upper limit of around 2000,
583        it caused the error "internal error: overran compiling workspace". The
584        maximum number of forward references (including repeats) was limited by the
585        internal workspace, and dependent on the LINK_SIZE. The code has been
586        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
587        the default depends on LINK_SIZE. There is a new upper limit (for safety)
588        of around 200,000 forward references. While doing this, I also speeded up
589        the filling in of repeated forward references.
590    
591    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
592        incorrectly expecting the subject to contain another "a" after the start.
593    
594    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
595        in the match, the SKIP should be ignored. This was not happening; instead
596        the SKIP was being treated as NOMATCH. For patterns such as
597        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
598        tested.
599    
600    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
601        now much more compatible with Perl, in particular in cases where the result
602        is a non-match for a non-anchored pattern. For example, if
603        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
604        "m", where previously it did not return a name. A side effect of this
605        change is that for partial matches, the last encountered mark name is
606        returned, as for non matches. A number of tests that were previously not
607        Perl-compatible have been moved into the Perl-compatible test files. The
608        refactoring has had the pleasing side effect of removing one argument from
609        the match() function, thus reducing its stack requirements.
610    
611    19. If the /S+ option was used in pcretest to study a pattern using JIT,
612        subsequent uses of /S (without +) incorrectly behaved like /S+.
613    
614    21. Retrieve executable code size support for the JIT compiler and fixing
615        some warnings.
616    
617    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
618        not work when the shorter character appeared right at the end of the
619        subject string.
620    
621    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
622        systems.
623    
624    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
625        output it when the /M option is used in pcretest.
626    
627    25. The CheckMan script was not being included in the distribution. Also, added
628        an explicit "perl" to run Perl scripts from the PrepareRelease script
629        because this is reportedly needed in Windows.
630    
631    26. If study data was being save in a file and studying had not found a set of
632        "starts with" bytes for the pattern, the data written to the file (though
633        never used) was taken from uninitialized memory and so caused valgrind to
634        complain.
635    
636    27. Updated RunTest.bat as provided by Sheri Pierce.
637    
638    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
639    
640    29. Computation of memory usage for the table of capturing group names was
641        giving an unnecessarily large value.
642    
643    
644    Version 8.20 21-Oct-2011
645    ------------------------
646    
647    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
648        a POSIX class. After further experiments with Perl, which convinced me that
649        Perl has bugs and confusions, a closing square bracket is no longer allowed
650        in a POSIX name. This bug also affected patterns with classes that started
651        with full stops.
652    
653    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
654        captured substring, but while checking the failing first alternative,
655        substring 1 is temporarily captured. If the output vector supplied to
656        pcre_exec() was not big enough for this capture, the yield of the function
657        was still zero ("insufficient space for captured substrings"). This cannot
658        be totally fixed without adding another stack variable, which seems a lot
659        of expense for a edge case. However, I have improved the situation in cases
660        such as /(a)(b)x|abc/ matched against "abc", where the return code
661        indicates that fewer than the maximum number of slots in the ovector have
662        been set.
663    
664    3.  Related to (2) above: when there are more back references in a pattern than
665        slots in the output vector, pcre_exec() uses temporary memory during
666        matching, and copies in the captures as far as possible afterwards. It was
667        using the entire output vector, but this conflicts with the specification
668        that only 2/3 is used for passing back captured substrings. Now it uses
669        only the first 2/3, for compatibility. This is, of course, another edge
670        case.
671    
672    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
673        main code base, and can be used by building with --enable-jit. When this is
674        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
675        runtime --no-jit option is given.
676    
677    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
678        ovector, the return from the function was zero, implying that there were
679        other matches that did not fit. The correct "exactly full" value is now
680        returned.
681    
682    6.  If a subpattern that was called recursively or as a subroutine contained
683        (*PRUNE) or any other control that caused it to give a non-standard return,
684        invalid errors such as "Error -26 (nested recursion at the same subject
685        position)" or even infinite loops could occur.
686    
687    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
688        computing the minimum length on reaching *ACCEPT, and so ended up with the
689        wrong value of 1 rather than 0. Further investigation indicates that
690        computing a minimum subject length in the presence of *ACCEPT is difficult
691        (think back references, subroutine calls), and so I have changed the code
692        so that no minimum is registered for a pattern that contains *ACCEPT.
693    
694    8.  If (*THEN) was present in the first (true) branch of a conditional group,
695        it was not handled as intended. [But see 16 below.]
696    
697    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
698        Sheri Pierce.
699    
700    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
701        the first byte in a match must be "a".
702    
703    11. Change 17 for 8.13 increased the recursion depth for patterns like
704        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
705        pattern contains any instances of (*THEN). If it does not, the old
706        optimizations are restored. It would be nice to do this on a per-group
707        basis, but at the moment that is not feasible.
708    
709    12. In some environments, the output of pcretest -C is CRLF terminated. This
710        broke RunTest's code that checks for the link size. A single white space
711        character after the value is now allowed for.
712    
713    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
714        For "fr", it uses the Windows-specific input and output files.
715    
716    14. If (*THEN) appeared in a group that was called recursively or as a
717        subroutine, it did not work as intended. [But see next item.]
718    
719    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
720        pattern fragments (but not containing any | characters). If A and B are
721        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
722        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
723        D. In other words, Perl considers parentheses that do not contain any |
724        characters to be part of a surrounding alternative, whereas PCRE was
725        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
726        differently. PCRE now behaves in the same way as Perl, except in the case
727        of subroutine/recursion calls such as (?1) which have in any case always
728        been different (but PCRE had them first :-).
729    
730    16. Related to 15 above: Perl does not treat the | in a conditional group as
731        creating alternatives. Such a group is treated in the same way as an
732        ordinary group without any | characters when processing (*THEN). PCRE has
733        been changed to match Perl's behaviour.
734    
735    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
736        RunGrepTest script failed.
737    
738    18. Change 22 for version 13 caused atomic groups to use more stack. This is
739        inevitable for groups that contain captures, but it can lead to a lot of
740        stack use in large patterns. The old behaviour has been restored for atomic
741        groups that do not contain any capturing parentheses.
742    
743    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
744        suppress the check for a minimum subject length at run time. (If it was
745        given to pcre_exec() or pcre_dfa_exec() it did work.)
746    
747    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
748        fail to work when decoding hex characters in data strings in EBCDIC
749        environments.
750    
751    21. It appears that in at least one Mac OS environment, the isxdigit() function
752        is implemented as a macro that evaluates to its argument more than once,
753        contravening the C 90 Standard (I haven't checked a later standard). There
754        was an instance in pcretest which caused it to go wrong when processing
755        \x{...} escapes in subject strings. The has been rewritten to avoid using
756        things like p++ in the argument of isxdigit().
757    
758    
759    Version 8.13 16-Aug-2011
760    ------------------------
761    
762    1.  The Unicode data tables have been updated to Unicode 6.0.0.
763    
764    2.  Two minor typos in pcre_internal.h have been fixed.
765    
766    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
767        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
768        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
769    
770    4.  There were a number of related bugs in the code for matching backrefences
771        caselessly in UTF-8 mode when codes for the characters concerned were
772        different numbers of bytes. For example, U+023A and U+2C65 are an upper
773        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
774        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
775        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
776        2-byte code at the end of the subject (it thought there wasn't enough data
777        left).
778    
779    5.  Comprehensive information about what went wrong is now returned by
780        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
781        as the output vector has at least 2 elements. The offset of the start of
782        the failing character and a reason code are placed in the vector.
783    
784    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
785        now returned is for the first byte of the failing character, instead of the
786        last byte inspected. This is an incompatible change, but I hope it is small
787        enough not to be a problem. It makes the returned offset consistent with
788        pcre_exec() and pcre_dfa_exec().
789    
790    7.  pcretest now gives a text phrase as well as the error number when
791        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
792        failure, the offset and reason code are output.
793    
794    8.  When \R was used with a maximizing quantifier it failed to skip backwards
795        over a \r\n pair if the subsequent match failed. Instead, it just skipped
796        back over a single character (\n). This seems wrong (because it treated the
797        two characters as a single entity when going forwards), conflicts with the
798        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
799        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
800        has been changed.
801    
802    9.  Some internal refactoring has changed the processing so that the handling
803        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
804        time (the PCRE_DOTALL option was changed this way some time ago: version
805        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
806        which was always a bit of a fudge. It also means that there is one less
807        argument for the match() function, which reduces its stack requirements
808        slightly. This change also fixes an incompatibility with Perl: the pattern
809        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
810    
811    10. More internal refactoring has drastically reduced the number of recursive
812        calls to match() for possessively repeated groups such as (abc)++ when
813        using pcre_exec().
814    
815    11. While implementing 10, a number of bugs in the handling of groups were
816        discovered and fixed:
817    
818        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
819        (a|)*(?1) gave a compile-time internal error.
820        ((a|)+)+  did not notice that the outer group could match an empty string.
821        (^a|^)+   was not marked as anchored.
822        (.*a|.*)+ was not marked as matching at start or after a newline.
823    
824    12. Yet more internal refactoring has removed another argument from the match()
825        function. Special calls to this function are now indicated by setting a
826        value in a variable in the "match data" data block.
827    
828    13. Be more explicit in pcre_study() instead of relying on "default" for
829        opcodes that mean there is no starting character; this means that when new
830        ones are added and accidentally left out of pcre_study(), testing should
831        pick them up.
832    
833    14. The -s option of pcretest has been documented for ages as being an old
834        synonym of -m (show memory usage). I have changed it to mean "force study
835        for every regex", that is, assume /S for every regex. This is similar to -i
836        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
837        using it. It makes it easier to run collections of tests with and without
838        study enabled, and thereby test pcre_study() more easily. All the standard
839        tests are now run with and without -s (but some patterns can be marked as
840        "never study" - see 20 below).
841    
842    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
843        restoration of the capturing data to the outer values was not happening
844        correctly.
845    
846    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
847        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
848        pattern had matched an empty string, and so incorrectly returned a no
849        match.
850    
851    17. There was optimizing code for the last branch of non-capturing parentheses,
852        and also for the obeyed branch of a conditional subexpression, which used
853        tail recursion to cut down on stack usage. Unfortunately, now that there is
854        the possibility of (*THEN) occurring in these branches, tail recursion is
855        no longer possible because the return has to be checked for (*THEN). These
856        two optimizations have therefore been removed. [But see 8.20/11 above.]
857    
858    18. If a pattern containing \R was studied, it was assumed that \R always
859        matched two bytes, thus causing the minimum subject length to be
860        incorrectly computed because \R can also match just one byte.
861    
862    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
863        was incorrectly computed.
864    
865    20. If /S is present twice on a test pattern in pcretest input, it now
866        *disables* studying, thereby overriding the use of -s on the command line
867        (see 14 above). This is necessary for one or two tests to keep the output
868        identical in both cases.
869    
870    21. When (*ACCEPT) was used in an assertion that matched an empty string and
871        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
872    
873    22. When an atomic group that contained a capturing parenthesis was
874        successfully matched, but the branch in which it appeared failed, the
875        capturing was not being forgotten if a higher numbered group was later
876        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
877        group 1 to "a", when in fact it should be unset. This applied to multi-
878        branched capturing and non-capturing groups, repeated or not, and also to
879        positive assertions (capturing in negative assertions does not happen
880        in PCRE) and also to nested atomic groups.
881    
882    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
883        subject after a captured substring, to make it easier to tell which of a
884        number of identical substrings has been captured.
885    
886    24. The way atomic groups are processed by pcre_exec() has been changed so that
887        if they are repeated, backtracking one repetition now resets captured
888        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
889        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
890        "aaa". Previously, it would have been "a". As part of this code
891        refactoring, the way recursive calls are handled has also been changed.
892    
893    25. If an assertion condition captured any substrings, they were not passed
894        back unless some other capturing happened later. For example, if
895        (?(?=(a))a) was matched against "a", no capturing was returned.
896    
897    26. When studying a pattern that contained subroutine calls or assertions,
898        the code for finding the minimum length of a possible match was handling
899        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
900        group 1 called group 2 while simultaneously a separate group 2 called group
901        1). A stack overflow occurred in this case. I have fixed this by limiting
902        the recursion depth to 10.
903    
904    27. Updated RunTest.bat in the distribution to the version supplied by Tom
905        Fortmann. This supports explicit test numbers on the command line, and has
906        argument validation and error reporting.
907    
908    28. An instance of \X with an unlimited repeat could fail if at any point the
909        first character it looked at was a mark character.
910    
911    29. Some minor code refactoring concerning Unicode properties and scripts
912        should reduce the stack requirement of match() slightly.
913    
914    30. Added the '=' option to pcretest to check the setting of unused capturing
915        slots at the end of the pattern, which are documented as being -1, but are
916        not included in the return count.
917    
918    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
919        compiled something random. Now it gives a compile-time error (as does
920        Perl).
921    
922    32. A *MARK encountered during the processing of a positive assertion is now
923        recorded and passed back (compatible with Perl).
924    
925    33. If --only-matching or --colour was set on a pcregrep call whose pattern
926        had alternative anchored branches, the search for a second match in a line
927        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
928        matched the line "0102" twice. The same bug affected patterns that started
929        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
930        twice.
931    
932    34. Previously, PCRE did not allow quantification of assertions. However, Perl
933        does, and because of capturing effects, quantifying parenthesized
934        assertions may at times be useful. Quantifiers are now allowed for
935        parenthesized assertions.
936    
937    35. A minor code tidy in pcre_compile() when checking options for \R usage.
938    
939    36. \g was being checked for fancy things in a character class, when it should
940        just be a literal "g".
941    
942    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
943        appearance of a nested POSIX class supersedes an apparent external class.
944        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
945        unescaped square brackets may also appear as part of class names. For
946        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
947        more like Perl. (But see 8.20/1 above.)
948    
949    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
950        was because it thought it was \N{name}, which is not supported).
951    
952    39. Add minix to OS list not supporting the -S option in pcretest.
953    
954    40. PCRE tries to detect cases of infinite recursion at compile time, but it
955        cannot analyze patterns in sufficient detail to catch mutual recursions
956        such as ((?1))((?2)). There is now a runtime test that gives an error if a
957        subgroup is called recursively as a subpattern for a second time at the
958        same position in the subject string. In previous releases this might have
959        been caught by the recursion limit, or it might have run out of stack.
960    
961    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
962        happen only once. PCRE was, however incorrectly giving a compile time error
963        "recursive call could loop indefinitely" because it cannot analyze the
964        pattern in sufficient detail. The compile time test no longer happens when
965        PCRE is compiling a conditional subpattern, but actual runaway loops are
966        now caught at runtime (see 40 above).
967    
968    42. It seems that Perl allows any characters other than a closing parenthesis
969        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
970        has been changed to be the same.
971    
972    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
973        as not to get warnings when autogen.sh is called. Also changed
974        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
975    
976    44. To help people who use pcregrep to scan files containing exceedingly long
977        lines, the following changes have been made:
978    
979        (a) The default value of the buffer size parameter has been increased from
980            8K to 20K. (The actual buffer used is three times this size.)
981    
982        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
983            PCRE is built.
984    
985        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
986            to be set at run time.
987    
988        (d) Numerical values in pcregrep options can be followed by K or M, for
989            example --buffer-size=50K.
990    
991        (e) If a line being scanned overflows pcregrep's buffer, an error is now
992            given and the return code is set to 2.
993    
994    45. Add a pointer to the latest mark to the callout data block.
995    
996    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
997        partial match of an empty string instead of no match. This was specific to
998        the use of ".".
999    
1000    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
1001        complete match instead of a partial match. This bug was dependent on both
1002        the PCRE_UTF8 and PCRE_DOTALL options being set.
1003    
1004    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
1005        starting byte set, because \b was not being ignored.
1006    
1007    
1008    Version 8.12 15-Jan-2011
1009    ------------------------
1010    
1011    1.  Fixed some typos in the markup of the man pages, and wrote a script that
1012        checks for such things as part of the documentation building process.
1013    
1014    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
1015        --match-limit and --recursion-limit options (added for 8.11). In
1016        particular, this made one of the standard tests fail. (The integer value
1017        went into the wrong half of a long int.)
1018    
1019    3.  If the --colour option was given to pcregrep with -v (invert match), it
1020        did strange things, either producing crazy output, or crashing. It should,
1021        of course, ignore a request for colour when reporting lines that do not
1022        match.
1023    
1024    4.  Another pcregrep bug caused similar problems if --colour was specified with
1025        -M (multiline) and the pattern match finished with a line ending.
1026    
1027    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
1028        matched in multiline mode, the following line was shown as part of the
1029        match. This seems wrong, so I have changed it.
1030    
1031    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
1032        the check for further matches in the same line (so they could be coloured)
1033        to overrun the end of the current line. If another match was found, it was
1034        incorrectly shown (and then shown again when found in the next line).
1035    
1036    7.  If pcregrep was compiled under Windows, there was a reference to the
1037        function pcregrep_exit() before it was defined. I am assuming this was
1038        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
1039        reported by a user. I've moved the definition above the reference.
1040    
1041    
1042    Version 8.11 10-Dec-2010
1043  ------------------------  ------------------------
1044    
1045  1.  (*THEN) was not working properly if there were untried alternatives prior  1.  (*THEN) was not working properly if there were untried alternatives prior
1046      to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it      to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
1047      backtracked to try for "b" instead of moving to the next alternative branch      backtracked to try for "b" instead of moving to the next alternative branch
1048      at the same level (in this case, to look for "c"). The Perl documentation      at the same level (in this case, to look for "c"). The Perl documentation
1049      is clear that when (*THEN) is backtracked onto, it goes to the "next      is clear that when (*THEN) is backtracked onto, it goes to the "next
1050      alternative in the innermost enclosing group".      alternative in the innermost enclosing group".
1051    
1052  2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern  2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
1053      such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should      such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
1054      result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and      result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
1055      (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides      (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
1056      (*THEN).      (*THEN).
1057    
1058  3.  If \s appeared in a character class, it removed the VT character from  3.  If \s appeared in a character class, it removed the VT character from
1059      the class, even if it had been included by some previous item, for example      the class, even if it had been included by some previous item, for example
1060      in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part      in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
1061      of \s, but is part of the POSIX "space" class.)      of \s, but is part of the POSIX "space" class.)
1062    
1063  4.  A partial match never returns an empty string (because you can always  4.  A partial match never returns an empty string (because you can always
1064      match an empty string at the end of the subject); however the checking for      match an empty string at the end of the subject); however the checking for
1065      an empty string was starting at the "start of match" point. This has been      an empty string was starting at the "start of match" point. This has been
# Line 31  Version 8.11 10-Oct-2010 Line 1069  Version 8.11 10-Oct-2010
1069      (previously it gave "no match").      (previously it gave "no match").
1070    
1071  5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching  5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
1072      of $, \z, \Z, \b, and \B. If the match point is at the end of the string,      of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
1073      previously a full match would be given. However, setting PCRE_PARTIAL_HARD      previously a full match would be given. However, setting PCRE_PARTIAL_HARD
1074      has an implication that the given string is incomplete (because a partial      has an implication that the given string is incomplete (because a partial
1075      match is preferred over a full match). For this reason, these items now      match is preferred over a full match). For this reason, these items now
1076      give a partial match in this situation. [Aside: previously, the one case      give a partial match in this situation. [Aside: previously, the one case
1077      /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial      /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
1078      match rather than a full match, which was wrong by the old rules, but is      match rather than a full match, which was wrong by the old rules, but is
1079      now correct.]      now correct.]
1080    
1081  6.  There was a bug in the handling of #-introduced comments, recognized when  6.  There was a bug in the handling of #-introduced comments, recognized when
1082      PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.      PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
1083      If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose      If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
1084      UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when      UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
1085      scanning for the end of the comment. (*Character* 0x85 is an "any" newline,      scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
1086      but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several      but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
1087      places in pcre_compile().      places in pcre_compile().
1088    
1089  7.  Related to (6) above, when pcre_compile() was skipping #-introduced  7.  Related to (6) above, when pcre_compile() was skipping #-introduced
1090      comments when looking ahead for named forward references to subpatterns,      comments when looking ahead for named forward references to subpatterns,
1091      the only newline sequence it recognized was NL. It now handles newlines      the only newline sequence it recognized was NL. It now handles newlines
1092      according to the set newline convention.      according to the set newline convention.
1093    
1094  8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the  8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
1095      former, but used strtoul(), whereas pcretest avoided strtoul() but did not      former, but used strtoul(), whereas pcretest avoided strtoul() but did not
1096      cater for a lack of strerror(). These oversights have been fixed.      cater for a lack of strerror(). These oversights have been fixed.
1097    
1098  9.  Added --match-limit and --recursion-limit to pcregrep.  9.  Added --match-limit and --recursion-limit to pcregrep.
1099    
1100  10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.  10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
1101    
1102  11. When the -o option was used, pcregrep was setting a return code of 1, even  11. When the -o option was used, pcregrep was setting a return code of 1, even
1103      when matches were found, and --line-buffered was not being honoured.      when matches were found, and --line-buffered was not being honoured.
1104    
1105    12. Added an optional parentheses number to the -o and --only-matching options
1106        of pcregrep.
1107    
1108    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
1109        can match an empty string. The code to do it in pcretest and pcredemo
1110        needed fixing:
1111    
1112        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
1113            only one byte after an empty string match just before CRLF (this case
1114            just got forgotten; "any" and "anycrlf" were OK).
1115    
1116        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
1117            mode when an empty string match preceded an ASCII character followed by
1118            a non-ASCII character. (The code for advancing by one character rather
1119            than one byte was nonsense.)
1120    
1121        (c) The pcredemo.c sample program did not have any code at all to handle
1122            the cases when CRLF is a valid newline sequence.
1123    
1124    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
1125        as a starting offset was within the subject string. There is now a new
1126        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
1127        negative or greater than the length of the string. In order to test this,
1128        pcretest is extended to allow the setting of negative starting offsets.
1129    
1130    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
1131        starting offset points to the beginning of a UTF-8 character was
1132        unnecessarily clumsy. I tidied it up.
1133    
1134    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
1135        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
1136    
1137    17. Nobody had reported that the --include_dir option, which was added in
1138        release 7.7 should have been called --include-dir (hyphen, not underscore)
1139        for compatibility with GNU grep. I have changed it to --include-dir, but
1140        left --include_dir as an undocumented synonym, and the same for
1141        --exclude-dir, though that is not available in GNU grep, at least as of
1142        release 2.5.4.
1143    
1144    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
1145        characters from a string of bytes) have been redefined so as not to use
1146        loops, in order to improve performance in some environments. At the same
1147        time, I abstracted some of the common code into auxiliary macros to save
1148        repetition (this should not affect the compiled code).
1149    
1150    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
1151        compile-time error is now given if \c is not followed by an ASCII
1152        character, that is, a byte less than 128. (In EBCDIC mode, the code is
1153        different, and any byte value is allowed.)
1154    
1155    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
1156        START_OPTIMIZE option, which is now allowed at compile time - but just
1157        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
1158        to pcregrep and other applications that have no direct access to PCRE
1159        options. The new /Y option in pcretest sets this option when calling
1160        pcre_compile().
1161    
1162    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
1163        back references. Groups containing recursive back references were forced to
1164        be atomic by that change, but in the case of named groups, the amount of
1165        memory required was incorrectly computed, leading to "Failed: internal
1166        error: code overflow". This has been fixed.
1167    
1168    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
1169        pcretest.c, to avoid build problems in some Borland environments.
1170    
1171    
1172  Version 8.10 25-Jun-2010  Version 8.10 25-Jun-2010
1173  ------------------------  ------------------------

Legend:
Removed from v.564  
changed lines
  Added in v.1322

  ViewVC Help
Powered by ViewVC 1.1.5