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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.574  
changed lines
  Added in v.1248

  ViewVC Help
Powered by ViewVC 1.1.5