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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.491  
changed lines
  Added in v.1418

  ViewVC Help
Powered by ViewVC 1.1.5