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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.608  
changed lines
  Added in v.1345

  ViewVC Help
Powered by ViewVC 1.1.5