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

Diff of /code/trunk/ChangeLog

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

revision 207 by ph10, Mon Aug 6 09:32:14 2007 UTC revision 1346 by ph10, Tue Jul 2 18:37:36 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 05-Jul-07  Version 8.34 xx-xxxx-201x
5    --------------------------
6    
7    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
8        executable memory. Patch inspired by Carsten Klein.
9    
10    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
11        this macro is never tested and has no effect, because the work to support
12        coverage involves only compiling and linking options and special targets in
13        the Makefile. The comment in config.h implied that defining the macro would
14        enable coverage support, which is totally false. There was also support for
15        setting this macro in the CMake files (my fault, I just copied it from
16        configure). SUPPORT_GCOV has now been removed.
17    
18    3.  Make a small performance improvement in strlen16() and strlen32() in
19        pcretest.
20    
21    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
22        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
23        these cases). There was also one in pcretest.c.
24    
25    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
26    
27    
28    Version 8.33 28-May-2013
29    --------------------------
30    
31    1.  Added 'U' to some constants that are compared to unsigned integers, to
32        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
33        variables that are added to signed variables, to ensure the result is
34        signed and can be negated.
35    
36    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
37        CMake config files.
38    
39    3.  Revise the creation of config.h.generic so that all boolean macros are
40        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
41        overriding via -D on the command line possible.
42    
43    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
44        to unsigned int is reported to make a quite noticeable speed difference in
45        a specific Windows environment. Testing on Linux did also appear to show
46        some benefit (and it is clearly not harmful). Also fixed the definition of
47        Xop which should be unsigned.
48    
49    5.  Related to (4), changing the definition of the intermediate variable cc
50        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
51        improvements.
52    
53    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
54        unnecessary spaces.
55    
56    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
57        and later.
58    
59    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
60    
61    9.  Optimizing fast_forward_start_bits in JIT.
62    
63    10. Adding support for callouts in JIT, and fixing some issues revealed
64        during this work. Namely:
65    
66        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
67    
68        (b) Minimum length was not checked before the matching is started.
69    
70    11. The value of capture_last that is passed to callouts was incorrect in some
71        cases when there was a capture on one path that was subsequently abandoned
72        after a backtrack. Also, the capture_last value is now reset after a
73        recursion, since all captures are also reset in this case.
74    
75    12. The interpreter no longer returns the "too many substrings" error in the
76        case when an overflowing capture is in a branch that is subsequently
77        abandoned after a backtrack.
78    
79    13. In the pathological case when an offset vector of size 2 is used, pcretest
80        now prints out the matched string after a yield of 0 or 1.
81    
82    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
83        Only supported by the JIT compiler at the moment.
84    
85    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
86    
87    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
88        offset of the starting point of the matching process, provided the offsets
89        vector is large enough.
90    
91    17. The \A escape now records a lookbehind value of 1, though its execution
92        does not actually inspect the previous character. This is to ensure that,
93        in partial multi-segment matching, at least one character from the old
94        segment is retained when a new segment is processed. Otherwise, if there
95        are no lookbehinds in the pattern, \A might match incorrectly at the start
96        of a new segment.
97    
98    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
99    
100    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
101        gives some modest performance improvement in 8-bit mode.
102    
103    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
104        be expressed in certain programming languages using Universal Character
105        Names.
106    
107    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
108        which points out that "non characters" are not "characters that may not
109        appear in Unicode strings" but rather "characters that are reserved for
110        internal use and have only local meaning".
111    
112    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
113        there was a conditional group that depended on an assertion, if the
114        assertion was false, the callout that immediately followed the alternation
115        in the condition was skipped when pcre_exec() was used for matching.
116    
117    23. Allow an explicit callout to be inserted before an assertion that is the
118        condition for a conditional group, for compatibility with automatic
119        callouts, which always insert a callout at this point.
120    
121    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
122        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
123    
124    25. (*PRUNE) is now supported by the JIT compiler.
125    
126    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
127    
128    27. Fix the case where there are two or more SKIPs with arguments that may be
129        ignored.
130    
131    28. (*SKIP) is now supported by the JIT compiler.
132    
133    29. (*THEN) is now supported by the JIT compiler.
134    
135    30. Update RunTest with additional test selector options.
136    
137    31. The way PCRE handles backtracking verbs has been changed in two ways.
138    
139        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
140        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
141        backtracking. In some cases this makes it more Perl-compatible, but Perl's
142        rather obscure rules do not always do the same thing.
143    
144        (2) Previously, backtracking verbs were confined within assertions. This is
145        no longer the case for positive assertions, except for (*ACCEPT). Again,
146        this sometimes improves Perl compatibility, and sometimes does not.
147    
148    32. A number of tests that were in test 2 because Perl did things differently
149        have been moved to test 1, because either Perl or PCRE has changed, and
150        these tests are now compatible.
151    
152    32. Backtracking control verbs are now handled in the same way in JIT and
153        interpreter.
154    
155    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
156        contained a forward subroutine reference caused a compile error.
157    
158    34. Auto-detect and optimize limited repetitions in JIT.
159    
160    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
161        blocking (*UTF) etc.
162    
163    36. In the interpreter, maximizing pattern repetitions for characters and
164        character types now use tail recursion, which reduces stack usage.
165    
166    37. The value of the max lookbehind was not correctly preserved if a compiled
167        and saved regex was reloaded on a host of different endianness.
168    
169    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
170        of the compiled pattern block, expand the flags field from 16 to 32 bits
171        because it was almost full.
172    
173    39. Try madvise first before posix_madvise.
174    
175    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
176        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
177        original change locked out all matches of empty strings. This has been
178        changed so that one match of an empty string per line is recognized.
179        Subsequent searches on the same line (for colouring or for --only-matching,
180        for example) do not recognize empty strings.
181    
182    41. Applied a user patch to fix a number of spelling mistakes in comments.
183    
184    42. Data lines longer than 65536 caused pcretest to crash.
185    
186    43. Clarified the data type for length and startoffset arguments for pcre_exec
187        and pcre_dfa_exec in the function-specific man pages, where they were
188        explicitly stated to be in bytes, never having been updated. I also added
189        some clarification to the pcreapi man page.
190    
191    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
192        a segmentation fault.
193    
194    
195    Version 8.32 30-November-2012
196    -----------------------------
197    
198    1.  Improved JIT compiler optimizations for first character search and single
199        character iterators.
200    
201    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
202        Patch by Daniel Richard G.
203    
204    3.  Single character iterator optimizations in the JIT compiler.
205    
206    4.  Improved JIT compiler optimizations for character ranges.
207    
208    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
209        Reported by Giuseppe D'Angelo.
210    
211    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
212        of a line, was being set incorrectly in cases where .* appeared inside
213        atomic brackets at the start of a pattern, or where there was a subsequent
214        *PRUNE or *SKIP.
215    
216    7.  Improved instruction cache flush for POWER/PowerPC.
217        Patch by Daniel Richard G.
218    
219    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
220        grep:
221    
222        (a) There is now no limit to the number of patterns to be matched.
223    
224        (b) An error is given if a pattern is too long.
225    
226        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
227            are now supported.
228    
229        (d) --exclude-from and --include-from (multiple use) have been added.
230    
231        (e) Exclusions and inclusions now apply to all files and directories, not
232            just to those obtained from scanning a directory recursively.
233    
234        (f) Multiple uses of -f and --file-list are now supported.
235    
236        (g) In a Windows environment, the default for -d has been changed from
237            "read" (the GNU grep default) to "skip", because otherwise the presence
238            of a directory in the file list provokes an error.
239    
240        (h) The documentation has been revised and clarified in places.
241    
242    9.  Improve the matching speed of capturing brackets.
243    
244    10. Changed the meaning of \X so that it now matches a Unicode extended
245        grapheme cluster.
246    
247    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
248        out POSIX threads when JIT support is configured.
249    
250    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
251    
252    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
253        structure could go wrong in environments where size_t is not the same size
254        as int.
255    
256    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
257        set.
258    
259    15. The EBCDIC support had decayed; later updates to the code had included
260        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
261        general tidy up of EBCDIC-related issues, and the documentation was also
262        not quite right. There is now a test that can be run on ASCII systems to
263        check some of the EBCDIC-related things (but is it not a full test).
264    
265    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
266        in a small tidy to the code.
267    
268    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
269    
270    18. If the --only-matching (-o) option in pcregrep is specified multiple
271        times, each one causes appropriate output. For example, -o1 -o2 outputs the
272        substrings matched by the 1st and 2nd capturing parentheses. A separating
273        string can be specified by --om-separator (default empty).
274    
275    19. Improving the first n character searches.
276    
277    20. Turn case lists for horizontal and vertical white space into macros so that
278        they are defined only once.
279    
280    21. This set of changes together give more compatible Unicode case-folding
281        behaviour for characters that have more than one other case when UCP
282        support is available.
283    
284        (a) The Unicode property table now has offsets into a new table of sets of
285            three or more characters that are case-equivalent. The MultiStage2.py
286            script that generates these tables (the pcre_ucd.c file) now scans
287            CaseFolding.txt instead of UnicodeData.txt for character case
288            information.
289    
290        (b) The code for adding characters or ranges of characters to a character
291            class has been abstracted into a generalized function that also handles
292            case-independence. In UTF-mode with UCP support, this uses the new data
293            to handle characters with more than one other case.
294    
295        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
296            whose other case is greater than 256 are now correctly matched
297            caselessly. Previously, the high codepoint matched the low one, but not
298            vice versa.
299    
300        (d) The processing of \h, \H, \v, and \ in character classes now makes use
301            of the new class addition function, using character lists defined as
302            macros alongside the case definitions of 20 above.
303    
304        (e) Caseless back references now work with characters that have more than
305            one other case.
306    
307        (f) General caseless matching of characters with more than one other case
308            is supported.
309    
310    22. Unicode character properties were updated from Unicode 6.2.0
311    
312    23. Improved CMake support under Windows. Patch by Daniel Richard G.
313    
314    24. Add support for 32-bit character strings, and UTF-32
315    
316    25. Major JIT compiler update (code refactoring and bugfixing).
317        Experimental Sparc 32 support is added.
318    
319    26. Applied a modified version of Daniel Richard G's patch to create
320        pcre.h.generic and config.h.generic by "make" instead of in the
321        PrepareRelease script.
322    
323    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
324        pcre_compile.c when checking for a zero character.
325    
326    28. Introducing a native interface for JIT. Through this interface, the compiled
327        machine code can be directly executed. The purpose of this interface is to
328        provide fast pattern matching, so several sanity checks are not performed.
329        However, feature tests are still performed. The new interface provides
330        1.4x speedup compared to the old one.
331    
332    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
333        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
334        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
335    
336    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
337        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
338        the "old" RFC 2279). Instead, it ended up passing a negative length to
339        pcre_exec().
340    
341    31. Add support for GCC's visibility feature to hide internal functions.
342    
343    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
344        "unknown -C option" after outputting 0 or 1.
345    
346    33. There is now support for generating a code coverage report for the test
347        suite in environments where gcc is the compiler and lcov is installed. This
348        is mainly for the benefit of the developers.
349    
350    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
351        unaddressable using valgrind annotations, allowing valgrind to detect
352        invalid memory accesses. This is mainly for the benefit of the developers.
353    
354    25. (*UTF) can now be used to start a pattern in any of the three libraries.
355    
356    26. Give configure error if --enable-cpp but no C++ compiler found.
357    
358    
359    Version 8.31 06-July-2012
360    -------------------------
361    
362    1.  Fixing a wrong JIT test case and some compiler warnings.
363    
364    2.  Removed a bashism from the RunTest script.
365    
366    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
367        to unsigned type, result still unsigned" that was given by an MS compiler
368        on encountering the code "-sizeof(xxx)".
369    
370    4.  Partial matching support is added to the JIT compiler.
371    
372    5.  Fixed several bugs concerned with partial matching of items that consist
373        of more than one character:
374    
375        (a) /^(..)\1/ did not partially match "aba" because checking references was
376            done on an "all or nothing" basis. This also applied to repeated
377            references.
378    
379        (b) \R did not give a hard partial match if \r was found at the end of the
380            subject.
381    
382        (c) \X did not give a hard partial match after matching one or more
383            characters at the end of the subject.
384    
385        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
386            a partial match for the string "\r".
387    
388        (e) When newline was set to CRLF, the metacharacter "." did not recognize
389            a partial match for a CR character at the end of the subject string.
390    
391    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
392        running pcretest, the text "(JIT)" added to the output whenever JIT is
393        actually used to run the match.
394    
395    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
396        or /S+[+] with a digit between 1 and 7.
397    
398    8.  OP_NOT now supports any UTF character not just single-byte ones.
399    
400    9.  (*MARK) control verb is now supported by the JIT compiler.
401    
402    10. The command "./RunTest list" lists the available tests without actually
403        running any of them. (Because I keep forgetting what they all are.)
404    
405    11. Add PCRE_INFO_MAXLOOKBEHIND.
406    
407    12. Applied a (slightly modified) user-supplied patch that improves performance
408        when the heap is used for recursion (compiled with --disable-stack-for-
409        recursion). Instead of malloc and free for each heap frame each time a
410        logical recursion happens, frames are retained on a chain and re-used where
411        possible. This sometimes gives as much as 30% improvement.
412    
413    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
414        call.
415    
416    14. As documented, (*COMMIT) is now confined to within a positive assertion.
417    
418    15. It is now possible to link pcretest with libedit as an alternative to
419        libreadline.
420    
421    16. (*COMMIT) control verb is now supported by the JIT compiler.
422    
423    17. The Unicode data tables have been updated to Unicode 6.1.0.
424    
425    18. Added --file-list option to pcregrep.
426    
427    19. Added binary file support to pcregrep, including the -a, --binary-files,
428        -I, and --text options.
429    
430    20. The madvise function is renamed for posix_madvise for QNX compatibility
431        reasons. Fixed by Giuseppe D'Angelo.
432    
433    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
434    
435    22. Changed the option for creating symbolic links for 16-bit man pages from
436        -s to -sf so that re-installing does not cause issues.
437    
438    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
439    
440    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
441        matches in certain environments (the workspace was not being correctly
442        retained). Also added to pcre_dfa_exec() a simple plausibility check on
443        some of the workspace data at the beginning of a restart.
444    
445    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
446        was not doing so when it should - probably a typo introduced by SVN 528
447        (change 8.10/14).
448    
449    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
450        \w+ when the character tables indicated that \x{c4} was a word character.
451        There were several related cases, all because the tests for doing a table
452        lookup were testing for characters less than 127 instead of 255.
453    
454    27. If a pattern contains capturing parentheses that are not used in a match,
455        their slots in the ovector are set to -1. For those that are higher than
456        any matched groups, this happens at the end of processing. In the case when
457        there were back references that the ovector was too small to contain
458        (causing temporary malloc'd memory to be used during matching), and the
459        highest capturing number was not used, memory off the end of the ovector
460        was incorrectly being set to -1. (It was using the size of the temporary
461        memory instead of the true size.)
462    
463    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
464        ovector size, it uses memory at the end of the block that it has got.
465    
466    29. Check for an overlong MARK name and give an error at compile time. The
467        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
468    
469    30. JIT compiler update.
470    
471    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
472        Rill for the patch.
473    
474    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
475    
476    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
477    
478    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
479        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
480        was enabled.
481    
482    35. Improve JIT code generation for greedy plus quantifier.
483    
484    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
485        1 to "aa" instead of to an empty string. The bug affected repeated groups
486        that could potentially match an empty string.
487    
488    37. Optimizing single character iterators in JIT.
489    
490    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
491        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
492        codepoints that are too big for the mode are faulted, and in a UTF mode,
493        disallowed codepoints are also faulted.
494    
495    39. If PCRE was compiled with UTF support, in three places in the DFA
496        matcher there was code that should only have been obeyed in UTF mode, but
497        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
498        processing when bytes with values greater than 127 were present. In 16-bit
499        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
500        both cases the values are those that cannot be the first data item in a UTF
501        character. The three items that might have provoked this were recursions,
502        possessively repeated groups, and atomic groups.
503    
504    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
505        and pcregrep, because some OS require shared objects to be explicitly
506        passed to ld, causing the link step to fail if they are not.
507    
508    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
509        mode, patterns that started with \h* or \R* might be incorrectly matched.
510    
511    
512    Version 8.30 04-February-2012
513    -----------------------------
514    
515    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
516        name is defined in ctype.h.
517    
518    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
519        only in quite long subpatterns.
520    
521    3.  Removed the function pcre_info(), which has been obsolete and deprecated
522        since it was replaced by pcre_fullinfo() in February 2000.
523    
524    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
525        match a (*MARK), and the match failed at the start of the subject, a
526        reference to memory before the start of the subject could occur. This bug
527        was introduced by fix 17 of release 8.21.
528    
529    5.  A reference to an unset group with zero minimum repetition was giving
530        totally wrong answers (in non-JavaScript-compatibility mode). For example,
531        /(another)?(\1?)test/ matched against "hello world test". This bug was
532        introduced in release 8.13.
533    
534    6.  Add support for 16-bit character strings (a large amount of work involving
535        many changes and refactorings).
536    
537    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
538        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
539        from a file.
540    
541    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
542        rounding is not applied in this particular case).
543    
544    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
545        if they appear, or are escaped, in patterns.
546    
547    10. Get rid of a number of -Wunused-but-set-variable warnings.
548    
549    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
550        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
551        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
552        also returns the mark "x". This bug applied to capturing parentheses,
553        non-capturing parentheses, and atomic parentheses. It also applied to some
554        assertions.
555    
556    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
557        information out of configure.ac instead of relying on pcre.h.generic, which
558        is not stored in the repository.
559    
560    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
561        -lreadline.
562    
563    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
564    
565    15. Applied Graycode's patch to put the top-level frame on the stack rather
566        than the heap when not using the stack for recursion. This gives a
567        performance improvement in many cases when recursion is not deep.
568    
569    16. Experimental code added to "pcretest -C" to output the stack frame size.
570    
571    
572    Version 8.21 12-Dec-2011
573    ------------------------
574    
575    1.  Updating the JIT compiler.
576    
577    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
578        are added as well.
579    
580    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
581        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
582        calling _pcre_jit_exec. Some extra comments are added.
583    
584    4.  (*MARK) settings inside atomic groups that do not contain any capturing
585        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
586        was introduced by change 18 for 8.20.
587    
588    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
589        ECMA-262 standard.
590    
591    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
592        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
593        This bug was probably introduced by change 9 of 8.13.
594    
595    7.  While fixing 6 above, I noticed that a number of other items were being
596        incorrectly rejected as "not fixed length". This arose partly because newer
597        opcodes had not been added to the fixed-length checking code. I have (a)
598        corrected the bug and added tests for these items, and (b) arranged for an
599        error to occur if an unknown opcode is encountered while checking for fixed
600        length instead of just assuming "not fixed length". The items that were
601        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
602        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
603        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
604    
605    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
606        being incorrectly compiled and would have given unpredicatble results.
607    
608    9.  A possessively repeated subpattern with minimum repeat count greater than
609        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
610        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
611        the first (A) could occur when it should not.
612    
613    10. Add a cast and remove a redundant test from the code.
614    
615    11. JIT should use pcre_malloc/pcre_free for allocation.
616    
617    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
618        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
619        is anything other than /usr, -L is still shown).
620    
621    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
622    
623    14. Perl does not support \N without a following name in a [] class; PCRE now
624        also gives an error.
625    
626    15. If a forward reference was repeated with an upper limit of around 2000,
627        it caused the error "internal error: overran compiling workspace". The
628        maximum number of forward references (including repeats) was limited by the
629        internal workspace, and dependent on the LINK_SIZE. The code has been
630        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
631        the default depends on LINK_SIZE. There is a new upper limit (for safety)
632        of around 200,000 forward references. While doing this, I also speeded up
633        the filling in of repeated forward references.
634    
635    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
636        incorrectly expecting the subject to contain another "a" after the start.
637    
638    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
639        in the match, the SKIP should be ignored. This was not happening; instead
640        the SKIP was being treated as NOMATCH. For patterns such as
641        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
642        tested.
643    
644    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
645        now much more compatible with Perl, in particular in cases where the result
646        is a non-match for a non-anchored pattern. For example, if
647        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
648        "m", where previously it did not return a name. A side effect of this
649        change is that for partial matches, the last encountered mark name is
650        returned, as for non matches. A number of tests that were previously not
651        Perl-compatible have been moved into the Perl-compatible test files. The
652        refactoring has had the pleasing side effect of removing one argument from
653        the match() function, thus reducing its stack requirements.
654    
655    19. If the /S+ option was used in pcretest to study a pattern using JIT,
656        subsequent uses of /S (without +) incorrectly behaved like /S+.
657    
658    21. Retrieve executable code size support for the JIT compiler and fixing
659        some warnings.
660    
661    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
662        not work when the shorter character appeared right at the end of the
663        subject string.
664    
665    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
666        systems.
667    
668    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
669        output it when the /M option is used in pcretest.
670    
671    25. The CheckMan script was not being included in the distribution. Also, added
672        an explicit "perl" to run Perl scripts from the PrepareRelease script
673        because this is reportedly needed in Windows.
674    
675    26. If study data was being save in a file and studying had not found a set of
676        "starts with" bytes for the pattern, the data written to the file (though
677        never used) was taken from uninitialized memory and so caused valgrind to
678        complain.
679    
680    27. Updated RunTest.bat as provided by Sheri Pierce.
681    
682    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
683    
684    29. Computation of memory usage for the table of capturing group names was
685        giving an unnecessarily large value.
686    
687    
688    Version 8.20 21-Oct-2011
689    ------------------------
690    
691    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
692        a POSIX class. After further experiments with Perl, which convinced me that
693        Perl has bugs and confusions, a closing square bracket is no longer allowed
694        in a POSIX name. This bug also affected patterns with classes that started
695        with full stops.
696    
697    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
698        captured substring, but while checking the failing first alternative,
699        substring 1 is temporarily captured. If the output vector supplied to
700        pcre_exec() was not big enough for this capture, the yield of the function
701        was still zero ("insufficient space for captured substrings"). This cannot
702        be totally fixed without adding another stack variable, which seems a lot
703        of expense for a edge case. However, I have improved the situation in cases
704        such as /(a)(b)x|abc/ matched against "abc", where the return code
705        indicates that fewer than the maximum number of slots in the ovector have
706        been set.
707    
708    3.  Related to (2) above: when there are more back references in a pattern than
709        slots in the output vector, pcre_exec() uses temporary memory during
710        matching, and copies in the captures as far as possible afterwards. It was
711        using the entire output vector, but this conflicts with the specification
712        that only 2/3 is used for passing back captured substrings. Now it uses
713        only the first 2/3, for compatibility. This is, of course, another edge
714        case.
715    
716    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
717        main code base, and can be used by building with --enable-jit. When this is
718        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
719        runtime --no-jit option is given.
720    
721    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
722        ovector, the return from the function was zero, implying that there were
723        other matches that did not fit. The correct "exactly full" value is now
724        returned.
725    
726    6.  If a subpattern that was called recursively or as a subroutine contained
727        (*PRUNE) or any other control that caused it to give a non-standard return,
728        invalid errors such as "Error -26 (nested recursion at the same subject
729        position)" or even infinite loops could occur.
730    
731    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
732        computing the minimum length on reaching *ACCEPT, and so ended up with the
733        wrong value of 1 rather than 0. Further investigation indicates that
734        computing a minimum subject length in the presence of *ACCEPT is difficult
735        (think back references, subroutine calls), and so I have changed the code
736        so that no minimum is registered for a pattern that contains *ACCEPT.
737    
738    8.  If (*THEN) was present in the first (true) branch of a conditional group,
739        it was not handled as intended. [But see 16 below.]
740    
741    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
742        Sheri Pierce.
743    
744    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
745        the first byte in a match must be "a".
746    
747    11. Change 17 for 8.13 increased the recursion depth for patterns like
748        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
749        pattern contains any instances of (*THEN). If it does not, the old
750        optimizations are restored. It would be nice to do this on a per-group
751        basis, but at the moment that is not feasible.
752    
753    12. In some environments, the output of pcretest -C is CRLF terminated. This
754        broke RunTest's code that checks for the link size. A single white space
755        character after the value is now allowed for.
756    
757    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
758        For "fr", it uses the Windows-specific input and output files.
759    
760    14. If (*THEN) appeared in a group that was called recursively or as a
761        subroutine, it did not work as intended. [But see next item.]
762    
763    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
764        pattern fragments (but not containing any | characters). If A and B are
765        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
766        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
767        D. In other words, Perl considers parentheses that do not contain any |
768        characters to be part of a surrounding alternative, whereas PCRE was
769        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
770        differently. PCRE now behaves in the same way as Perl, except in the case
771        of subroutine/recursion calls such as (?1) which have in any case always
772        been different (but PCRE had them first :-).
773    
774    16. Related to 15 above: Perl does not treat the | in a conditional group as
775        creating alternatives. Such a group is treated in the same way as an
776        ordinary group without any | characters when processing (*THEN). PCRE has
777        been changed to match Perl's behaviour.
778    
779    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
780        RunGrepTest script failed.
781    
782    18. Change 22 for version 13 caused atomic groups to use more stack. This is
783        inevitable for groups that contain captures, but it can lead to a lot of
784        stack use in large patterns. The old behaviour has been restored for atomic
785        groups that do not contain any capturing parentheses.
786    
787    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
788        suppress the check for a minimum subject length at run time. (If it was
789        given to pcre_exec() or pcre_dfa_exec() it did work.)
790    
791    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
792        fail to work when decoding hex characters in data strings in EBCDIC
793        environments.
794    
795    21. It appears that in at least one Mac OS environment, the isxdigit() function
796        is implemented as a macro that evaluates to its argument more than once,
797        contravening the C 90 Standard (I haven't checked a later standard). There
798        was an instance in pcretest which caused it to go wrong when processing
799        \x{...} escapes in subject strings. The has been rewritten to avoid using
800        things like p++ in the argument of isxdigit().
801    
802    
803    Version 8.13 16-Aug-2011
804    ------------------------
805    
806    1.  The Unicode data tables have been updated to Unicode 6.0.0.
807    
808    2.  Two minor typos in pcre_internal.h have been fixed.
809    
810    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
811        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
812        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
813    
814    4.  There were a number of related bugs in the code for matching backrefences
815        caselessly in UTF-8 mode when codes for the characters concerned were
816        different numbers of bytes. For example, U+023A and U+2C65 are an upper
817        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
818        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
819        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
820        2-byte code at the end of the subject (it thought there wasn't enough data
821        left).
822    
823    5.  Comprehensive information about what went wrong is now returned by
824        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
825        as the output vector has at least 2 elements. The offset of the start of
826        the failing character and a reason code are placed in the vector.
827    
828    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
829        now returned is for the first byte of the failing character, instead of the
830        last byte inspected. This is an incompatible change, but I hope it is small
831        enough not to be a problem. It makes the returned offset consistent with
832        pcre_exec() and pcre_dfa_exec().
833    
834    7.  pcretest now gives a text phrase as well as the error number when
835        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
836        failure, the offset and reason code are output.
837    
838    8.  When \R was used with a maximizing quantifier it failed to skip backwards
839        over a \r\n pair if the subsequent match failed. Instead, it just skipped
840        back over a single character (\n). This seems wrong (because it treated the
841        two characters as a single entity when going forwards), conflicts with the
842        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
843        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
844        has been changed.
845    
846    9.  Some internal refactoring has changed the processing so that the handling
847        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
848        time (the PCRE_DOTALL option was changed this way some time ago: version
849        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
850        which was always a bit of a fudge. It also means that there is one less
851        argument for the match() function, which reduces its stack requirements
852        slightly. This change also fixes an incompatibility with Perl: the pattern
853        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
854    
855    10. More internal refactoring has drastically reduced the number of recursive
856        calls to match() for possessively repeated groups such as (abc)++ when
857        using pcre_exec().
858    
859    11. While implementing 10, a number of bugs in the handling of groups were
860        discovered and fixed:
861    
862        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
863        (a|)*(?1) gave a compile-time internal error.
864        ((a|)+)+  did not notice that the outer group could match an empty string.
865        (^a|^)+   was not marked as anchored.
866        (.*a|.*)+ was not marked as matching at start or after a newline.
867    
868    12. Yet more internal refactoring has removed another argument from the match()
869        function. Special calls to this function are now indicated by setting a
870        value in a variable in the "match data" data block.
871    
872    13. Be more explicit in pcre_study() instead of relying on "default" for
873        opcodes that mean there is no starting character; this means that when new
874        ones are added and accidentally left out of pcre_study(), testing should
875        pick them up.
876    
877    14. The -s option of pcretest has been documented for ages as being an old
878        synonym of -m (show memory usage). I have changed it to mean "force study
879        for every regex", that is, assume /S for every regex. This is similar to -i
880        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
881        using it. It makes it easier to run collections of tests with and without
882        study enabled, and thereby test pcre_study() more easily. All the standard
883        tests are now run with and without -s (but some patterns can be marked as
884        "never study" - see 20 below).
885    
886    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
887        restoration of the capturing data to the outer values was not happening
888        correctly.
889    
890    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
891        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
892        pattern had matched an empty string, and so incorrectly returned a no
893        match.
894    
895    17. There was optimizing code for the last branch of non-capturing parentheses,
896        and also for the obeyed branch of a conditional subexpression, which used
897        tail recursion to cut down on stack usage. Unfortunately, now that there is
898        the possibility of (*THEN) occurring in these branches, tail recursion is
899        no longer possible because the return has to be checked for (*THEN). These
900        two optimizations have therefore been removed. [But see 8.20/11 above.]
901    
902    18. If a pattern containing \R was studied, it was assumed that \R always
903        matched two bytes, thus causing the minimum subject length to be
904        incorrectly computed because \R can also match just one byte.
905    
906    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
907        was incorrectly computed.
908    
909    20. If /S is present twice on a test pattern in pcretest input, it now
910        *disables* studying, thereby overriding the use of -s on the command line
911        (see 14 above). This is necessary for one or two tests to keep the output
912        identical in both cases.
913    
914    21. When (*ACCEPT) was used in an assertion that matched an empty string and
915        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
916    
917    22. When an atomic group that contained a capturing parenthesis was
918        successfully matched, but the branch in which it appeared failed, the
919        capturing was not being forgotten if a higher numbered group was later
920        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
921        group 1 to "a", when in fact it should be unset. This applied to multi-
922        branched capturing and non-capturing groups, repeated or not, and also to
923        positive assertions (capturing in negative assertions does not happen
924        in PCRE) and also to nested atomic groups.
925    
926    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
927        subject after a captured substring, to make it easier to tell which of a
928        number of identical substrings has been captured.
929    
930    24. The way atomic groups are processed by pcre_exec() has been changed so that
931        if they are repeated, backtracking one repetition now resets captured
932        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
933        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
934        "aaa". Previously, it would have been "a". As part of this code
935        refactoring, the way recursive calls are handled has also been changed.
936    
937    25. If an assertion condition captured any substrings, they were not passed
938        back unless some other capturing happened later. For example, if
939        (?(?=(a))a) was matched against "a", no capturing was returned.
940    
941    26. When studying a pattern that contained subroutine calls or assertions,
942        the code for finding the minimum length of a possible match was handling
943        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
944        group 1 called group 2 while simultaneously a separate group 2 called group
945        1). A stack overflow occurred in this case. I have fixed this by limiting
946        the recursion depth to 10.
947    
948    27. Updated RunTest.bat in the distribution to the version supplied by Tom
949        Fortmann. This supports explicit test numbers on the command line, and has
950        argument validation and error reporting.
951    
952    28. An instance of \X with an unlimited repeat could fail if at any point the
953        first character it looked at was a mark character.
954    
955    29. Some minor code refactoring concerning Unicode properties and scripts
956        should reduce the stack requirement of match() slightly.
957    
958    30. Added the '=' option to pcretest to check the setting of unused capturing
959        slots at the end of the pattern, which are documented as being -1, but are
960        not included in the return count.
961    
962    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
963        compiled something random. Now it gives a compile-time error (as does
964        Perl).
965    
966    32. A *MARK encountered during the processing of a positive assertion is now
967        recorded and passed back (compatible with Perl).
968    
969    33. If --only-matching or --colour was set on a pcregrep call whose pattern
970        had alternative anchored branches, the search for a second match in a line
971        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
972        matched the line "0102" twice. The same bug affected patterns that started
973        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
974        twice.
975    
976    34. Previously, PCRE did not allow quantification of assertions. However, Perl
977        does, and because of capturing effects, quantifying parenthesized
978        assertions may at times be useful. Quantifiers are now allowed for
979        parenthesized assertions.
980    
981    35. A minor code tidy in pcre_compile() when checking options for \R usage.
982    
983    36. \g was being checked for fancy things in a character class, when it should
984        just be a literal "g".
985    
986    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
987        appearance of a nested POSIX class supersedes an apparent external class.
988        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
989        unescaped square brackets may also appear as part of class names. For
990        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
991        more like Perl. (But see 8.20/1 above.)
992    
993    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
994        was because it thought it was \N{name}, which is not supported).
995    
996    39. Add minix to OS list not supporting the -S option in pcretest.
997    
998    40. PCRE tries to detect cases of infinite recursion at compile time, but it
999        cannot analyze patterns in sufficient detail to catch mutual recursions
1000        such as ((?1))((?2)). There is now a runtime test that gives an error if a
1001        subgroup is called recursively as a subpattern for a second time at the
1002        same position in the subject string. In previous releases this might have
1003        been caught by the recursion limit, or it might have run out of stack.
1004    
1005    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
1006        happen only once. PCRE was, however incorrectly giving a compile time error
1007        "recursive call could loop indefinitely" because it cannot analyze the
1008        pattern in sufficient detail. The compile time test no longer happens when
1009        PCRE is compiling a conditional subpattern, but actual runaway loops are
1010        now caught at runtime (see 40 above).
1011    
1012    42. It seems that Perl allows any characters other than a closing parenthesis
1013        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
1014        has been changed to be the same.
1015    
1016    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
1017        as not to get warnings when autogen.sh is called. Also changed
1018        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
1019    
1020    44. To help people who use pcregrep to scan files containing exceedingly long
1021        lines, the following changes have been made:
1022    
1023        (a) The default value of the buffer size parameter has been increased from
1024            8K to 20K. (The actual buffer used is three times this size.)
1025    
1026        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
1027            PCRE is built.
1028    
1029        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
1030            to be set at run time.
1031    
1032        (d) Numerical values in pcregrep options can be followed by K or M, for
1033            example --buffer-size=50K.
1034    
1035        (e) If a line being scanned overflows pcregrep's buffer, an error is now
1036            given and the return code is set to 2.
1037    
1038    45. Add a pointer to the latest mark to the callout data block.
1039    
1040    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
1041        partial match of an empty string instead of no match. This was specific to
1042        the use of ".".
1043    
1044    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
1045        complete match instead of a partial match. This bug was dependent on both
1046        the PCRE_UTF8 and PCRE_DOTALL options being set.
1047    
1048    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
1049        starting byte set, because \b was not being ignored.
1050    
1051    
1052    Version 8.12 15-Jan-2011
1053    ------------------------
1054    
1055    1.  Fixed some typos in the markup of the man pages, and wrote a script that
1056        checks for such things as part of the documentation building process.
1057    
1058    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
1059        --match-limit and --recursion-limit options (added for 8.11). In
1060        particular, this made one of the standard tests fail. (The integer value
1061        went into the wrong half of a long int.)
1062    
1063    3.  If the --colour option was given to pcregrep with -v (invert match), it
1064        did strange things, either producing crazy output, or crashing. It should,
1065        of course, ignore a request for colour when reporting lines that do not
1066        match.
1067    
1068    4.  Another pcregrep bug caused similar problems if --colour was specified with
1069        -M (multiline) and the pattern match finished with a line ending.
1070    
1071    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
1072        matched in multiline mode, the following line was shown as part of the
1073        match. This seems wrong, so I have changed it.
1074    
1075    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
1076        the check for further matches in the same line (so they could be coloured)
1077        to overrun the end of the current line. If another match was found, it was
1078        incorrectly shown (and then shown again when found in the next line).
1079    
1080    7.  If pcregrep was compiled under Windows, there was a reference to the
1081        function pcregrep_exit() before it was defined. I am assuming this was
1082        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
1083        reported by a user. I've moved the definition above the reference.
1084    
1085    
1086    Version 8.11 10-Dec-2010
1087    ------------------------
1088    
1089    1.  (*THEN) was not working properly if there were untried alternatives prior
1090        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
1091        backtracked to try for "b" instead of moving to the next alternative branch
1092        at the same level (in this case, to look for "c"). The Perl documentation
1093        is clear that when (*THEN) is backtracked onto, it goes to the "next
1094        alternative in the innermost enclosing group".
1095    
1096    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
1097        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
1098        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
1099        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
1100        (*THEN).
1101    
1102    3.  If \s appeared in a character class, it removed the VT character from
1103        the class, even if it had been included by some previous item, for example
1104        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
1105        of \s, but is part of the POSIX "space" class.)
1106    
1107    4.  A partial match never returns an empty string (because you can always
1108        match an empty string at the end of the subject); however the checking for
1109        an empty string was starting at the "start of match" point. This has been
1110        changed to the "earliest inspected character" point, because the returned
1111        data for a partial match starts at this character. This means that, for
1112        example, /(?<=abc)def/ gives a partial match for the subject "abc"
1113        (previously it gave "no match").
1114    
1115    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
1116        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
1117        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
1118        has an implication that the given string is incomplete (because a partial
1119        match is preferred over a full match). For this reason, these items now
1120        give a partial match in this situation. [Aside: previously, the one case
1121        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
1122        match rather than a full match, which was wrong by the old rules, but is
1123        now correct.]
1124    
1125    6.  There was a bug in the handling of #-introduced comments, recognized when
1126        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
1127        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
1128        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
1129        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
1130        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
1131        places in pcre_compile().
1132    
1133    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
1134        comments when looking ahead for named forward references to subpatterns,
1135        the only newline sequence it recognized was NL. It now handles newlines
1136        according to the set newline convention.
1137    
1138    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
1139        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
1140        cater for a lack of strerror(). These oversights have been fixed.
1141    
1142    9.  Added --match-limit and --recursion-limit to pcregrep.
1143    
1144    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
1145    
1146    11. When the -o option was used, pcregrep was setting a return code of 1, even
1147        when matches were found, and --line-buffered was not being honoured.
1148    
1149    12. Added an optional parentheses number to the -o and --only-matching options
1150        of pcregrep.
1151    
1152    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
1153        can match an empty string. The code to do it in pcretest and pcredemo
1154        needed fixing:
1155    
1156        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
1157            only one byte after an empty string match just before CRLF (this case
1158            just got forgotten; "any" and "anycrlf" were OK).
1159    
1160        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
1161            mode when an empty string match preceded an ASCII character followed by
1162            a non-ASCII character. (The code for advancing by one character rather
1163            than one byte was nonsense.)
1164    
1165        (c) The pcredemo.c sample program did not have any code at all to handle
1166            the cases when CRLF is a valid newline sequence.
1167    
1168    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
1169        as a starting offset was within the subject string. There is now a new
1170        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
1171        negative or greater than the length of the string. In order to test this,
1172        pcretest is extended to allow the setting of negative starting offsets.
1173    
1174    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
1175        starting offset points to the beginning of a UTF-8 character was
1176        unnecessarily clumsy. I tidied it up.
1177    
1178    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
1179        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
1180    
1181    17. Nobody had reported that the --include_dir option, which was added in
1182        release 7.7 should have been called --include-dir (hyphen, not underscore)
1183        for compatibility with GNU grep. I have changed it to --include-dir, but
1184        left --include_dir as an undocumented synonym, and the same for
1185        --exclude-dir, though that is not available in GNU grep, at least as of
1186        release 2.5.4.
1187    
1188    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
1189        characters from a string of bytes) have been redefined so as not to use
1190        loops, in order to improve performance in some environments. At the same
1191        time, I abstracted some of the common code into auxiliary macros to save
1192        repetition (this should not affect the compiled code).
1193    
1194    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
1195        compile-time error is now given if \c is not followed by an ASCII
1196        character, that is, a byte less than 128. (In EBCDIC mode, the code is
1197        different, and any byte value is allowed.)
1198    
1199    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
1200        START_OPTIMIZE option, which is now allowed at compile time - but just
1201        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
1202        to pcregrep and other applications that have no direct access to PCRE
1203        options. The new /Y option in pcretest sets this option when calling
1204        pcre_compile().
1205    
1206    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
1207        back references. Groups containing recursive back references were forced to
1208        be atomic by that change, but in the case of named groups, the amount of
1209        memory required was incorrectly computed, leading to "Failed: internal
1210        error: code overflow". This has been fixed.
1211    
1212    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
1213        pcretest.c, to avoid build problems in some Borland environments.
1214    
1215    
1216    Version 8.10 25-Jun-2010
1217    ------------------------
1218    
1219    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
1220        THEN.
1221    
1222    2.  (*ACCEPT) was not working when inside an atomic group.
1223    
1224    3.  Inside a character class, \B is treated as a literal by default, but
1225        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
1226        causes the error). The code is unchanged, but I tidied the documentation.
1227    
1228    4.  Inside a character class, PCRE always treated \R and \X as literals,
1229        whereas Perl faults them if its -w option is set. I have changed PCRE so
1230        that it faults them when PCRE_EXTRA is set.
1231    
1232    5.  Added support for \N, which always matches any character other than
1233        newline. (It is the same as "." when PCRE_DOTALL is not set.)
1234    
1235    6.  When compiling pcregrep with newer versions of gcc which may have
1236        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
1237        declared with attribute warn_unused_result" were given. Just casting the
1238        result to (void) does not stop the warnings; a more elaborate fudge is
1239        needed. I've used a macro to implement this.
1240    
1241    7.  Minor change to pcretest.c to avoid a compiler warning.
1242    
1243    8.  Added four artifical Unicode properties to help with an option to make
1244        \s etc use properties (see next item). The new properties are: Xan
1245        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
1246    
1247    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
1248        use Unicode properties. (*UCP) at the start of a pattern can be used to set
1249        this option. Modified pcretest to add /W to test this facility. Added
1250        REG_UCP to make it available via the POSIX interface.
1251    
1252    10. Added --line-buffered to pcregrep.
1253    
1254    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
1255        studied, and the match started with a letter with a code point greater than
1256        127 whose first byte was different to the first byte of the other case of
1257        the letter, the other case of this starting letter was not recognized
1258        (#976).
1259    
1260    12. If a pattern that was studied started with a repeated Unicode property
1261        test, for example, \p{Nd}+, there was the theoretical possibility of
1262        setting up an incorrect bitmap of starting bytes, but fortunately it could
1263        not have actually happened in practice until change 8 above was made (it
1264        added property types that matched character-matching opcodes).
1265    
1266    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
1267        possible starting bytes for non-anchored patterns.
1268    
1269    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
1270        \R, and also a number of cases that involve Unicode properties, both
1271        explicit and implicit when PCRE_UCP is set.
1272    
1273    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
1274        input, it could crash or give wrong results if characters with values
1275        greater than 0xc0 were present in the subject string. (Detail: it assumed
1276        UTF-8 input when processing these items.)
1277    
1278    16. Added a lot of (int) casts to avoid compiler warnings in systems where
1279        size_t is 64-bit (#991).
1280    
1281    17. Added a check for running out of memory when PCRE is compiled with
1282        --disable-stack-for-recursion (#990).
1283    
1284    18. If the last data line in a file for pcretest does not have a newline on
1285        the end, a newline was missing in the output.
1286    
1287    19. The default pcre_chartables.c file recognizes only ASCII characters (values
1288        less than 128) in its various bitmaps. However, there is a facility for
1289        generating tables according to the current locale when PCRE is compiled. It
1290        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
1291        characters, are recognized by isspace() and therefore were getting set in
1292        these tables, and indeed these tables seem to approximate to ISO 8859. This
1293        caused a problem in UTF-8 mode when pcre_study() was used to create a list
1294        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
1295        which of course cannot start UTF-8 characters. I have changed the code so
1296        that only real ASCII characters (less than 128) and the correct starting
1297        bytes for UTF-8 encodings are set for characters greater than 127 when in
1298        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
1299        altogether.)
1300    
1301    20. Added the /T option to pcretest so as to be able to run tests with non-
1302        standard character tables, thus making it possible to include the tests
1303        used for 19 above in the standard set of tests.
1304    
1305    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
1306        reference to a subpattern the other side of a comment that contains an
1307        opening parenthesis caused either an internal compiling error, or a
1308        reference to the wrong subpattern.
1309    
1310    
1311    Version 8.02 19-Mar-2010
1312    ------------------------
1313    
1314    1.  The Unicode data tables have been updated to Unicode 5.2.0.
1315    
1316    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
1317        configured.
1318    
1319    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
1320        original author of that file, following a query about its status.
1321    
1322    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
1323        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
1324    
1325    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
1326        quantifier applied to a forward-referencing subroutine call, could compile
1327        incorrect code or give the error "internal error: previously-checked
1328        referenced subpattern not found".
1329    
1330    6.  Both MS Visual Studio and Symbian OS have problems with initializing
1331        variables to point to external functions. For these systems, therefore,
1332        pcre_malloc etc. are now initialized to local functions that call the
1333        relevant global functions.
1334    
1335    7.  There were two entries missing in the vectors called coptable and poptable
1336        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
1337        I've fixed the data, and added a kludgy way of testing at compile time that
1338        the lengths are correct (equal to the number of opcodes).
1339    
1340    8.  Following on from 7, I added a similar kludge to check the length of the
1341        eint vector in pcreposix.c.
1342    
1343    9.  Error texts for pcre_compile() are held as one long string to avoid too
1344        much relocation at load time. To find a text, the string is searched,
1345        counting zeros. There was no check for running off the end of the string,
1346        which could happen if a new error number was added without updating the
1347        string.
1348    
1349    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
1350    
1351    11. \K was not working if it appeared in an atomic group or in a group that
1352        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
1353        \K is "not well defined" if used in an assertion. PCRE now accepts it if
1354        the assertion is positive, but not if it is negative.
1355    
1356    12. Change 11 fortuitously reduced the size of the stack frame used in the
1357        "match()" function of pcre_exec.c by one pointer. Forthcoming
1358        implementation of support for (*MARK) will need an extra pointer on the
1359        stack; I have reserved it now, so that the stack frame size does not
1360        decrease.
1361    
1362    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
1363        item in branch that calls a recursion is a subroutine call - as in the
1364        second branch in the above example - was incorrectly given the compile-
1365        time error "recursive call could loop indefinitely" because pcre_compile()
1366        was not correctly checking the subroutine for matching a non-empty string.
1367    
1368    14. The checks for overrunning compiling workspace could trigger after an
1369        overrun had occurred. This is a "should never occur" error, but it can be
1370        triggered by pathological patterns such as hundreds of nested parentheses.
1371        The checks now trigger 100 bytes before the end of the workspace.
1372    
1373    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
1374    
1375    
1376    Version 8.01 19-Jan-2010
1377    ------------------------
1378    
1379    1.  If a pattern contained a conditional subpattern with only one branch (in
1380        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
1381        computed the wrong minimum data length (which is of course zero for such
1382        subpatterns). This could cause incorrect "no match" results.
1383    
1384    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
1385        the pattern is reset in the first branch, pcre_compile() failed with
1386        "internal error: code overflow at offset...". This happened only when
1387        the reset was to the original external option setting. (An optimization
1388        abstracts leading options settings into an external setting, which was the
1389        cause of this.)
1390    
1391    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
1392        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
1393        assertion pattern did not match (meaning that the assertion was true), it
1394        was incorrectly treated as false if the SKIP had been reached during the
1395        matching. This also applied to assertions used as conditions.
1396    
1397    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
1398        assertion subpattern, including such a pattern used as a condition,
1399        unpredictable results occurred, instead of the error return
1400        PCRE_ERROR_DFA_UITEM.
1401    
1402    5.  The C++ GlobalReplace function was not working like Perl for the special
1403        situation when an empty string is matched. It now does the fancy magic
1404        stuff that is necessary.
1405    
1406    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
1407        removed. (These were left over from very, very early versions of PCRE.)
1408    
1409    7.  Some cosmetic changes to the code to make life easier when compiling it
1410        as part of something else:
1411    
1412        (a) Change DEBUG to PCRE_DEBUG.
1413    
1414        (b) In pcre_compile(), rename the member of the "branch_chain" structure
1415            called "current" as "current_branch", to prevent a collision with the
1416            Linux macro when compiled as a kernel module.
1417    
1418        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
1419            prevent a collision with the Linux macro when compiled as a kernel
1420            module.
1421    
1422    8.  In pcre_compile() there are some checks for integer overflows that used to
1423        cast potentially large values to (double). This has been changed to that
1424        when building, a check for int64_t is made, and if it is found, it is used
1425        instead, thus avoiding the use of floating point arithmetic. (There is no
1426        other use of FP in PCRE.) If int64_t is not found, the fallback is to
1427        double.
1428    
1429    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
1430        2005 (difference between two addresses compared to an unsigned value).
1431    
1432    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
1433        custom one, because of the following reported problem in Windows:
1434    
1435          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
1436              under Win32.
1437          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
1438              therefore missing the function definition.
1439          - The compiler thus generates a "C" signature for the test function.
1440          - The linker fails to find the "C" function.
1441          - PCRE fails to configure if asked to do so against libbz2.
1442    
1443    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
1444        messages were output:
1445    
1446          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
1447          rerunning libtoolize, to keep the correct libtool macros in-tree.
1448          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
1449    
1450        I have done both of these things.
1451    
1452    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
1453        most of the time, it *can* run out if it is given a pattern that contains a
1454        runaway infinite recursion. I updated the discussion in the pcrestack man
1455        page.
1456    
1457    13. Now that we have gone to the x.xx style of version numbers, the minor
1458        version may start with zero. Using 08 or 09 is a bad idea because users
1459        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
1460        interpreted as invalid octal numbers. I've updated the previous comment in
1461        configure.ac, and also added a check that gives an error if 08 or 09 are
1462        used.
1463    
1464    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
1465        causing partial matching to fail when the end of the subject matched \W
1466        in a UTF-8 pattern where \W was quantified with a minimum of 3.
1467    
1468    15. There were some discrepancies between the declarations in pcre_internal.h
1469        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
1470        their definitions. The declarations used "const uschar *" and the
1471        definitions used USPTR. Even though USPTR is normally defined as "const
1472        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
1473        reported that: "This difference in casting confuses some C++ compilers, for
1474        example, SunCC recognizes above declarations as different functions and
1475        generates broken code for hbpcre." I have changed the declarations to use
1476        USPTR.
1477    
1478    16. GNU libtool is named differently on some systems. The autogen.sh script now
1479        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
1480        (FreeBSD).
1481    
1482    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
1483        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
1484        comment: "Figure out how to create a longlong from a string: strtoll and
1485        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
1486        instance, but it only takes 2 args instead of 3!"
1487    
1488    18. A subtle bug concerned with back references has been fixed by a change of
1489        specification, with a corresponding code fix. A pattern such as
1490        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
1491        refers, was giving matches when it shouldn't. For example, xa=xaaa would
1492        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
1493        same bug. Such groups have to be quantified to be useful, or contained
1494        inside another quantified group. (If there's no repetition, the reference
1495        can never match.) The problem arises because, having left the group and
1496        moved on to the rest of the pattern, a later failure that backtracks into
1497        the group uses the captured value from the final iteration of the group
1498        rather than the correct earlier one. I have fixed this in PCRE by forcing
1499        any group that contains a reference to itself to be an atomic group; that
1500        is, there cannot be any backtracking into it once it has completed. This is
1501        similar to recursive and subroutine calls.
1502    
1503    
1504    Version 8.00 19-Oct-09
1505    ----------------------
1506    
1507    1.  The table for translating pcre_compile() error codes into POSIX error codes
1508        was out-of-date, and there was no check on the pcre_compile() error code
1509        being within the table. This could lead to an OK return being given in
1510        error.
1511    
1512    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
1513        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
1514        in a Windows environment.
1515    
1516    3.  The pcregrep --count option prints the count for each file even when it is
1517        zero, as does GNU grep. However, pcregrep was also printing all files when
1518        --files-with-matches was added. Now, when both options are given, it prints
1519        counts only for those files that have at least one match. (GNU grep just
1520        prints the file name in this circumstance, but including the count seems
1521        more useful - otherwise, why use --count?) Also ensured that the
1522        combination -clh just lists non-zero counts, with no names.
1523    
1524    4.  The long form of the pcregrep -F option was incorrectly implemented as
1525        --fixed_strings instead of --fixed-strings. This is an incompatible change,
1526        but it seems right to fix it, and I didn't think it was worth preserving
1527        the old behaviour.
1528    
1529    5.  The command line items --regex=pattern and --regexp=pattern were not
1530        recognized by pcregrep, which required --regex pattern or --regexp pattern
1531        (with a space rather than an '='). The man page documented the '=' forms,
1532        which are compatible with GNU grep; these now work.
1533    
1534    6.  No libpcreposix.pc file was created for pkg-config; there was just
1535        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
1536    
1537    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
1538        when UCP support is not needed, by modifying the Python script that
1539        generates it from Unicode data files. This should not matter if the module
1540        is correctly used as a library, but I received one complaint about 50K of
1541        unwanted data. My guess is that the person linked everything into his
1542        program rather than using a library. Anyway, it does no harm.
1543    
1544    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
1545        was a minimum greater than 1 for a wide character in a possessive
1546        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
1547        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
1548        character. Chaos in the form of incorrect output or a compiling loop could
1549        result.
1550    
1551    9.  The restrictions on what a pattern can contain when partial matching is
1552        requested for pcre_exec() have been removed. All patterns can now be
1553        partially matched by this function. In addition, if there are at least two
1554        slots in the offset vector, the offset of the earliest inspected character
1555        for the match and the offset of the end of the subject are set in them when
1556        PCRE_ERROR_PARTIAL is returned.
1557    
1558    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
1559        synonymous with PCRE_PARTIAL, for backwards compatibility, and
1560        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
1561        and may be more useful for multi-segment matching.
1562    
1563    11. Partial matching with pcre_exec() is now more intuitive. A partial match
1564        used to be given if ever the end of the subject was reached; now it is
1565        given only if matching could not proceed because another character was
1566        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
1567        string "Z", which now yields "no match" instead of "partial match". In the
1568        case of pcre_dfa_exec(), "no match" is given if every matching path for the
1569        final character ended with (*FAIL).
1570    
1571    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
1572        if the pattern had a "must contain" character that was already found in the
1573        earlier partial match, unless partial matching was again requested. For
1574        example, with the pattern /dog.(body)?/, the "must contain" character is
1575        "g". If the first part-match was for the string "dog", restarting with
1576        "sbody" failed. This bug has been fixed.
1577    
1578    13. The string returned by pcre_dfa_exec() after a partial match has been
1579        changed so that it starts at the first inspected character rather than the
1580        first character of the match. This makes a difference only if the pattern
1581        starts with a lookbehind assertion or \b or \B (\K is not supported by
1582        pcre_dfa_exec()). It's an incompatible change, but it makes the two
1583        matching functions compatible, and I think it's the right thing to do.
1584    
1585    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
1586        so that the demonstration program is easily available in environments where
1587        PCRE has not been installed from source.
1588    
1589    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
1590        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
1591        library.
1592    
1593    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
1594        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
1595        is not the first non-POSIX option to be added. Clearly some people find
1596        these options useful.
1597    
1598    17. If a caller to the POSIX matching function regexec() passes a non-zero
1599        value for nmatch with a NULL value for pmatch, the value of
1600        nmatch is forced to zero.
1601    
1602    18. RunGrepTest did not have a test for the availability of the -u option of
1603        the diff command, as RunTest does. It now checks in the same way as
1604        RunTest, and also checks for the -b option.
1605    
1606    19. If an odd number of negated classes containing just a single character
1607        interposed, within parentheses, between a forward reference to a named
1608        subpattern and the definition of the subpattern, compilation crashed with
1609        an internal error, complaining that it could not find the referenced
1610        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
1611        [The bug was that it was starting one character too far in when skipping
1612        over the character class, thus treating the ] as data rather than
1613        terminating the class. This meant it could skip too much.]
1614    
1615    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
1616        /g option in pcretest when the pattern contains \K, which makes it possible
1617        to have an empty string match not at the start, even when the pattern is
1618        anchored. Updated pcretest and pcredemo to use this option.
1619    
1620    21. If the maximum number of capturing subpatterns in a recursion was greater
1621        than the maximum at the outer level, the higher number was returned, but
1622        with unset values at the outer level. The correct (outer level) value is
1623        now given.
1624    
1625    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
1626        PCRE did not set those parentheses (unlike Perl). I have now found a way to
1627        make it do so. The string so far is captured, making this feature
1628        compatible with Perl.
1629    
1630    23. The tests have been re-organized, adding tests 11 and 12, to make it
1631        possible to check the Perl 5.10 features against Perl 5.10.
1632    
1633    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
1634        pattern matches a fixed length string. PCRE did not allow this; now it
1635        does. Neither allows recursion.
1636    
1637    25. I finally figured out how to implement a request to provide the minimum
1638        length of subject string that was needed in order to match a given pattern.
1639        (It was back references and recursion that I had previously got hung up
1640        on.) This code has now been added to pcre_study(); it finds a lower bound
1641        to the length of subject needed. It is not necessarily the greatest lower
1642        bound, but using it to avoid searching strings that are too short does give
1643        some useful speed-ups. The value is available to calling programs via
1644        pcre_fullinfo().
1645    
1646    26. While implementing 25, I discovered to my embarrassment that pcretest had
1647        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
1648        study optimizations had never been tested with that matching function.
1649        Oops. What is worse, even when it was passed study data, there was a bug in
1650        pcre_dfa_exec() that meant it never actually used it. Double oops. There
1651        were also very few tests of studied patterns with pcre_dfa_exec().
1652    
1653    27. If (?| is used to create subpatterns with duplicate numbers, they are now
1654        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
1655        on the other side of the coin, they are no longer allowed to have different
1656        names, because these cannot be distinguished in PCRE, and this has caused
1657        confusion. (This is a difference from Perl.)
1658    
1659    28. When duplicate subpattern names are present (necessarily with different
1660        numbers, as required by 27 above), and a test is made by name in a
1661        conditional pattern, either for a subpattern having been matched, or for
1662        recursion in such a pattern, all the associated numbered subpatterns are
1663        tested, and the overall condition is true if the condition is true for any
1664        one of them. This is the way Perl works, and is also more like the way
1665        testing by number works.
1666    
1667    
1668    Version 7.9 11-Apr-09
1669    ---------------------
1670    
1671    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
1672        (pcretest), all targets were linked against these libraries. This included
1673        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
1674        libraries. This caused unwanted dependencies to be created. This problem
1675        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
1676        pcretest is linked with readline.
1677    
1678    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
1679        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
1680        moved outside it again, because FALSE and TRUE are already defined in AIX,
1681        but BOOL is not.
1682    
1683    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
1684        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
1685    
1686    4.  The pcregrep documentation said spaces were inserted as well as colons (or
1687        hyphens) following file names and line numbers when outputting matching
1688        lines. This is not true; no spaces are inserted. I have also clarified the
1689        wording for the --colour (or --color) option.
1690    
1691    5.  In pcregrep, when --colour was used with -o, the list of matching strings
1692        was not coloured; this is different to GNU grep, so I have changed it to be
1693        the same.
1694    
1695    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
1696        each matching line was coloured. Now it goes on to look for further matches
1697        of any of the test patterns, which is the same behaviour as GNU grep.
1698    
1699    7.  A pattern that could match an empty string could cause pcregrep to loop; it
1700        doesn't make sense to accept an empty string match in pcregrep, so I have
1701        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1702        seems to be how GNU grep behaves. [But see later change 40 for release
1703        8.33.]
1704    
1705    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
1706        start or after a newline", because the conditional assertion was not being
1707        correctly handled. The rule now is that both the assertion and what follows
1708        in the first alternative must satisfy the test.
1709    
1710    9.  If auto-callout was enabled in a pattern with a conditional group whose
1711        condition was an assertion, PCRE could crash during matching, both with
1712        pcre_exec() and pcre_dfa_exec().
1713    
1714    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
1715        used for matching.
1716    
1717    11. Unicode property support in character classes was not working for
1718        characters (bytes) greater than 127 when not in UTF-8 mode.
1719    
1720    12. Added the -M command line option to pcretest.
1721    
1722    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
1723    
1724    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
1725    
1726    16. Added comments and documentation about mis-use of no_arg in the C++
1727        wrapper.
1728    
1729    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
1730        from Martin Jerabek that uses macro names for all relevant character and
1731        string constants.
1732    
1733    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
1734        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
1735        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
1736        these, but not everybody uses configure.
1737    
1738    19. A conditional group that had only one branch was not being correctly
1739        recognized as an item that could match an empty string. This meant that an
1740        enclosing group might also not be so recognized, causing infinite looping
1741        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
1742        with the subject "ab", where knowledge that the repeated group can match
1743        nothing is needed in order to break the loop.
1744    
1745    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
1746        exec(), but without supplying a callout function, matching went wrong.
1747    
1748    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
1749        leak if the size of the offset vector was greater than 30. When the vector
1750        is smaller, the saved offsets during recursion go onto a local stack
1751        vector, but for larger vectors malloc() is used. It was failing to free
1752        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
1753        error, in fact).
1754    
1755    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
1756        heapframe that is used only when UTF-8 support is enabled. This caused no
1757        problem, but was untidy.
1758    
1759    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
1760        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
1761        included within another project.
1762    
1763    24. Steven Van Ingelgem's patches to add more options to the CMake support,
1764        slightly modified by me:
1765    
1766          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
1767              not building pcregrep.
1768    
1769          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
1770              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
1771    
1772    25. Forward references, both numeric and by name, in patterns that made use of
1773        duplicate group numbers, could behave incorrectly or give incorrect errors,
1774        because when scanning forward to find the reference group, PCRE was not
1775        taking into account the duplicate group numbers. A pattern such as
1776        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
1777    
1778    26. Changed a few more instances of "const unsigned char *" to USPTR, making
1779        the feature of a custom pointer more persuasive (as requested by a user).
1780    
1781    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
1782        pcretest.c, inside #ifndefs, because it seems they are sometimes already
1783        pre-defined.
1784    
1785    28. Added support for (*UTF8) at the start of a pattern.
1786    
1787    29. Arrange for flags added by the "release type" setting in CMake to be shown
1788        in the configuration summary.
1789    
1790    
1791    Version 7.8 05-Sep-08
1792    ---------------------
1793    
1794    1.  Replaced UCP searching code with optimized version as implemented for Ad
1795        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
1796        stage table and inline lookup instead of a function, giving speed ups of 2
1797        to 5 times on some simple patterns that I tested. Permission was given to
1798        distribute the MultiStage2.py script that generates the tables (it's not in
1799        the tarball, but is in the Subversion repository).
1800    
1801    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
1802        scripts.
1803    
1804    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
1805        a group with a zero qualifier. The result of the study could be incorrect,
1806        or the function might crash, depending on the pattern.
1807    
1808    4.  Caseless matching was not working for non-ASCII characters in back
1809        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
1810        It now works when Unicode Property Support is available.
1811    
1812    5.  In pcretest, an escape such as \x{de} in the data was always generating
1813        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
1814        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
1815        truncation.
1816    
1817    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
1818    
1819    7.  Added two (int) casts to pcregrep when printing the difference of two
1820        pointers, in case they are 64-bit values.
1821    
1822    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
1823        test 2 if it fails.
1824    
1825    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
1826        and a #define of that name to empty if it is not externally set. This is to
1827        allow users of MSVC to set it if necessary.
1828    
1829    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
1830        the convenience functions in the pcre_get.c source file.
1831    
1832    11. An option change at the start of a pattern that had top-level alternatives
1833        could cause overwriting and/or a crash. This command provoked a crash in
1834        some environments:
1835    
1836          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
1837    
1838        This potential security problem was recorded as CVE-2008-2371.
1839    
1840    12. For a pattern where the match had to start at the beginning or immediately
1841        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
1842        pcre_dfa_exec() could read past the end of the passed subject if there was
1843        no match. To help with detecting such bugs (e.g. with valgrind), I modified
1844        pcretest so that it places the subject at the end of its malloc-ed buffer.
1845    
1846    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
1847        exec() might read past the end of the data buffer in UTF-8 mode.
1848    
1849    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
1850        the data contained the byte 0x85 as part of a UTF-8 character within its
1851        first line. This applied both to normal and DFA matching.
1852    
1853    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
1854        /^[^d]*?$/8 failed to match "abc".
1855    
1856    16. Added a missing copyright notice to pcrecpp_internal.h.
1857    
1858    17. Make it more clear in the documentation that values returned from
1859        pcre_exec() in ovector are byte offsets, not character counts.
1860    
1861    18. Tidied a few places to stop certain compilers from issuing warnings.
1862    
1863    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
1864        supplied by Stefan Weber. I made a further small update for 7.8 because
1865        there is a change of source arrangements: the pcre_searchfuncs.c module is
1866        replaced by pcre_ucd.c.
1867    
1868    
1869    Version 7.7 07-May-08
1870    ---------------------
1871    
1872    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
1873        a string to a long long, pretend we don't even have a long long." This is
1874        done by checking for the strtoq, strtoll, and _strtoi64 functions.
1875    
1876    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
1877        pre-7.6 versions, which defined a global no_arg variable instead of putting
1878        it in the RE class. (See also #8 below.)
1879    
1880    3.  Remove a line of dead code, identified by coverity and reported by Nuno
1881        Lopes.
1882    
1883    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
1884    
1885        (1) The include/exclude patterns were being applied to the whole pathnames
1886            of files, instead of just to the final components.
1887    
1888        (2) If there was more than one level of directory, the subdirectories were
1889            skipped unless they satisfied the include/exclude conditions. This is
1890            inconsistent with GNU grep (and could even be seen as contrary to the
1891            pcregrep specification - which I improved to make it absolutely clear).
1892            The action now is always to scan all levels of directory, and just
1893            apply the include/exclude patterns to regular files.
1894    
1895    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
1896        --exclude_dir in the tests to avoid scanning .svn directories.
1897    
1898    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
1899        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
1900        doesn't support NULs in patterns.
1901    
1902    7.  Added some missing "const"s to declarations of static tables in
1903        pcre_compile.c and pcre_dfa_exec.c.
1904    
1905    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
1906        caused by fix #2  above. (Subsequently also a second patch to fix the
1907        first patch. And a third patch - this was a messy problem.)
1908    
1909    9.  Applied Craig's patch to remove the use of push_back().
1910    
1911    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
1912        matching function regexec().
1913    
1914    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
1915        which, however, unlike Perl's \g{...}, are subroutine calls, not back
1916        references. PCRE supports relative numbers with this syntax (I don't think
1917        Oniguruma does).
1918    
1919    12. Previously, a group with a zero repeat such as (...){0} was completely
1920        omitted from the compiled regex. However, this means that if the group
1921        was called as a subroutine from elsewhere in the pattern, things went wrong
1922        (an internal error was given). Such groups are now left in the compiled
1923        pattern, with a new opcode that causes them to be skipped at execution
1924        time.
1925    
1926    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
1927        to the way PCRE behaves:
1928    
1929        (a) A lone ] character is dis-allowed (Perl treats it as data).
1930    
1931        (b) A back reference to an unmatched subpattern matches an empty string
1932            (Perl fails the current match path).
1933    
1934        (c) A data ] in a character class must be notated as \] because if the
1935            first data character in a class is ], it defines an empty class. (In
1936            Perl it is not possible to have an empty class.) The empty class []
1937            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
1938            The negative empty class [^] matches any one character, independently
1939            of the DOTALL setting.
1940    
1941    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
1942        non-existent subpattern following a character class starting with ']' and
1943        containing () gave an internal compiling error instead of "reference to
1944        non-existent subpattern". Fortunately, when the pattern did exist, the
1945        compiled code was correct. (When scanning forwards to check for the
1946        existence of the subpattern, it was treating the data ']' as terminating
1947        the class, so got the count wrong. When actually compiling, the reference
1948        was subsequently set up correctly.)
1949    
1950    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
1951        it was being rejected as not supported by pcre_dfa_exec(), even though
1952        other assertions are supported. I have made pcre_dfa_exec() support
1953        (*FAIL).
1954    
1955    16. The implementation of 13c above involved the invention of a new opcode,
1956        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
1957        cannot be changed at match time, I realized I could make a small
1958        improvement to matching performance by compiling OP_ALLANY instead of
1959        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
1960        on the OP_ANY path.
1961    
1962    17. Compiling pcretest on Windows with readline support failed without the
1963        following two fixes: (1) Make the unistd.h include conditional on
1964        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
1965    
1966    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
1967        ncurses library to be included for pcretest when ReadLine support is
1968        requested, but also to allow for it to be overridden. This patch came from
1969        Daniel Bergström.
1970    
1971    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
1972        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
1973        any errors with the current Unicode tables. Thanks to Peter Kankowski for
1974        spotting this.
1975    
1976    
1977    Version 7.6 28-Jan-08
1978    ---------------------
1979    
1980    1.  A character class containing a very large number of characters with
1981        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
1982        overflow.
1983    
1984    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
1985        HAVE_LONG_LONG is not defined.
1986    
1987    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
1988        bring them up to date and include new features. This patch includes:
1989    
1990        - Fixed PH's badly added libz and libbz2 support.
1991        - Fixed a problem with static linking.
1992        - Added pcredemo. [But later removed - see 7 below.]
1993        - Fixed dftables problem and added an option.
1994        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
1995            HAVE_LONG_LONG.
1996        - Added readline support for pcretest.
1997        - Added an listing of the option settings after cmake has run.
1998    
1999    4.  A user submitted a patch to Makefile that makes it easy to create
2000        "pcre.dll" under mingw when using Configure/Make. I added stuff to
2001        Makefile.am that cause it to include this special target, without
2002        affecting anything else. Note that the same mingw target plus all
2003        the other distribution libraries and programs are now supported
2004        when configuring with CMake (see 6 below) instead of with
2005        Configure/Make.
2006    
2007    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
2008        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
2009        exported in the Windows port". It has not yet been confirmed that the patch
2010        solves the problem, but it does no harm.
2011    
2012    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
2013        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
2014        with CMake, and also correct the comment about stack recursion.
2015    
2016    7.  Remove the automatic building of pcredemo from the ./configure system and
2017        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
2018        of a program that users should build themselves after PCRE is installed, so
2019        building it automatically is not really right. What is more, it gave
2020        trouble in some build environments.
2021    
2022    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
2023    
2024    
2025    Version 7.5 10-Jan-08
2026    ---------------------
2027    
2028    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
2029        values in parens when parsing an RE using the C++ wrapper."
2030    
2031    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
2032        Characters greater than 255 were excluded from the class instead of being
2033        included.
2034    
2035    3.  The same bug as (2) above applied to negated POSIX classes such as
2036        [:^space:].
2037    
2038    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
2039        defined or documented. It seems to have been a typo for PCRE_STATIC, so
2040        I have changed it.
2041    
2042    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
2043        first named subpattern) and a construct such as (?&a) would reference the
2044        first named subpattern whose name started with "a" (in other words, the
2045        length check was missing). Both these problems are fixed. "Subpattern name
2046        expected" is now given for (?&) (a zero-length name), and this patch also
2047        makes it give the same error for \k'' (previously it complained that that
2048        was a reference to a non-existent subpattern).
2049    
2050    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
2051        this is right because (?- can be followed by option settings as well as by
2052        digits. I have, however, made the messages clearer.
2053    
2054    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
2055        than the number used in the conditional) now cause a compile-time error.
2056        This is actually not compatible with Perl, which accepts such patterns, but
2057        treats the conditional as always being FALSE (as PCRE used to), but it
2058        seems to me that giving a diagnostic is better.
2059    
2060    8.  Change "alphameric" to the more common word "alphanumeric" in comments
2061        and messages.
2062    
2063    9.  Fix two occurrences of "backslash" in comments that should have been
2064        "backspace".
2065    
2066    10. Remove two redundant lines of code that can never be obeyed (their function
2067        was moved elsewhere).
2068    
2069    11. The program that makes PCRE's Unicode character property table had a bug
2070        which caused it to generate incorrect table entries for sequences of
2071        characters that have the same character type, but are in different scripts.
2072        It amalgamated them into a single range, with the script of the first of
2073        them. In other words, some characters were in the wrong script. There were
2074        thirteen such cases, affecting characters in the following ranges:
2075    
2076          U+002b0 - U+002c1
2077          U+0060c - U+0060d
2078          U+0061e - U+00612
2079          U+0064b - U+0065e
2080          U+0074d - U+0076d
2081          U+01800 - U+01805
2082          U+01d00 - U+01d77
2083          U+01d9b - U+01dbf
2084          U+0200b - U+0200f
2085          U+030fc - U+030fe
2086          U+03260 - U+0327f
2087          U+0fb46 - U+0fbb1
2088          U+10450 - U+1049d
2089    
2090    12. The -o option (show only the matching part of a line) for pcregrep was not
2091        compatible with GNU grep in that, if there was more than one match in a
2092        line, it showed only the first of them. It now behaves in the same way as
2093        GNU grep.
2094    
2095    13. If the -o and -v options were combined for pcregrep, it printed a blank
2096        line for every non-matching line. GNU grep prints nothing, and pcregrep now
2097        does the same. The return code can be used to tell if there were any
2098        non-matching lines.
2099    
2100    14. Added --file-offsets and --line-offsets to pcregrep.
2101    
2102    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
2103        infinitely looping recursion. The bug was that positive lookaheads were not
2104        being skipped when checking for a possible empty match (negative lookaheads
2105        and both kinds of lookbehind were skipped).
2106    
2107    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
2108        inclusion of <windows.h> to before rather than after the definition of
2109        INVALID_FILE_ATTRIBUTES (patch from David Byron).
2110    
2111    17. Specifying a possessive quantifier with a specific limit for a Unicode
2112        character property caused pcre_compile() to compile bad code, which led at
2113        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
2114        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
2115        caused the error; without that there was no problem.
2116    
2117    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
2118    
2119    19. Added --enable-pcretest-libreadline.
2120    
2121    20. In pcrecpp.cc, the variable 'count' was incremented twice in
2122        RE::GlobalReplace(). As a result, the number of replacements returned was
2123        double what it should be. I removed one of the increments, but Craig sent a
2124        later patch that removed the other one (the right fix) and added unit tests
2125        that check the return values (which was not done before).
2126    
2127    21. Several CMake things:
2128    
2129        (1) Arranged that, when cmake is used on Unix, the libraries end up with
2130            the names libpcre and libpcreposix, not just pcre and pcreposix.
2131    
2132        (2) The above change means that pcretest and pcregrep are now correctly
2133            linked with the newly-built libraries, not previously installed ones.
2134    
2135        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
2136    
2137    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
2138        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
2139        UTF-8 newline character). The key issue is that the pattern starts .*;
2140        this means that the match must be either at the beginning, or after a
2141        newline. The bug was in the code for advancing after a failed match and
2142        checking that the new position followed a newline. It was not taking
2143        account of UTF-8 characters correctly.
2144    
2145    23. PCRE was behaving differently from Perl in the way it recognized POSIX
2146        character classes. PCRE was not treating the sequence [:...:] as a
2147        character class unless the ... were all letters. Perl, however, seems to
2148        allow any characters between [: and :], though of course it rejects as
2149        unknown any "names" that contain non-letters, because all the known class
2150        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
2151        for example, whereas PCRE did not - it did not recognize a POSIX character
2152        class. This seemed a bit dangerous, so the code has been changed to be
2153        closer to Perl. The behaviour is not identical to Perl, because PCRE will
2154        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
2155        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
2156        Perl does, and where it didn't before.
2157    
2158    24. Rewrite so as to remove the single use of %n from pcregrep because in some
2159        Windows environments %n is disabled by default.
2160    
2161    
2162    Version 7.4 21-Sep-07
2163    ---------------------
2164    
2165    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
2166        means that a class such as [\s] counted as "explicit reference to CR or
2167        LF". That isn't really right - the whole point of the change was to try to
2168        help when there was an actual mention of one of the two characters. So now
2169        the change happens only if \r or \n (or a literal CR or LF) character is
2170        encountered.
2171    
2172    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
2173        of both had grown to the point where there were only 3 bits left.
2174        Fortunately, there was spare space in the data structure, and so I have
2175        moved the internal flags into a new 16-bit field to free up more option
2176        bits.
2177    
2178    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
2179        but did not set the internal JCHANGED flag - either of these is enough to
2180        control the way the "get" function works - but the PCRE_INFO_JCHANGED
2181        facility is supposed to tell if (?J) was ever used, so now (?J) at the
2182        start sets both bits.
2183    
2184    4.  Added options (at build time, compile time, exec time) to change \R from
2185        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
2186    
2187    5.  doc/pcresyntax.html was missing from the distribution.
2188    
2189    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
2190        compatibility, even though it is no longer used.
2191    
2192    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
2193        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
2194        windows.h file is present (where different names are used). [This was
2195        reversed later after testing - see 16 below.]
2196    
2197    8.  Changed all #include <config.h> to #include "config.h". There were also
2198        some further <pcre.h> cases that I changed to "pcre.h".
2199    
2200    9.  When pcregrep was used with the --colour option, it missed the line ending
2201        sequence off the lines that it output.
2202    
2203    10. It was pointed out to me that arrays of string pointers cause lots of
2204        relocations when a shared library is dynamically loaded. A technique of
2205        using a single long string with a table of offsets can drastically reduce
2206        these. I have refactored PCRE in four places to do this. The result is
2207        dramatic:
2208    
2209          Originally:                          290
2210          After changing UCP table:            187
2211          After changing error message table:   43
2212          After changing table of "verbs"       36
2213          After changing table of Posix names   22
2214    
2215        Thanks to the folks working on Gregex for glib for this insight.
2216    
2217    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
2218        unicode-properties was also set.
2219    
2220    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
2221    
2222    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
2223        checked only for CRLF.
2224    
2225    14. Added casts to pcretest.c to avoid compiler warnings.
2226    
2227    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
2228    
2229    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
2230        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
2231        entirely. This removes changes made in 7 above.
2232    
2233    17. The CMake files have been updated, and there is now more information about
2234        building with CMake in the NON-UNIX-USE document.
2235    
2236    
2237    Version 7.3 28-Aug-07
2238  ---------------------  ---------------------
2239    
2240   1. In the rejigging of the build system that eventually resulted in 7.1, the   1. In the rejigging of the build system that eventually resulted in 7.1, the
# Line 64  Version 7.3 05-Jul-07 Line 2297  Version 7.3 05-Jul-07
2297      dynamic way, which I have now done. The artificial limitation on group      dynamic way, which I have now done. The artificial limitation on group
2298      length has been removed - we now have only the limit on the total length of      length has been removed - we now have only the limit on the total length of
2299      the compiled pattern, which depends on the LINK_SIZE setting.      the compiled pattern, which depends on the LINK_SIZE setting.
2300    
2301  10. Fixed a bug in the documentation for get/copy named substring when  10. Fixed a bug in the documentation for get/copy named substring when
2302      duplicate names are permitted. If none of the named substrings are set, the      duplicate names are permitted. If none of the named substrings are set, the
2303      functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an      functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
2304      empty string.      empty string.
2305    
2306  11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E  11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
2307      instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,      instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
2308      because the ] is interpreted as the first data character and the      because the ] is interpreted as the first data character and the
2309      terminating ] is not found. PCRE has been made compatible with Perl in this      terminating ] is not found. PCRE has been made compatible with Perl in this
2310      regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could      regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
2311      cause memory overwriting.      cause memory overwriting.
2312    
2313  10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty  10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
2314      string has been matched (to stop an infinite loop). It was not recognizing      string has been matched (to stop an infinite loop). It was not recognizing
2315      a conditional subpattern that could match an empty string if that      a conditional subpattern that could match an empty string if that
2316      subpattern was within another subpattern. For example, it looped when      subpattern was within another subpattern. For example, it looped when
2317      trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the      trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
2318      condition was not nested. This bug has been fixed.      condition was not nested. This bug has been fixed.
2319    
2320  12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack  12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
2321      past the start of the subject in the presence of bytes with the top bit      past the start of the subject in the presence of bytes with the top bit
2322      set, for example "\x8aBCD".      set, for example "\x8aBCD".
2323    
2324    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
2325        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
2326    
2327    14. Optimized (?!) to (*FAIL).
2328    
2329    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
2330        This restricts code points to be within the range 0 to 0x10FFFF, excluding
2331        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
2332        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
2333        does: it's just the validity check that is more restrictive.
2334    
2335    16. Inserted checks for integer overflows during escape sequence (backslash)
2336        processing, and also fixed erroneous offset values for syntax errors during
2337        backslash processing.
2338    
2339    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
2340        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
2341    
2342    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
2343        caused an overrun.
2344    
2345    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
2346        something other than just ASCII characters) inside a group that had an
2347        unlimited repeat caused a loop at compile time (while checking to see
2348        whether the group could match an empty string).
2349    
2350    20. Debugging a pattern containing \p or \P could cause a crash. For example,
2351        [\P{Any}] did so. (Error in the code for printing property names.)
2352    
2353    21. An orphan \E inside a character class could cause a crash.
2354    
2355    22. A repeated capturing bracket such as (A)? could cause a wild memory
2356        reference during compilation.
2357    
2358    23. There are several functions in pcre_compile() that scan along a compiled
2359        expression for various reasons (e.g. to see if it's fixed length for look
2360        behind). There were bugs in these functions when a repeated \p or \P was
2361        present in the pattern. These operators have additional parameters compared
2362        with \d, etc, and these were not being taken into account when moving along
2363        the compiled data. Specifically:
2364    
2365        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
2366            length.
2367    
2368        (b) An item such as \pL+ within a repeated group could cause crashes or
2369            loops.
2370    
2371        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
2372            "reference to non-existent subpattern" error.
2373    
2374        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
2375    
2376    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
2377        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
2378    
2379    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
2380    
2381    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
2382        character were causing crashes (broken optimization).
2383    
2384    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
2385        \p or \P) caused a compile-time loop.
2386    
2387    28. More problems have arisen in unanchored patterns when CRLF is a valid line
2388        break. For example, the unstudied pattern [\r\n]A does not match the string
2389        "\r\nA" because change 7.0/46 below moves the current point on by two
2390        characters after failing to match at the start. However, the pattern \nA
2391        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
2392        the same is true. There doesn't seem any very clean way out of this, but
2393        what I have chosen to do makes the common cases work: PCRE now takes note
2394        of whether there can be an explicit match for \r or \n anywhere in the
2395        pattern, and if so, 7.0/46 no longer applies. As part of this change,
2396        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
2397        pattern has explicit CR or LF references.
2398    
2399    29. Added (*CR) etc for changing newline setting at start of pattern.
2400    
2401    
2402  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
2403  ---------------------  ---------------------

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

  ViewVC Help
Powered by ViewVC 1.1.5