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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.605  
changed lines
  Added in v.1346

  ViewVC Help
Powered by ViewVC 1.1.5