ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 836 by ph10, Wed Dec 28 17:16:11 2011 UTC revision 1366 by ph10, Sun Oct 6 18:34:33 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.30  Version 8.34 xx-xxxx-201x
5  ------------  --------------------------
7  1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this  1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
8      name is defined in ctype.h.      executable memory. Patch inspired by Carsten Klein.
10  2.  Fixed a bug in the code for calculating the fixed length of lookbehind  2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
11      assertions.      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.
18  3.  Removed the function pcre_info(), which has been obsolete and deprecated  3.  Make a small performance improvement in strlen16() and strlen32() in
19      since it was replaced by pcre_fullinfo() in February 2000.      pcretest.
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.
25    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
27    6.  In UTF mode, the code for checking whether a group could match an empty
28        string (which is used for indefinitely repeated groups to allow for
29        breaking an infinite loop) was broken when the group contained a repeated
30        negated single-character class with a character that occupied more than one
31        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
32        UTF-8 mode). The effect was undefined: the group might or might not be
33        deemed as matching an empty string, or the program might have crashed.
35    7.  The code for checking whether a group could match an empty string was not
36        recognizing that \h, \H, \v, \V, and \R must match a character.
38    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
39        an empty string. If it can, pcretest shows this in its information output.
41    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
42        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
43        matched by pcre_exec() without using JIT:
45        (a) If the rest of the pattern did not match after a maximal run of
46            grapheme clusters, the code for backing up to try with fewer of them
47            did not always back up over a full grapheme when characters that do not
48            have the modifier quality were involved, e.g. Hangul syllables.
50        (b) If the match point in a subject started with modifier character, and
51            there was no match, the code could incorrectly back up beyond the match
52            point, and potentially beyond the first character in the subject,
53            leading to a segfault or an incorrect match result.
55    10. A conditional group with an assertion condition could lead to PCRE
56        recording an incorrect first data item for a match if no other first data
57        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
58        first data item, and therefore matched "ca" after "c" instead of at the
59        start.
61    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
62        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
64    12. The source of pcregrep now includes z/OS-specific code so that it can be
65        compiled for z/OS as part of the special z/OS distribution.
67    13. Added the -T and -TM options to pcretest.
69    14. The code in pcre_compile.c for creating the table of named capturing groups
70        has been refactored. Instead of creating the table dynamically during the
71        actual compiling pass, the information is remembered during the pre-compile
72        pass (on the stack unless there are more than 20 named groups, in which
73        case malloc() is used) and the whole table is created before the actual
74        compile happens. This has simplified the code (it is now nearly 150 lines
75        shorter) and prepared the way for better handling of references to groups
76        with duplicate names.
78    15. A back reference to a named subpattern when there is more than one of the
79        same name now checks them in the order in which they appear in the pattern.
80        The first one that is set is used for the reference. Previously only the
81        first one was inspected. This change makes PCRE more compatible with Perl.
83    16. Unicode character properties were updated from Unicode 6.3.0.
85    17. The compile-time code for auto-possessification has been refactored, based
86        on a patch by Zoltan Herczeg. It now happens after instead of during
87        compilation. The code is cleaner, and more cases are handled. The option
88        PCRE_NO_AUTO_POSSESSIFY is added for testing purposes, and the -O and /O
89        options in pcretest are provided to set it.
91    18. The character VT has been added to the set of characters that match \s and
92        are generally treated as white space, following this same change in Perl
93        5.18. There is now no difference between "Perl space" and "POSIX space".
95    19. The code for checking named groups as conditions, either for being set or
96        for being recursed, has been refactored (this is related to 14 and 15
97        above). Processing unduplicated named groups should now be as fast at
98        numerical groups, and processing duplicated groups should be faster than
99        before.
102    Version 8.33 28-May-2013
103    ------------------------
105    1.  Added 'U' to some constants that are compared to unsigned integers, to
106        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
107        variables that are added to signed variables, to ensure the result is
108        signed and can be negated.
110    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
111        CMake config files.
113    3.  Revise the creation of config.h.generic so that all boolean macros are
114        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
115        overriding via -D on the command line possible.
117    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
118        to unsigned int is reported to make a quite noticeable speed difference in
119        a specific Windows environment. Testing on Linux did also appear to show
120        some benefit (and it is clearly not harmful). Also fixed the definition of
121        Xop which should be unsigned.
123    5.  Related to (4), changing the definition of the intermediate variable cc
124        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
125        improvements.
127    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
128        unnecessary spaces.
130    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
131        and later.
133    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
135    9.  Optimizing fast_forward_start_bits in JIT.
137    10. Adding support for callouts in JIT, and fixing some issues revealed
138        during this work. Namely:
140        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
142        (b) Minimum length was not checked before the matching is started.
144    11. The value of capture_last that is passed to callouts was incorrect in some
145        cases when there was a capture on one path that was subsequently abandoned
146        after a backtrack. Also, the capture_last value is now reset after a
147        recursion, since all captures are also reset in this case.
149    12. The interpreter no longer returns the "too many substrings" error in the
150        case when an overflowing capture is in a branch that is subsequently
151        abandoned after a backtrack.
153    13. In the pathological case when an offset vector of size 2 is used, pcretest
154        now prints out the matched string after a yield of 0 or 1.
156    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
157        Only supported by the JIT compiler at the moment.
159    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
161    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
162        offset of the starting point of the matching process, provided the offsets
163        vector is large enough.
165    17. The \A escape now records a lookbehind value of 1, though its execution
166        does not actually inspect the previous character. This is to ensure that,
167        in partial multi-segment matching, at least one character from the old
168        segment is retained when a new segment is processed. Otherwise, if there
169        are no lookbehinds in the pattern, \A might match incorrectly at the start
170        of a new segment.
172    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
174    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
175        gives some modest performance improvement in 8-bit mode.
177    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
178        be expressed in certain programming languages using Universal Character
179        Names.
181    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
182        which points out that "non characters" are not "characters that may not
183        appear in Unicode strings" but rather "characters that are reserved for
184        internal use and have only local meaning".
186    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
187        there was a conditional group that depended on an assertion, if the
188        assertion was false, the callout that immediately followed the alternation
189        in the condition was skipped when pcre_exec() was used for matching.
191    23. Allow an explicit callout to be inserted before an assertion that is the
192        condition for a conditional group, for compatibility with automatic
193        callouts, which always insert a callout at this point.
195    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
196        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
198    25. (*PRUNE) is now supported by the JIT compiler.
200    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
202    27. Fix the case where there are two or more SKIPs with arguments that may be
203        ignored.
205    28. (*SKIP) is now supported by the JIT compiler.
207    29. (*THEN) is now supported by the JIT compiler.
209    30. Update RunTest with additional test selector options.
211    31. The way PCRE handles backtracking verbs has been changed in two ways.
213        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
214        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
215        backtracking. In some cases this makes it more Perl-compatible, but Perl's
216        rather obscure rules do not always do the same thing.
218        (2) Previously, backtracking verbs were confined within assertions. This is
219        no longer the case for positive assertions, except for (*ACCEPT). Again,
220        this sometimes improves Perl compatibility, and sometimes does not.
222    32. A number of tests that were in test 2 because Perl did things differently
223        have been moved to test 1, because either Perl or PCRE has changed, and
224        these tests are now compatible.
226    32. Backtracking control verbs are now handled in the same way in JIT and
227        interpreter.
229    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
230        contained a forward subroutine reference caused a compile error.
232    34. Auto-detect and optimize limited repetitions in JIT.
234    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
235        blocking (*UTF) etc.
237    36. In the interpreter, maximizing pattern repetitions for characters and
238        character types now use tail recursion, which reduces stack usage.
240    37. The value of the max lookbehind was not correctly preserved if a compiled
241        and saved regex was reloaded on a host of different endianness.
243    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
244        of the compiled pattern block, expand the flags field from 16 to 32 bits
245        because it was almost full.
247    39. Try madvise first before posix_madvise.
249    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
250        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
251        original change locked out all matches of empty strings. This has been
252        changed so that one match of an empty string per line is recognized.
253        Subsequent searches on the same line (for colouring or for --only-matching,
254        for example) do not recognize empty strings.
256    41. Applied a user patch to fix a number of spelling mistakes in comments.
258    42. Data lines longer than 65536 caused pcretest to crash.
260    43. Clarified the data type for length and startoffset arguments for pcre_exec
261        and pcre_dfa_exec in the function-specific man pages, where they were
262        explicitly stated to be in bytes, never having been updated. I also added
263        some clarification to the pcreapi man page.
265    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
266        a segmentation fault.
269    Version 8.32 30-November-2012
270    -----------------------------
272    1.  Improved JIT compiler optimizations for first character search and single
273        character iterators.
275    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
276        Patch by Daniel Richard G.
278    3.  Single character iterator optimizations in the JIT compiler.
280    4.  Improved JIT compiler optimizations for character ranges.
282    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
283        Reported by Giuseppe D'Angelo.
285    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
286        of a line, was being set incorrectly in cases where .* appeared inside
287        atomic brackets at the start of a pattern, or where there was a subsequent
288        *PRUNE or *SKIP.
290    7.  Improved instruction cache flush for POWER/PowerPC.
291        Patch by Daniel Richard G.
293    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
294        grep:
296        (a) There is now no limit to the number of patterns to be matched.
298        (b) An error is given if a pattern is too long.
300        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
301            are now supported.
303        (d) --exclude-from and --include-from (multiple use) have been added.
305        (e) Exclusions and inclusions now apply to all files and directories, not
306            just to those obtained from scanning a directory recursively.
308        (f) Multiple uses of -f and --file-list are now supported.
310        (g) In a Windows environment, the default for -d has been changed from
311            "read" (the GNU grep default) to "skip", because otherwise the presence
312            of a directory in the file list provokes an error.
314        (h) The documentation has been revised and clarified in places.
316    9.  Improve the matching speed of capturing brackets.
318    10. Changed the meaning of \X so that it now matches a Unicode extended
319        grapheme cluster.
321    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
322        out POSIX threads when JIT support is configured.
324    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
326    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
327        structure could go wrong in environments where size_t is not the same size
328        as int.
330    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
331        set.
333    15. The EBCDIC support had decayed; later updates to the code had included
334        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
335        general tidy up of EBCDIC-related issues, and the documentation was also
336        not quite right. There is now a test that can be run on ASCII systems to
337        check some of the EBCDIC-related things (but is it not a full test).
339    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
340        in a small tidy to the code.
342    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
344    18. If the --only-matching (-o) option in pcregrep is specified multiple
345        times, each one causes appropriate output. For example, -o1 -o2 outputs the
346        substrings matched by the 1st and 2nd capturing parentheses. A separating
347        string can be specified by --om-separator (default empty).
349    19. Improving the first n character searches.
351    20. Turn case lists for horizontal and vertical white space into macros so that
352        they are defined only once.
354    21. This set of changes together give more compatible Unicode case-folding
355        behaviour for characters that have more than one other case when UCP
356        support is available.
358        (a) The Unicode property table now has offsets into a new table of sets of
359            three or more characters that are case-equivalent. The MultiStage2.py
360            script that generates these tables (the pcre_ucd.c file) now scans
361            CaseFolding.txt instead of UnicodeData.txt for character case
362            information.
364        (b) The code for adding characters or ranges of characters to a character
365            class has been abstracted into a generalized function that also handles
366            case-independence. In UTF-mode with UCP support, this uses the new data
367            to handle characters with more than one other case.
369        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
370            whose other case is greater than 256 are now correctly matched
371            caselessly. Previously, the high codepoint matched the low one, but not
372            vice versa.
374        (d) The processing of \h, \H, \v, and \ in character classes now makes use
375            of the new class addition function, using character lists defined as
376            macros alongside the case definitions of 20 above.
378        (e) Caseless back references now work with characters that have more than
379            one other case.
381        (f) General caseless matching of characters with more than one other case
382            is supported.
384    22. Unicode character properties were updated from Unicode 6.2.0
386    23. Improved CMake support under Windows. Patch by Daniel Richard G.
388    24. Add support for 32-bit character strings, and UTF-32
390    25. Major JIT compiler update (code refactoring and bugfixing).
391        Experimental Sparc 32 support is added.
393    26. Applied a modified version of Daniel Richard G's patch to create
394        pcre.h.generic and config.h.generic by "make" instead of in the
395        PrepareRelease script.
397    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
398        pcre_compile.c when checking for a zero character.
400    28. Introducing a native interface for JIT. Through this interface, the compiled
401        machine code can be directly executed. The purpose of this interface is to
402        provide fast pattern matching, so several sanity checks are not performed.
403        However, feature tests are still performed. The new interface provides
404        1.4x speedup compared to the old one.
406    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
407        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
408        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
410    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
411        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
412        the "old" RFC 2279). Instead, it ended up passing a negative length to
413        pcre_exec().
415    31. Add support for GCC's visibility feature to hide internal functions.
417    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
418        "unknown -C option" after outputting 0 or 1.
420    33. There is now support for generating a code coverage report for the test
421        suite in environments where gcc is the compiler and lcov is installed. This
422        is mainly for the benefit of the developers.
424    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
425        unaddressable using valgrind annotations, allowing valgrind to detect
426        invalid memory accesses. This is mainly for the benefit of the developers.
428    25. (*UTF) can now be used to start a pattern in any of the three libraries.
430    26. Give configure error if --enable-cpp but no C++ compiler found.
433    Version 8.31 06-July-2012
434    -------------------------
436    1.  Fixing a wrong JIT test case and some compiler warnings.
438    2.  Removed a bashism from the RunTest script.
440    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
441        to unsigned type, result still unsigned" that was given by an MS compiler
442        on encountering the code "-sizeof(xxx)".
444    4.  Partial matching support is added to the JIT compiler.
446    5.  Fixed several bugs concerned with partial matching of items that consist
447        of more than one character:
449        (a) /^(..)\1/ did not partially match "aba" because checking references was
450            done on an "all or nothing" basis. This also applied to repeated
451            references.
453        (b) \R did not give a hard partial match if \r was found at the end of the
454            subject.
456        (c) \X did not give a hard partial match after matching one or more
457            characters at the end of the subject.
459        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
460            a partial match for the string "\r".
462        (e) When newline was set to CRLF, the metacharacter "." did not recognize
463            a partial match for a CR character at the end of the subject string.
465    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
466        running pcretest, the text "(JIT)" added to the output whenever JIT is
467        actually used to run the match.
469    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
470        or /S+[+] with a digit between 1 and 7.
472    8.  OP_NOT now supports any UTF character not just single-byte ones.
474    9.  (*MARK) control verb is now supported by the JIT compiler.
476    10. The command "./RunTest list" lists the available tests without actually
477        running any of them. (Because I keep forgetting what they all are.)
481    12. Applied a (slightly modified) user-supplied patch that improves performance
482        when the heap is used for recursion (compiled with --disable-stack-for-
483        recursion). Instead of malloc and free for each heap frame each time a
484        logical recursion happens, frames are retained on a chain and re-used where
485        possible. This sometimes gives as much as 30% improvement.
487    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
488        call.
490    14. As documented, (*COMMIT) is now confined to within a positive assertion.
492    15. It is now possible to link pcretest with libedit as an alternative to
493        libreadline.
495    16. (*COMMIT) control verb is now supported by the JIT compiler.
497    17. The Unicode data tables have been updated to Unicode 6.1.0.
499    18. Added --file-list option to pcregrep.
501    19. Added binary file support to pcregrep, including the -a, --binary-files,
502        -I, and --text options.
504    20. The madvise function is renamed for posix_madvise for QNX compatibility
505        reasons. Fixed by Giuseppe D'Angelo.
507    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
509    22. Changed the option for creating symbolic links for 16-bit man pages from
510        -s to -sf so that re-installing does not cause issues.
512    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
514    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
515        matches in certain environments (the workspace was not being correctly
516        retained). Also added to pcre_dfa_exec() a simple plausibility check on
517        some of the workspace data at the beginning of a restart.
519    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
520        was not doing so when it should - probably a typo introduced by SVN 528
521        (change 8.10/14).
523    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
524        \w+ when the character tables indicated that \x{c4} was a word character.
525        There were several related cases, all because the tests for doing a table
526        lookup were testing for characters less than 127 instead of 255.
528    27. If a pattern contains capturing parentheses that are not used in a match,
529        their slots in the ovector are set to -1. For those that are higher than
530        any matched groups, this happens at the end of processing. In the case when
531        there were back references that the ovector was too small to contain
532        (causing temporary malloc'd memory to be used during matching), and the
533        highest capturing number was not used, memory off the end of the ovector
534        was incorrectly being set to -1. (It was using the size of the temporary
535        memory instead of the true size.)
537    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
538        ovector size, it uses memory at the end of the block that it has got.
540    29. Check for an overlong MARK name and give an error at compile time. The
541        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
543    30. JIT compiler update.
545    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
546        Rill for the patch.
548    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
550    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
552    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
553        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
554        was enabled.
556    35. Improve JIT code generation for greedy plus quantifier.
558    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
559        1 to "aa" instead of to an empty string. The bug affected repeated groups
560        that could potentially match an empty string.
562    37. Optimizing single character iterators in JIT.
564    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
565        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
566        codepoints that are too big for the mode are faulted, and in a UTF mode,
567        disallowed codepoints are also faulted.
569    39. If PCRE was compiled with UTF support, in three places in the DFA
570        matcher there was code that should only have been obeyed in UTF mode, but
571        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
572        processing when bytes with values greater than 127 were present. In 16-bit
573        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
574        both cases the values are those that cannot be the first data item in a UTF
575        character. The three items that might have provoked this were recursions,
576        possessively repeated groups, and atomic groups.
578    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
579        and pcregrep, because some OS require shared objects to be explicitly
580        passed to ld, causing the link step to fail if they are not.
582    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
583        mode, patterns that started with \h* or \R* might be incorrectly matched.
586    Version 8.30 04-February-2012
587    -----------------------------
589    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
590        name is defined in ctype.h.
592    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
593        only in quite long subpatterns.
595    3.  Removed the function pcre_info(), which has been obsolete and deprecated
596        since it was replaced by pcre_fullinfo() in February 2000.
598  4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not  4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
599      match a (*MARK), and the match failed at the start of the subject, a      match a (*MARK), and the match failed at the start of the subject, a
600      reference to memory before the start of the subject could occur. This bug      reference to memory before the start of the subject could occur. This bug
601      was introduced by fix 17 of release 8.21.      was introduced by fix 17 of release 8.21.
603  5.  A reference to an unset group with zero minimum repetition was giving  5.  A reference to an unset group with zero minimum repetition was giving
604      totally wrong answers (in non-JavaScript-compatibility mode). For example,      totally wrong answers (in non-JavaScript-compatibility mode). For example,
605      /(another)?(\1?)test/ matched against "hello world test". This bug was      /(another)?(\1?)test/ matched against "hello world test". This bug was
606      introduced in release 8.13.      introduced in release 8.13.
608  6.  Add support for 16-bit character strings (a large amount of work involving  6.  Add support for 16-bit character strings (a large amount of work involving
609      many changes and refactorings).      many changes and refactorings).
611    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
612        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
613        from a file.
615    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
616        rounding is not applied in this particular case).
618    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
619        if they appear, or are escaped, in patterns.
621    10. Get rid of a number of -Wunused-but-set-variable warnings.
623    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
624        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
625        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
626        also returns the mark "x". This bug applied to capturing parentheses,
627        non-capturing parentheses, and atomic parentheses. It also applied to some
628        assertions.
630    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
631        information out of configure.ac instead of relying on pcre.h.generic, which
632        is not stored in the repository.
634    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
635        -lreadline.
637    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
639    15. Applied Graycode's patch to put the top-level frame on the stack rather
640        than the heap when not using the stack for recursion. This gives a
641        performance improvement in many cases when recursion is not deep.
643    16. Experimental code added to "pcretest -C" to output the stack frame size.
646  Version 8.21 12-Dec-2011  Version 8.21 12-Dec-2011
647  ------------------------  ------------------------
# Line 1157  Version 7.9 11-Apr-09 Line 1773  Version 7.9 11-Apr-09
1773  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
1774      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
1775      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1776      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1777        8.33.]
1779  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
1780      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 1400  Version 7.7 07-May-08 Line 2017  Version 7.7 07-May-08
2017      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2018      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2019      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2020      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2021      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2022      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.836  
changed lines
  Added in v.1366

  ViewVC Help
Powered by ViewVC 1.1.5