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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.539  
changed lines
  Added in v.1271

  ViewVC Help
Powered by ViewVC 1.1.5