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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.505  
changed lines
  Added in v.1245

  ViewVC Help
Powered by ViewVC 1.1.5