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

Diff of /code/trunk/ChangeLog

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

revision 622 by ph10, Mon Jul 18 10:46:51 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.13 30-Apr-2011  Version 8.33 xx-xxxx-201x
5    -------------------------
6    
7    1.  Added 'U' to some constants that are compared to unsigned integers, to
8        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
9        variables that are added to signed variables, to ensure the result is
10        signed and can be negated.
11    
12    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
13        CMake config files.
14    
15    3.  Revise the creation of config.h.generic so that all boolean macros are
16        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
17        overriding via -D on the command line possible.
18    
19    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
20        to unsigned int is reported to make a quite noticeable speed difference in
21        a specific Windows environment. Testing on Linux did also appear to show
22        some benefit (and it is clearly not harmful). Also fixed the definition of
23        Xop which should be unsigned.
24    
25    5.  Related to (4), changing the definition of the intermediate variable cc
26        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
27        improvements.
28    
29    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
30        unnecessary spaces.
31    
32    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
33        and later.
34    
35    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
36    
37    9.  Optimizing fast_forward_start_bits in JIT.
38    
39    10. Adding experimental support for callouts in JIT, and fixing some
40        issues revealed during this work. Namely:
41    
42        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
43    
44        (b) Minimum length was not checked before the matching is started.
45    
46    11. The value of capture_last that is passed to callouts was incorrect in some
47        cases when there was a capture on one path that was subsequently abandoned
48        after a backtrack. Also, the capture_last value is now reset after a
49        recursion, since all captures are also reset in this case.
50    
51    12. The interpreter no longer returns the "too many substrings" error in the
52        case when an overflowing capture is in a branch that is subsequently
53        abandoned after a backtrack.
54    
55    13. In the pathological case when an offset vector of size 2 is used, pcretest
56        now prints out the matched string after a yield of 0 or 1.
57    
58    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
59        Only supported by the JIT compiler at the moment.
60    
61    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
62    
63    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
64        offset of the starting point of the matching process, provided the offsets
65        vector is large enough.
66    
67    17. The \A escape now records a lookbehind value of 1, though its execution
68        does not actually inspect the previous character. This is to ensure that,
69        in partial multi-segment matching, at least one character from the old
70        segment is retained when a new segment is processed. Otherwise, if there
71        are no lookbehinds in the pattern, \A might match incorrectly at the start
72        of a new segment.
73    
74    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
75    
76    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
77        gives some modest performance improvement in 8-bit mode.
78    
79    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
80        be expressed in certain programming languages using Universal Character
81        Names.
82    
83    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
84        which points out that "non characters" are not "characters that may not
85        appear in Unicode strings" but rather "characters that are reserved for
86        internal use and have only local meaning".
87    
88    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
89        there was a conditional group that depended on an assertion, if the
90        assertion was false, the callout that immediately followed the alternation
91        in the condition was skipped when pcre_exec() was used for matching.
92    
93    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.
501    
502    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
503        are added as well.
504    
505    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
506        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
507        calling _pcre_jit_exec. Some extra comments are added.
508    
509    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
511        was introduced by change 18 for 8.20.
512    
513    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
514        ECMA-262 standard.
515    
516    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.
518        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
521        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)
523        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
525        length instead of just assuming "not fixed length". The items that were
526        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
527        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
528        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
529    
530    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
531        being incorrectly compiled and would have given unpredicatble results.
532    
533    9.  A possessively repeated subpattern with minimum repeat count greater than
534        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
535        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
536        the first (A) could occur when it should not.
537    
538    10. Add a cast and remove a redundant test from the code.
539    
540    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
543        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
544        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.
547    
548    14. Perl does not support \N without a following name in a [] class; PCRE now
549        also gives an error.
550    
551    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
553        maximum number of forward references (including repeats) was limited by the
554        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
556        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
558        the filling in of repeated forward references.
559    
560    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.
562    
563    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
565        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
567        tested.
568    
569    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
571        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
573        "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
575        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
577        refactoring has had the pleasing side effect of removing one argument from
578        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,
581        subsequent uses of /S (without +) incorrectly behaved like /S+.
582    
583    21. Retrieve executable code size support for the JIT compiler and fixing
584        some warnings.
585    
586    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
588        subject string.
589    
590    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
591        systems.
592    
593    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.
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
614    ------------------------
615    
616    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
617        a POSIX class. After further experiments with Perl, which convinced me that
618        Perl has bugs and confusions, a closing square bracket is no longer allowed
619        in a POSIX name. This bug also affected patterns with classes that started
620        with full stops.
621    
622    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
623        captured substring, but while checking the failing first alternative,
624        substring 1 is temporarily captured. If the output vector supplied to
625        pcre_exec() was not big enough for this capture, the yield of the function
626        was still zero ("insufficient space for captured substrings"). This cannot
627        be totally fixed without adding another stack variable, which seems a lot
628        of expense for a edge case. However, I have improved the situation in cases
629        such as /(a)(b)x|abc/ matched against "abc", where the return code
630        indicates that fewer than the maximum number of slots in the ovector have
631        been set.
632    
633    3.  Related to (2) above: when there are more back references in a pattern than
634        slots in the output vector, pcre_exec() uses temporary memory during
635        matching, and copies in the captures as far as possible afterwards. It was
636        using the entire output vector, but this conflicts with the specification
637        that only 2/3 is used for passing back captured substrings. Now it uses
638        only the first 2/3, for compatibility. This is, of course, another edge
639        case.
640    
641    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
642        main code base, and can be used by building with --enable-jit. When this is
643        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
644        runtime --no-jit option is given.
645    
646    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
647        ovector, the return from the function was zero, implying that there were
648        other matches that did not fit. The correct "exactly full" value is now
649        returned.
650    
651    6.  If a subpattern that was called recursively or as a subroutine contained
652        (*PRUNE) or any other control that caused it to give a non-standard return,
653        invalid errors such as "Error -26 (nested recursion at the same subject
654        position)" or even infinite loops could occur.
655    
656    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
657        computing the minimum length on reaching *ACCEPT, and so ended up with the
658        wrong value of 1 rather than 0. Further investigation indicates that
659        computing a minimum subject length in the presence of *ACCEPT is difficult
660        (think back references, subroutine calls), and so I have changed the code
661        so that no minimum is registered for a pattern that contains *ACCEPT.
662    
663    8.  If (*THEN) was present in the first (true) branch of a conditional group,
664        it was not handled as intended. [But see 16 below.]
665    
666    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
667        Sheri Pierce.
668    
669    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
670        the first byte in a match must be "a".
671    
672    11. Change 17 for 8.13 increased the recursion depth for patterns like
673        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
674        pattern contains any instances of (*THEN). If it does not, the old
675        optimizations are restored. It would be nice to do this on a per-group
676        basis, but at the moment that is not feasible.
677    
678    12. In some environments, the output of pcretest -C is CRLF terminated. This
679        broke RunTest's code that checks for the link size. A single white space
680        character after the value is now allowed for.
681    
682    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
683        For "fr", it uses the Windows-specific input and output files.
684    
685    14. If (*THEN) appeared in a group that was called recursively or as a
686        subroutine, it did not work as intended. [But see next item.]
687    
688    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
689        pattern fragments (but not containing any | characters). If A and B are
690        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
691        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
692        D. In other words, Perl considers parentheses that do not contain any |
693        characters to be part of a surrounding alternative, whereas PCRE was
694        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
695        differently. PCRE now behaves in the same way as Perl, except in the case
696        of subroutine/recursion calls such as (?1) which have in any case always
697        been different (but PCRE had them first :-).
698    
699    16. Related to 15 above: Perl does not treat the | in a conditional group as
700        creating alternatives. Such a group is treated in the same way as an
701        ordinary group without any | characters when processing (*THEN). PCRE has
702        been changed to match Perl's behaviour.
703    
704    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
705        RunGrepTest script failed.
706    
707    18. Change 22 for version 13 caused atomic groups to use more stack. This is
708        inevitable for groups that contain captures, but it can lead to a lot of
709        stack use in large patterns. The old behaviour has been restored for atomic
710        groups that do not contain any capturing parentheses.
711    
712    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
713        suppress the check for a minimum subject length at run time. (If it was
714        given to pcre_exec() or pcre_dfa_exec() it did work.)
715    
716    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
717        fail to work when decoding hex characters in data strings in EBCDIC
718        environments.
719    
720    21. It appears that in at least one Mac OS environment, the isxdigit() function
721        is implemented as a macro that evaluates to its argument more than once,
722        contravening the C 90 Standard (I haven't checked a later standard). There
723        was an instance in pcretest which caused it to go wrong when processing
724        \x{...} escapes in subject strings. The has been rewritten to avoid using
725        things like p++ in the argument of isxdigit().
726    
727    
728    Version 8.13 16-Aug-2011
729  ------------------------  ------------------------
730    
731  1.  The Unicode data tables have been updated to Unicode 6.0.0.  1.  The Unicode data tables have been updated to Unicode 6.0.0.
# Line 20  Version 8.13 30-Apr-2011 Line 744  Version 8.13 30-Apr-2011
744      code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a      code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
745      2-byte code at the end of the subject (it thought there wasn't enough data      2-byte code at the end of the subject (it thought there wasn't enough data
746      left).      left).
747    
748  5.  Comprehensive information about what went wrong is now returned by  5.  Comprehensive information about what went wrong is now returned by
749      pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long      pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
750      as the output vector has at least 2 elements. The offset of the start of      as the output vector has at least 2 elements. The offset of the start of
751      the failing character and a reason code are placed in the vector.      the failing character and a reason code are placed in the vector.
752    
753  6.  When the UTF-8 string check fails for pcre_compile(), the offset that is  6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
754      now returned is for the first byte of the failing character, instead of the      now returned is for the first byte of the failing character, instead of the
755      last byte inspected. This is an incompatible change, but I hope it is small      last byte inspected. This is an incompatible change, but I hope it is small
756      enough not to be a problem. It makes the returned offset consistent with      enough not to be a problem. It makes the returned offset consistent with
757      pcre_exec() and pcre_dfa_exec().      pcre_exec() and pcre_dfa_exec().
758    
759  7.  pcretest now gives a text phrase as well as the error number when  7.  pcretest now gives a text phrase as well as the error number when
760      pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check      pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
761      failure, the offset and reason code are output.      failure, the offset and reason code are output.
762    
763  8.  When \R was used with a maximizing quantifier it failed to skip backwards  8.  When \R was used with a maximizing quantifier it failed to skip backwards
764      over a \r\n pair if the subsequent match failed. Instead, it just skipped      over a \r\n pair if the subsequent match failed. Instead, it just skipped
765      back over a single character (\n). This seems wrong (because it treated the      back over a single character (\n). This seems wrong (because it treated the
766      two characters as a single entity when going forwards), conflicts with the      two characters as a single entity when going forwards), conflicts with the
767      documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the      documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
768      behaviour of \R* different to (\R)*, which also seems wrong. The behaviour      behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
769      has been changed.      has been changed.
770    
771  9.  Some internal refactoring has changed the processing so that the handling  9.  Some internal refactoring has changed the processing so that the handling
772      of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile      of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
773      time (the PCRE_DOTALL option was changed this way some time ago: version      time (the PCRE_DOTALL option was changed this way some time ago: version
774      7.7 change 16). This has made it possible to abolish the OP_OPT op code,      7.7 change 16). This has made it possible to abolish the OP_OPT op code,
775      which was always a bit of a fudge. It also means that there is one less      which was always a bit of a fudge. It also means that there is one less
776      argument for the match() function, which reduces its stack requirements      argument for the match() function, which reduces its stack requirements
777      slightly. This change also fixes an incompatibility with Perl: the pattern      slightly. This change also fixes an incompatibility with Perl: the pattern
778      (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.      (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
779    
780  10. More internal refactoring has drastically reduced the number of recursive  10. More internal refactoring has drastically reduced the number of recursive
781      calls to match() for possessively repeated groups such as (abc)++ when      calls to match() for possessively repeated groups such as (abc)++ when
782      using pcre_exec().      using pcre_exec().
783    
784  11. While implementing 10, a number of bugs in the handling of groups were  11. While implementing 10, a number of bugs in the handling of groups were
785      discovered and fixed:      discovered and fixed:
786    
787      (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).      (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
788      (a|)*(?1) gave a compile-time internal error.      (a|)*(?1) gave a compile-time internal error.
789      ((a|)+)+  did not notice that the outer group could match an empty string.      ((a|)+)+  did not notice that the outer group could match an empty string.
790      (^a|^)+   was not marked as anchored.      (^a|^)+   was not marked as anchored.
791      (.*a|.*)+ was not marked as matching at start or after a newline.      (.*a|.*)+ was not marked as matching at start or after a newline.
792    
793  12. Yet more internal refactoring has removed another argument from the match()  12. Yet more internal refactoring has removed another argument from the match()
794      function. Special calls to this function are now indicated by setting a      function. Special calls to this function are now indicated by setting a
795      value in a variable in the "match data" data block.      value in a variable in the "match data" data block.
796    
797  13. Be more explicit in pcre_study() instead of relying on "default" for  13. Be more explicit in pcre_study() instead of relying on "default" for
798      opcodes that mean there is no starting character; this means that when new      opcodes that mean there is no starting character; this means that when new
799      ones are added and accidentally left out of pcre_study(), testing should      ones are added and accidentally left out of pcre_study(), testing should
800      pick them up.      pick them up.
801    
802  14. The -s option of pcretest has been documented for ages as being an old  14. The -s option of pcretest has been documented for ages as being an old
803      synonym of -m (show memory usage). I have changed it to mean "force study      synonym of -m (show memory usage). I have changed it to mean "force study
804      for every regex", that is, assume /S for every regex. This is similar to -i      for every regex", that is, assume /S for every regex. This is similar to -i
805      and -d etc. It's slightly incompatible, but I'm hoping nobody is still      and -d etc. It's slightly incompatible, but I'm hoping nobody is still
806      using it. It makes it easier to run collections of tests with and without      using it. It makes it easier to run collections of tests with and without
807      study enabled, and thereby test pcre_study() more easily. All the standard      study enabled, and thereby test pcre_study() more easily. All the standard
808      tests are now run with and without -s (but some patterns can be marked as      tests are now run with and without -s (but some patterns can be marked as
809      "never study" - see 20 below).      "never study" - see 20 below).
810    
811  15. When (*ACCEPT) was used in a subpattern that was called recursively, the  15. When (*ACCEPT) was used in a subpattern that was called recursively, the
812      restoration of the capturing data to the outer values was not happening      restoration of the capturing data to the outer values was not happening
813      correctly.      correctly.
814    
815  16. If a recursively called subpattern ended with (*ACCEPT) and matched an  16. If a recursively called subpattern ended with (*ACCEPT) and matched an
816      empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole      empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
817      pattern had matched an empty string, and so incorrectly returned a no      pattern had matched an empty string, and so incorrectly returned a no
818      match.      match.
819    
820  17. There was optimizing code for the last branch of non-capturing parentheses,  17. There was optimizing code for the last branch of non-capturing parentheses,
821      and also for the obeyed branch of a conditional subexpression, which used      and also for the obeyed branch of a conditional subexpression, which used
822      tail recursion to cut down on stack usage. Unfortunately, not that there is      tail recursion to cut down on stack usage. Unfortunately, now that there is
823      the possibility of (*THEN) occurring in these branches, tail recursion is      the possibility of (*THEN) occurring in these branches, tail recursion is
824      no longer possible because the return has to be checked for (*THEN). These      no longer possible because the return has to be checked for (*THEN). These
825      two optimizations have therefore been removed.      two optimizations have therefore been removed. [But see 8.20/11 above.]
826    
827  18. If a pattern containing \R was studied, it was assumed that \R always  18. If a pattern containing \R was studied, it was assumed that \R always
828      matched two bytes, thus causing the minimum subject length to be      matched two bytes, thus causing the minimum subject length to be
829      incorrectly computed because \R can also match just one byte.      incorrectly computed because \R can also match just one byte.
830    
831  19. If a pattern containing (*ACCEPT) was studied, the minimum subject length  19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
832      was incorrectly computed.      was incorrectly computed.
833    
834  20. If /S is present twice on a test pattern in pcretest input, it *disables*  20. If /S is present twice on a test pattern in pcretest input, it now
835      studying, thereby overriding the use of -s on the command line. This is      *disables* studying, thereby overriding the use of -s on the command line
836      necessary for one or two tests to keep the output identical in both cases.      (see 14 above). This is necessary for one or two tests to keep the output
837        identical in both cases.
838    
839  21. When (*ACCEPT) was used in an assertion that matched an empty string and  21. When (*ACCEPT) was used in an assertion that matched an empty string and
840      PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.      PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
841    
842  22. When an atomic group that contained a capturing parenthesis was  22. When an atomic group that contained a capturing parenthesis was
843      successfully matched, but the branch in which it appeared failed, the      successfully matched, but the branch in which it appeared failed, the
844      capturing was not being forgotten if a higher numbered group was later      capturing was not being forgotten if a higher numbered group was later
845      captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing      captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
846      group 1 to "a", when in fact it should be unset. This applied to multi-      group 1 to "a", when in fact it should be unset. This applied to multi-
847      branched capturing and non-capturing groups, repeated or not, and also to      branched capturing and non-capturing groups, repeated or not, and also to
848      positive assertions (capturing in negative assertions is not well defined      positive assertions (capturing in negative assertions does not happen
849      in PCRE) and also to nested atomic groups.      in PCRE) and also to nested atomic groups.
850    
851  23. Add the ++ qualifier feature to pcretest, to show the remainder of the  23. Add the ++ qualifier feature to pcretest, to show the remainder of the
852      subject after a captured substring (to make it easier to tell which of a      subject after a captured substring, to make it easier to tell which of a
853      number of identical substrings has been captured).      number of identical substrings has been captured.
854    
855  24. The way atomic groups are processed by pcre_exec() has been changed so that  24. The way atomic groups are processed by pcre_exec() has been changed so that
856      if they are repeated, backtracking one repetition now resets captured      if they are repeated, backtracking one repetition now resets captured
857      values correctly. For example, if ((?>(a+)b)+aabab) is matched against      values correctly. For example, if ((?>(a+)b)+aabab) is matched against
858      "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as      "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
859      "aaa". Previously, it would have been "a". As part of this code      "aaa". Previously, it would have been "a". As part of this code
860      refactoring, the way recursive calls are handled has also been changed.      refactoring, the way recursive calls are handled has also been changed.
861    
862  24. If an assertion condition captured any substrings, they were not passed  25. If an assertion condition captured any substrings, they were not passed
863      back unless some other capturing happened later. For example, if      back unless some other capturing happened later. For example, if
864      (?(?=(a))a) was matched against "a", no capturing was returned.      (?(?=(a))a) was matched against "a", no capturing was returned.
865    
866  25. When studying a pattern that contained subroutine calls or assertions,  26. When studying a pattern that contained subroutine calls or assertions,
867      the code for finding the minimum length of a possible match was handling      the code for finding the minimum length of a possible match was handling
868      direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where      direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
869      group 1 called group 2 while simultaneously a separate group 2 called group      group 1 called group 2 while simultaneously a separate group 2 called group
870      1). A stack overflow occurred in this case. I have fixed this by limiting      1). A stack overflow occurred in this case. I have fixed this by limiting
871      the recursion depth to 10.      the recursion depth to 10.
872    
873  26. Updated RunTest.bat in the distribution to the version supplied by Tom  27. Updated RunTest.bat in the distribution to the version supplied by Tom
874      Fortmann. This supports explicit test numbers on the command line, and has      Fortmann. This supports explicit test numbers on the command line, and has
875      argument validation and error reporting.      argument validation and error reporting.
876    
877    28. An instance of \X with an unlimited repeat could fail if at any point the
878        first character it looked at was a mark character.
879    
880    29. Some minor code refactoring concerning Unicode properties and scripts
881        should reduce the stack requirement of match() slightly.
882    
883    30. Added the '=' option to pcretest to check the setting of unused capturing
884        slots at the end of the pattern, which are documented as being -1, but are
885        not included in the return count.
886    
887    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
888        compiled something random. Now it gives a compile-time error (as does
889        Perl).
890    
891    32. A *MARK encountered during the processing of a positive assertion is now
892        recorded and passed back (compatible with Perl).
893    
894    33. If --only-matching or --colour was set on a pcregrep call whose pattern
895        had alternative anchored branches, the search for a second match in a line
896        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
897        matched the line "0102" twice. The same bug affected patterns that started
898        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
899        twice.
900    
901    34. Previously, PCRE did not allow quantification of assertions. However, Perl
902        does, and because of capturing effects, quantifying parenthesized
903        assertions may at times be useful. Quantifiers are now allowed for
904        parenthesized assertions.
905    
906    35. A minor code tidy in pcre_compile() when checking options for \R usage.
907    
908    36. \g was being checked for fancy things in a character class, when it should
909        just be a literal "g".
910    
911    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
912        appearance of a nested POSIX class supersedes an apparent external class.
913        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
914        unescaped square brackets may also appear as part of class names. For
915        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
916        more like Perl. (But see 8.20/1 above.)
917    
918    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
919        was because it thought it was \N{name}, which is not supported).
920    
921    39. Add minix to OS list not supporting the -S option in pcretest.
922    
923    40. PCRE tries to detect cases of infinite recursion at compile time, but it
924        cannot analyze patterns in sufficient detail to catch mutual recursions
925        such as ((?1))((?2)). There is now a runtime test that gives an error if a
926        subgroup is called recursively as a subpattern for a second time at the
927        same position in the subject string. In previous releases this might have
928        been caught by the recursion limit, or it might have run out of stack.
929    
930    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
931        happen only once. PCRE was, however incorrectly giving a compile time error
932        "recursive call could loop indefinitely" because it cannot analyze the
933        pattern in sufficient detail. The compile time test no longer happens when
934        PCRE is compiling a conditional subpattern, but actual runaway loops are
935        now caught at runtime (see 40 above).
936    
937    42. It seems that Perl allows any characters other than a closing parenthesis
938        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
939        has been changed to be the same.
940    
941    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
942        as not to get warnings when autogen.sh is called. Also changed
943        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
944    
945    44. To help people who use pcregrep to scan files containing exceedingly long
946        lines, the following changes have been made:
947    
948        (a) The default value of the buffer size parameter has been increased from
949            8K to 20K. (The actual buffer used is three times this size.)
950    
951        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
952            PCRE is built.
953    
954        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
955            to be set at run time.
956    
957        (d) Numerical values in pcregrep options can be followed by K or M, for
958            example --buffer-size=50K.
959    
960        (e) If a line being scanned overflows pcregrep's buffer, an error is now
961            given and the return code is set to 2.
962    
963    45. Add a pointer to the latest mark to the callout data block.
964    
965    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
966        partial match of an empty string instead of no match. This was specific to
967        the use of ".".
968    
969    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
970        complete match instead of a partial match. This bug was dependent on both
971        the PCRE_UTF8 and PCRE_DOTALL options being set.
972    
973    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
974        starting byte set, because \b was not being ignored.
975    
976    
977  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011

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

  ViewVC Help
Powered by ViewVC 1.1.5