ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 168 by ph10, Tue May 29 15:18:18 2007 UTC revision 488 by ph10, Mon Jan 11 15:29:42 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.2 01-May-07  Version 8.01 01-Jan-10
5    ----------------------
7    1.  If a pattern contained a conditional subpattern with only one branch (in
8        particular, this includes all (DEFINE) patterns), a call to pcre_study()
9        computed the wrong minimum data length (which is of course zero for such
10        subpatterns).
12    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
13        the pattern is reset in the first branch, pcre_compile() failed with
14        "internal error: code overflow at offset...". This happened only when
15        the reset was to the original external option setting. (An optimization
16        abstracts leading options settings into an external setting, which was the
17        cause of this.)
19    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
20        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
21        assertion pattern did not match (meaning that the assertion was true), it
22        was incorrectly treated as false if the SKIP had been reached during the
23        matching. This also applied to assertions used as conditions.
25    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
26        assertion subpattern, including such a pattern used as a condition,
27        unpredictable results occurred, instead of the error return
30    5.  The C++ GlobalReplace function was not working like Perl for the special
31        situation when an empty string is matched. It now does the fancy magic
32        stuff that is necessary.
34    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
35        removed. (These were left over from very, very early versions of PCRE.)
37    7.  Some cosmetic changes to the code to make life easier when compiling it
38        as part of something else:
40        (a) Change DEBUG to PCRE_DEBUG.
42        (b) In pcre_compile(), rename the member of the "branch_chain" structure
43            called "current" as "current_branch", to prevent a collision with the
44            Linux macro when compiled as a kernel module.
46        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
47            prevent a collision with the Linux macro when compiled as a kernel
48            module.
50    8.  In pcre_compile() there are some checks for integer overflows that used to
51        cast potentially large values to (double). This has been changed to that
52        when building, a check for int64_t is made, and if it is found, it is used
53        instead, thus avoiding the use of floating point arithmetic. (There is no
54        other use of FP in PCRE.) If int64_t is not found, the fallback is to
55        double.
57    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
58        2005 (difference between two addresses compared to an unsigned value).
60    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
61        custom one, because of the following reported problem in Windows:
63          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
64            under Win32.
65          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
66            therefore missing the function definition.
67          - The compiler thus generates a "C" signature for the test function.
68          - The linker fails to find the "C" function.
69          - PCRE fails to configure if asked to do so against libbz2.
71    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
72        messages were output:
74          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
75          rerunning libtoolize, to keep the correct libtool macros in-tree.
76          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
78        I have done both of these things.
80    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
81        most of the time, it *can* run out if it is given a pattern that contains a
82        runaway infinite recursion. I updated the discussion in the pcrestack man
83        page.
85    13. Now that we have gone to the x.xx style of version numbers, the minor
86        version may start with zero. Using 08 or 09 is a bad idea because users
87        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
88        interpreted as invalid octal numbers. I've updated the previous comment in
89        configure.ac, and also added a check that gives an error if 08 or 09 are
90        used.
92    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
93        causing partial matching to fail when the end of the subject matched \W
94        in a UTF-8 pattern where \W was quantified with a minimum of 3.
96    15. There were some discrepancies between the declarations in pcre_internal.h
97        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
98        their definitions. The declarations used "const uschar *" and the
99        definitions used USPTR. Even though USPTR is normally defined as "const
100        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
101        reported that: "This difference in casting confuses some C++ compilers, for
102        example, SunCC recognizes above declarations as different functions and
103        generates broken code for hbpcre." I have changed the declarations to use
104        USPTR.
106    16. GNU libtool is named differently on some systems. The autogen.sh script now
107        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
108        (FreeBSD).
110    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
111        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
112        comment: "Figure out how to create a longlong from a string: strtoll and
113        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
114        instance, but it only takes 2 args instead of 3!"
116    18. A subtle bug concerned with back references has been fixed by a change of
117        specification, with a corresponding code fix. A pattern such as
118        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
119        refers, was giving matches when it shouldn't. For example, xa=xaaa would
120        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
121        same bug. Such groups have to be quantified to be useful, or contained
122        inside another quantified group. (If there's no repetition, the reference
123        can never match.) The problem arises because, having left the group and
124        moved on to the rest of the pattern, a later failure that backtracks into
125        the group uses the captured value from the final iteration of the group
126        rather than the correct earlier one. I have fixed this in PCRE by forcing
127        any group that contains a reference to itself to be an atomic group; that
128        is, there cannot be any backtracking into it once it has completed. This is
129        similar to recursive and subroutine calls.
132    Version 8.00 19-Oct-09
133    ----------------------
135    1.  The table for translating pcre_compile() error codes into POSIX error codes
136        was out-of-date, and there was no check on the pcre_compile() error code
137        being within the table. This could lead to an OK return being given in
138        error.
140    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
141        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
142        in a Windows environment.
144    3.  The pcregrep --count option prints the count for each file even when it is
145        zero, as does GNU grep. However, pcregrep was also printing all files when
146        --files-with-matches was added. Now, when both options are given, it prints
147        counts only for those files that have at least one match. (GNU grep just
148        prints the file name in this circumstance, but including the count seems
149        more useful - otherwise, why use --count?) Also ensured that the
150        combination -clh just lists non-zero counts, with no names.
152    4.  The long form of the pcregrep -F option was incorrectly implemented as
153        --fixed_strings instead of --fixed-strings. This is an incompatible change,
154        but it seems right to fix it, and I didn't think it was worth preserving
155        the old behaviour.
157    5.  The command line items --regex=pattern and --regexp=pattern were not
158        recognized by pcregrep, which required --regex pattern or --regexp pattern
159        (with a space rather than an '='). The man page documented the '=' forms,
160        which are compatible with GNU grep; these now work.
162    6.  No libpcreposix.pc file was created for pkg-config; there was just
163        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
165    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
166        when UCP support is not needed, by modifying the Python script that
167        generates it from Unicode data files. This should not matter if the module
168        is correctly used as a library, but I received one complaint about 50K of
169        unwanted data. My guess is that the person linked everything into his
170        program rather than using a library. Anyway, it does no harm.
172    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
173        was a minimum greater than 1 for a wide character in a possessive
174        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
175        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
176        character. Chaos in the form of incorrect output or a compiling loop could
177        result.
179    9.  The restrictions on what a pattern can contain when partial matching is
180        requested for pcre_exec() have been removed. All patterns can now be
181        partially matched by this function. In addition, if there are at least two
182        slots in the offset vector, the offset of the earliest inspected character
183        for the match and the offset of the end of the subject are set in them when
184        PCRE_ERROR_PARTIAL is returned.
186    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
187        synonymous with PCRE_PARTIAL, for backwards compatibility, and
188        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
189        and may be more useful for multi-segment matching.
191    11. Partial matching with pcre_exec() is now more intuitive. A partial match
192        used to be given if ever the end of the subject was reached; now it is
193        given only if matching could not proceed because another character was
194        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
195        string "Z", which now yields "no match" instead of "partial match". In the
196        case of pcre_dfa_exec(), "no match" is given if every matching path for the
197        final character ended with (*FAIL).
199    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
200        if the pattern had a "must contain" character that was already found in the
201        earlier partial match, unless partial matching was again requested. For
202        example, with the pattern /dog.(body)?/, the "must contain" character is
203        "g". If the first part-match was for the string "dog", restarting with
204        "sbody" failed. This bug has been fixed.
206    13. The string returned by pcre_dfa_exec() after a partial match has been
207        changed so that it starts at the first inspected character rather than the
208        first character of the match. This makes a difference only if the pattern
209        starts with a lookbehind assertion or \b or \B (\K is not supported by
210        pcre_dfa_exec()). It's an incompatible change, but it makes the two
211        matching functions compatible, and I think it's the right thing to do.
213    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
214        so that the demonstration program is easily available in environments where
215        PCRE has not been installed from source.
217    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
218        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
219        library.
221    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
222        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
223        is not the first non-POSIX option to be added. Clearly some people find
224        these options useful.
226    17. If a caller to the POSIX matching function regexec() passes a non-zero
227        value for nmatch with a NULL value for pmatch, the value of
228        nmatch is forced to zero.
230    18. RunGrepTest did not have a test for the availability of the -u option of
231        the diff command, as RunTest does. It now checks in the same way as
232        RunTest, and also checks for the -b option.
234    19. If an odd number of negated classes containing just a single character
235        interposed, within parentheses, between a forward reference to a named
236        subpattern and the definition of the subpattern, compilation crashed with
237        an internal error, complaining that it could not find the referenced
238        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
239        [The bug was that it was starting one character too far in when skipping
240        over the character class, thus treating the ] as data rather than
241        terminating the class. This meant it could skip too much.]
243    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
244        /g option in pcretest when the pattern contains \K, which makes it possible
245        to have an empty string match not at the start, even when the pattern is
246        anchored. Updated pcretest and pcredemo to use this option.
248    21. If the maximum number of capturing subpatterns in a recursion was greater
249        than the maximum at the outer level, the higher number was returned, but
250        with unset values at the outer level. The correct (outer level) value is
251        now given.
253    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
254        PCRE did not set those parentheses (unlike Perl). I have now found a way to
255        make it do so. The string so far is captured, making this feature
256        compatible with Perl.
258    23. The tests have been re-organized, adding tests 11 and 12, to make it
259        possible to check the Perl 5.10 features against Perl 5.10.
261    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
262        pattern matches a fixed length string. PCRE did not allow this; now it
263        does. Neither allows recursion.
265    25. I finally figured out how to implement a request to provide the minimum
266        length of subject string that was needed in order to match a given pattern.
267        (It was back references and recursion that I had previously got hung up
268        on.) This code has now been added to pcre_study(); it finds a lower bound
269        to the length of subject needed. It is not necessarily the greatest lower
270        bound, but using it to avoid searching strings that are too short does give
271        some useful speed-ups. The value is available to calling programs via
272        pcre_fullinfo().
274    26. While implementing 25, I discovered to my embarrassment that pcretest had
275        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
276        study optimizations had never been tested with that matching function.
277        Oops. What is worse, even when it was passed study data, there was a bug in
278        pcre_dfa_exec() that meant it never actually used it. Double oops. There
279        were also very few tests of studied patterns with pcre_dfa_exec().
281    27. If (?| is used to create subpatterns with duplicate numbers, they are now
282        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
283        on the other side of the coin, they are no longer allowed to have different
284        names, because these cannot be distinguished in PCRE, and this has caused
285        confusion. (This is a difference from Perl.)
287    28. When duplicate subpattern names are present (necessarily with different
288        numbers, as required by 27 above), and a test is made by name in a
289        conditional pattern, either for a subpattern having been matched, or for
290        recursion in such a pattern, all the associated numbered subpatterns are
291        tested, and the overall condition is true if the condition is true for any
292        one of them. This is the way Perl works, and is also more like the way
293        testing by number works.
296    Version 7.9 11-Apr-09
297    ---------------------
299    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
300        (pcretest), all targets were linked against these libraries. This included
301        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
302        libraries. This caused unwanted dependencies to be created. This problem
303        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
304        pcretest is linked with readline.
306    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
307        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
308        moved outside it again, because FALSE and TRUE are already defined in AIX,
309        but BOOL is not.
311    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
312        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
314    4.  The pcregrep documentation said spaces were inserted as well as colons (or
315        hyphens) following file names and line numbers when outputting matching
316        lines. This is not true; no spaces are inserted. I have also clarified the
317        wording for the --colour (or --color) option.
319    5.  In pcregrep, when --colour was used with -o, the list of matching strings
320        was not coloured; this is different to GNU grep, so I have changed it to be
321        the same.
323    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
324        each matching line was coloured. Now it goes on to look for further matches
325        of any of the test patterns, which is the same behaviour as GNU grep.
327    7.  A pattern that could match an empty string could cause pcregrep to loop; it
328        doesn't make sense to accept an empty string match in pcregrep, so I have
329        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
330        seems to be how GNU grep behaves.
332    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
333        start or after a newline", because the conditional assertion was not being
334        correctly handled. The rule now is that both the assertion and what follows
335        in the first alternative must satisfy the test.
337    9.  If auto-callout was enabled in a pattern with a conditional group whose
338        condition was an assertion, PCRE could crash during matching, both with
339        pcre_exec() and pcre_dfa_exec().
341    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
342        used for matching.
344    11. Unicode property support in character classes was not working for
345        characters (bytes) greater than 127 when not in UTF-8 mode.
347    12. Added the -M command line option to pcretest.
349    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
351    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
353    16. Added comments and documentation about mis-use of no_arg in the C++
354        wrapper.
356    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
357        from Martin Jerabek that uses macro names for all relevant character and
358        string constants.
360    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
361        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
362        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
363        these, but not everybody uses configure.
365    19. A conditional group that had only one branch was not being correctly
366        recognized as an item that could match an empty string. This meant that an
367        enclosing group might also not be so recognized, causing infinite looping
368        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
369        with the subject "ab", where knowledge that the repeated group can match
370        nothing is needed in order to break the loop.
372    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
373        exec(), but without supplying a callout function, matching went wrong.
375    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
376        leak if the size of the offset vector was greater than 30. When the vector
377        is smaller, the saved offsets during recursion go onto a local stack
378        vector, but for larger vectors malloc() is used. It was failing to free
379        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
380        error, in fact).
382    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
383        heapframe that is used only when UTF-8 support is enabled. This caused no
384        problem, but was untidy.
386    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
387        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
388        included within another project.
390    24. Steven Van Ingelgem's patches to add more options to the CMake support,
391        slightly modified by me:
393          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
394              not building pcregrep.
396          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
397              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
399    25. Forward references, both numeric and by name, in patterns that made use of
400        duplicate group numbers, could behave incorrectly or give incorrect errors,
401        because when scanning forward to find the reference group, PCRE was not
402        taking into account the duplicate group numbers. A pattern such as
403        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
405    26. Changed a few more instances of "const unsigned char *" to USPTR, making
406        the feature of a custom pointer more persuasive (as requested by a user).
408    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
409        pcretest.c, inside #ifndefs, because it seems they are sometimes already
410        pre-defined.
412    28. Added support for (*UTF8) at the start of a pattern.
414    29. Arrange for flags added by the "release type" setting in CMake to be shown
415        in the configuration summary.
418    Version 7.8 05-Sep-08
419    ---------------------
421    1.  Replaced UCP searching code with optimized version as implemented for Ad
422        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
423        stage table and inline lookup instead of a function, giving speed ups of 2
424        to 5 times on some simple patterns that I tested. Permission was given to
425        distribute the MultiStage2.py script that generates the tables (it's not in
426        the tarball, but is in the Subversion repository).
428    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
429        scripts.
431    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
432        a group with a zero qualifier. The result of the study could be incorrect,
433        or the function might crash, depending on the pattern.
435    4.  Caseless matching was not working for non-ASCII characters in back
436        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
437        It now works when Unicode Property Support is available.
439    5.  In pcretest, an escape such as \x{de} in the data was always generating
440        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
441        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
442        truncation.
444    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
446    7.  Added two (int) casts to pcregrep when printing the difference of two
447        pointers, in case they are 64-bit values.
449    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
450        test 2 if it fails.
452    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
453        and a #define of that name to empty if it is not externally set. This is to
454        allow users of MSVC to set it if necessary.
456    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
457        the convenience functions in the pcre_get.c source file.
459    11. An option change at the start of a pattern that had top-level alternatives
460        could cause overwriting and/or a crash. This command provoked a crash in
461        some environments:
463          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
465        This potential security problem was recorded as CVE-2008-2371.
467    12. For a pattern where the match had to start at the beginning or immediately
468        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
469        pcre_dfa_exec() could read past the end of the passed subject if there was
470        no match. To help with detecting such bugs (e.g. with valgrind), I modified
471        pcretest so that it places the subject at the end of its malloc-ed buffer.
473    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
474        exec() might read past the end of the data buffer in UTF-8 mode.
476    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
477        the data contained the byte 0x85 as part of a UTF-8 character within its
478        first line. This applied both to normal and DFA matching.
480    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
481        /^[^d]*?$/8 failed to match "abc".
483    16. Added a missing copyright notice to pcrecpp_internal.h.
485    17. Make it more clear in the documentation that values returned from
486        pcre_exec() in ovector are byte offsets, not character counts.
488    18. Tidied a few places to stop certain compilers from issuing warnings.
490    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
491        supplied by Stefan Weber. I made a further small update for 7.8 because
492        there is a change of source arrangements: the pcre_searchfuncs.c module is
493        replaced by pcre_ucd.c.
496    Version 7.7 07-May-08
497    ---------------------
499    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
500        a string to a long long, pretend we don't even have a long long." This is
501        done by checking for the strtoq, strtoll, and _strtoi64 functions.
503    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
504        pre-7.6 versions, which defined a global no_arg variable instead of putting
505        it in the RE class. (See also #8 below.)
507    3.  Remove a line of dead code, identified by coverity and reported by Nuno
508        Lopes.
510    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
512        (1) The include/exclude patterns were being applied to the whole pathnames
513            of files, instead of just to the final components.
515        (2) If there was more than one level of directory, the subdirectories were
516            skipped unless they satisfied the include/exclude conditions. This is
517            inconsistent with GNU grep (and could even be seen as contrary to the
518            pcregrep specification - which I improved to make it absolutely clear).
519            The action now is always to scan all levels of directory, and just
520            apply the include/exclude patterns to regular files.
522    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
523        --exclude_dir in the tests to avoid scanning .svn directories.
525    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
526        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
527        doesn't support NULs in patterns.
529    7.  Added some missing "const"s to declarations of static tables in
530        pcre_compile.c and pcre_dfa_exec.c.
532    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
533        caused by fix #2  above. (Subsequently also a second patch to fix the
534        first patch. And a third patch - this was a messy problem.)
536    9.  Applied Craig's patch to remove the use of push_back().
538    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
539        matching function regexec().
541    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
542        which, however, unlike Perl's \g{...}, are subroutine calls, not back
543        references. PCRE supports relative numbers with this syntax (I don't think
544        Oniguruma does).
546    12. Previously, a group with a zero repeat such as (...){0} was completely
547        omitted from the compiled regex. However, this means that if the group
548        was called as a subroutine from elsewhere in the pattern, things went wrong
549        (an internal error was given). Such groups are now left in the compiled
550        pattern, with a new opcode that causes them to be skipped at execution
551        time.
553    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
554        to the way PCRE behaves:
556        (a) A lone ] character is dis-allowed (Perl treats it as data).
558        (b) A back reference to an unmatched subpattern matches an empty string
559            (Perl fails the current match path).
561        (c) A data ] in a character class must be notated as \] because if the
562            first data character in a class is ], it defines an empty class. (In
563            Perl it is not possible to have an empty class.) The empty class []
564            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
565            The negative empty class [^] matches any one character, independently
566            of the DOTALL setting.
568    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
569        non-existent subpattern following a character class starting with ']' and
570        containing () gave an internal compiling error instead of "reference to
571        non-existent subpattern". Fortunately, when the pattern did exist, the
572        compiled code was correct. (When scanning forwards to check for the
573        existencd of the subpattern, it was treating the data ']' as terminating
574        the class, so got the count wrong. When actually compiling, the reference
575        was subsequently set up correctly.)
577    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
578        it was being rejected as not supported by pcre_dfa_exec(), even though
579        other assertions are supported. I have made pcre_dfa_exec() support
580        (*FAIL).
582    16. The implementation of 13c above involved the invention of a new opcode,
583        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
584        cannot be changed at match time, I realized I could make a small
585        improvement to matching performance by compiling OP_ALLANY instead of
586        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
587        on the OP_ANY path.
589    17. Compiling pcretest on Windows with readline support failed without the
590        following two fixes: (1) Make the unistd.h include conditional on
591        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
593    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
594        ncurses library to be included for pcretest when ReadLine support is
595        requested, but also to allow for it to be overridden. This patch came from
596        Daniel Bergström.
598    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
599        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
600        any errors with the current Unicode tables. Thanks to Peter Kankowski for
601        spotting this.
604    Version 7.6 28-Jan-08
605    ---------------------
607    1.  A character class containing a very large number of characters with
608        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
609        overflow.
611    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
612        HAVE_LONG_LONG is not defined.
614    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
615        bring them up to date and include new features. This patch includes:
617        - Fixed PH's badly added libz and libbz2 support.
618        - Fixed a problem with static linking.
619        - Added pcredemo. [But later removed - see 7 below.]
620        - Fixed dftables problem and added an option.
621        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
622            HAVE_LONG_LONG.
623        - Added readline support for pcretest.
624        - Added an listing of the option settings after cmake has run.
626    4.  A user submitted a patch to Makefile that makes it easy to create
627        "pcre.dll" under mingw when using Configure/Make. I added stuff to
628        Makefile.am that cause it to include this special target, without
629        affecting anything else. Note that the same mingw target plus all
630        the other distribution libraries and programs are now supported
631        when configuring with CMake (see 6 below) instead of with
632        Configure/Make.
634    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
635        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
636        exported in the Windows port". It has not yet been confirmed that the patch
637        solves the problem, but it does no harm.
639    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
640        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
641        with CMake, and also correct the comment about stack recursion.
643    7.  Remove the automatic building of pcredemo from the ./configure system and
644        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
645        of a program that users should build themselves after PCRE is installed, so
646        building it automatically is not really right. What is more, it gave
647        trouble in some build environments.
649    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
652    Version 7.5 10-Jan-08
653    ---------------------
655    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
656        values in parens when parsing an RE using the C++ wrapper."
658    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
659        Characters greater than 255 were excluded from the class instead of being
660        included.
662    3.  The same bug as (2) above applied to negated POSIX classes such as
663        [:^space:].
665    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
666        defined or documented. It seems to have been a typo for PCRE_STATIC, so
667        I have changed it.
669    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
670        first named subpattern) and a construct such as (?&a) would reference the
671        first named subpattern whose name started with "a" (in other words, the
672        length check was missing). Both these problems are fixed. "Subpattern name
673        expected" is now given for (?&) (a zero-length name), and this patch also
674        makes it give the same error for \k'' (previously it complained that that
675        was a reference to a non-existent subpattern).
677    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
678        this is right because (?- can be followed by option settings as well as by
679        digits. I have, however, made the messages clearer.
681    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
682        than the number used in the conditional) now cause a compile-time error.
683        This is actually not compatible with Perl, which accepts such patterns, but
684        treats the conditional as always being FALSE (as PCRE used to), but it
685        seems to me that giving a diagnostic is better.
687    8.  Change "alphameric" to the more common word "alphanumeric" in comments
688        and messages.
690    9.  Fix two occurrences of "backslash" in comments that should have been
691        "backspace".
693    10. Remove two redundant lines of code that can never be obeyed (their function
694        was moved elsewhere).
696    11. The program that makes PCRE's Unicode character property table had a bug
697        which caused it to generate incorrect table entries for sequences of
698        characters that have the same character type, but are in different scripts.
699        It amalgamated them into a single range, with the script of the first of
700        them. In other words, some characters were in the wrong script. There were
701        thirteen such cases, affecting characters in the following ranges:
703          U+002b0 - U+002c1
704          U+0060c - U+0060d
705          U+0061e - U+00612
706          U+0064b - U+0065e
707          U+0074d - U+0076d
708          U+01800 - U+01805
709          U+01d00 - U+01d77
710          U+01d9b - U+01dbf
711          U+0200b - U+0200f
712          U+030fc - U+030fe
713          U+03260 - U+0327f
714          U+0fb46 - U+0fbb1
715          U+10450 - U+1049d
717    12. The -o option (show only the matching part of a line) for pcregrep was not
718        compatible with GNU grep in that, if there was more than one match in a
719        line, it showed only the first of them. It now behaves in the same way as
720        GNU grep.
722    13. If the -o and -v options were combined for pcregrep, it printed a blank
723        line for every non-matching line. GNU grep prints nothing, and pcregrep now
724        does the same. The return code can be used to tell if there were any
725        non-matching lines.
727    14. Added --file-offsets and --line-offsets to pcregrep.
729    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
730        infinitely looping recursion. The bug was that positive lookaheads were not
731        being skipped when checking for a possible empty match (negative lookaheads
732        and both kinds of lookbehind were skipped).
734    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
735        inclusion of <windows.h> to before rather than after the definition of
736        INVALID_FILE_ATTRIBUTES (patch from David Byron).
738    17. Specifying a possessive quantifier with a specific limit for a Unicode
739        character property caused pcre_compile() to compile bad code, which led at
740        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
741        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
742        caused the error; without that there was no problem.
744    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
746    19. Added --enable-pcretest-libreadline.
748    20. In pcrecpp.cc, the variable 'count' was incremented twice in
749        RE::GlobalReplace(). As a result, the number of replacements returned was
750        double what it should be. I removed one of the increments, but Craig sent a
751        later patch that removed the other one (the right fix) and added unit tests
752        that check the return values (which was not done before).
754    21. Several CMake things:
756        (1) Arranged that, when cmake is used on Unix, the libraries end up with
757            the names libpcre and libpcreposix, not just pcre and pcreposix.
759        (2) The above change means that pcretest and pcregrep are now correctly
760            linked with the newly-built libraries, not previously installed ones.
764    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
765        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
766        UTF-8 newline character). The key issue is that the pattern starts .*;
767        this means that the match must be either at the beginning, or after a
768        newline. The bug was in the code for advancing after a failed match and
769        checking that the new position followed a newline. It was not taking
770        account of UTF-8 characters correctly.
772    23. PCRE was behaving differently from Perl in the way it recognized POSIX
773        character classes. PCRE was not treating the sequence [:...:] as a
774        character class unless the ... were all letters. Perl, however, seems to
775        allow any characters between [: and :], though of course it rejects as
776        unknown any "names" that contain non-letters, because all the known class
777        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
778        for example, whereas PCRE did not - it did not recognize a POSIX character
779        class. This seemed a bit dangerous, so the code has been changed to be
780        closer to Perl. The behaviour is not identical to Perl, because PCRE will
781        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
782        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
783        Perl does, and where it didn't before.
785    24. Rewrite so as to remove the single use of %n from pcregrep because in some
786        Windows environments %n is disabled by default.
789    Version 7.4 21-Sep-07
790    ---------------------
792    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
793        means that a class such as [\s] counted as "explicit reference to CR or
794        LF". That isn't really right - the whole point of the change was to try to
795        help when there was an actual mention of one of the two characters. So now
796        the change happens only if \r or \n (or a literal CR or LF) character is
797        encountered.
799    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
800        of both had grown to the point where there were only 3 bits left.
801        Fortunately, there was spare space in the data structure, and so I have
802        moved the internal flags into a new 16-bit field to free up more option
803        bits.
805    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
806        but did not set the internal JCHANGED flag - either of these is enough to
807        control the way the "get" function works - but the PCRE_INFO_JCHANGED
808        facility is supposed to tell if (?J) was ever used, so now (?J) at the
809        start sets both bits.
811    4.  Added options (at build time, compile time, exec time) to change \R from
812        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
814    5.  doc/pcresyntax.html was missing from the distribution.
816    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
817        compatibility, even though it is no longer used.
819    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
820        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
821        windows.h file is present (where different names are used). [This was
822        reversed later after testing - see 16 below.]
824    8.  Changed all #include <config.h> to #include "config.h". There were also
825        some further <pcre.h> cases that I changed to "pcre.h".
827    9.  When pcregrep was used with the --colour option, it missed the line ending
828        sequence off the lines that it output.
830    10. It was pointed out to me that arrays of string pointers cause lots of
831        relocations when a shared library is dynamically loaded. A technique of
832        using a single long string with a table of offsets can drastically reduce
833        these. I have refactored PCRE in four places to do this. The result is
834        dramatic:
836          Originally:                          290
837          After changing UCP table:            187
838          After changing error message table:   43
839          After changing table of "verbs"       36
840          After changing table of Posix names   22
842        Thanks to the folks working on Gregex for glib for this insight.
844    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
845        unicode-properties was also set.
847    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
849    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
850        checked only for CRLF.
852    14. Added casts to pcretest.c to avoid compiler warnings.
854    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
856    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
857        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
858        entirely. This removes changes made in 7 above.
860    17. The CMake files have been updated, and there is now more information about
861        building with CMake in the NON-UNIX-USE document.
864    Version 7.3 28-Aug-07
865    ---------------------
867     1. In the rejigging of the build system that eventually resulted in 7.1, the
868        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
869        brackets there is not right, since it causes compilers to look for an
870        installed pcre.h, not the version that is in the source that is being
871        compiled (which of course may be different). I have changed it back to:
873          #include "pcre.h"
875        I have a vague recollection that the change was concerned with compiling in
876        different directories, but in the new build system, that is taken care of
877        by the VPATH setting the Makefile.
879     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
880        when the subject happened to end in the byte 0x85 (e.g. if the last
881        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
882        characters but of course it shouldn't be taken as a newline when it is part
883        of another character. The bug was that, for an unlimited repeat of . in
884        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
885        characters when looking for a newline.
887     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
889     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
890        in debug output.
892     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
893        long printing in the pcrecpp unittest when running under MinGW.
895     6. ESC_K was left out of the EBCDIC table.
897     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
898        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
899        limit also applies to "virtual nesting" when a pattern is recursive, and in
900        this case 1000 isn't so big. I have been able to remove this limit at the
901        expense of backing off one optimization in certain circumstances. Normally,
902        when pcre_exec() would call its internal match() function recursively and
903        immediately return the result unconditionally, it uses a "tail recursion"
904        feature to save stack. However, when a subpattern that can match an empty
905        string has an unlimited repetition quantifier, it no longer makes this
906        optimization. That gives it a stack frame in which to save the data for
907        checking that an empty string has been matched. Previously this was taken
908        from the 1000-entry workspace that had been reserved. So now there is no
909        explicit limit, but more stack is used.
911     8. Applied Daniel's patches to solve problems with the import/export magic
912        syntax that is required for Windows, and which was going wrong for the
913        pcreposix and pcrecpp parts of the library. These were overlooked when this
914        problem was solved for the main library.
916     9. There were some crude static tests to avoid integer overflow when computing
917        the size of patterns that contain repeated groups with explicit upper
918        limits. As the maximum quantifier is 65535, the maximum group length was
919        set at 30,000 so that the product of these two numbers did not overflow a
920        32-bit integer. However, it turns out that people want to use groups that
921        are longer than 30,000 bytes (though not repeat them that many times).
922        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
923        made it possible to implement the integer overflow checks in a much more
924        dynamic way, which I have now done. The artificial limitation on group
925        length has been removed - we now have only the limit on the total length of
926        the compiled pattern, which depends on the LINK_SIZE setting.
928    10. Fixed a bug in the documentation for get/copy named substring when
929        duplicate names are permitted. If none of the named substrings are set, the
930        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
931        empty string.
933    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
934        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
935        because the ] is interpreted as the first data character and the
936        terminating ] is not found. PCRE has been made compatible with Perl in this
937        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
938        cause memory overwriting.
940    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
941        string has been matched (to stop an infinite loop). It was not recognizing
942        a conditional subpattern that could match an empty string if that
943        subpattern was within another subpattern. For example, it looped when
944        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
945        condition was not nested. This bug has been fixed.
947    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
948        past the start of the subject in the presence of bytes with the top bit
949        set, for example "\x8aBCD".
951    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
952        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
954    14. Optimized (?!) to (*FAIL).
956    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
957        This restricts code points to be within the range 0 to 0x10FFFF, excluding
958        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
959        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
960        does: it's just the validity check that is more restrictive.
962    16. Inserted checks for integer overflows during escape sequence (backslash)
963        processing, and also fixed erroneous offset values for syntax errors during
964        backslash processing.
966    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
967        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
969    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
970        caused an overrun.
972    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
973        something other than just ASCII characters) inside a group that had an
974        unlimited repeat caused a loop at compile time (while checking to see
975        whether the group could match an empty string).
977    20. Debugging a pattern containing \p or \P could cause a crash. For example,
978        [\P{Any}] did so. (Error in the code for printing property names.)
980    21. An orphan \E inside a character class could cause a crash.
982    22. A repeated capturing bracket such as (A)? could cause a wild memory
983        reference during compilation.
985    23. There are several functions in pcre_compile() that scan along a compiled
986        expression for various reasons (e.g. to see if it's fixed length for look
987        behind). There were bugs in these functions when a repeated \p or \P was
988        present in the pattern. These operators have additional parameters compared
989        with \d, etc, and these were not being taken into account when moving along
990        the compiled data. Specifically:
992        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
993            length.
995        (b) An item such as \pL+ within a repeated group could cause crashes or
996            loops.
998        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
999            "reference to non-existent subpattern" error.
1001        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
1003    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
1004        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
1006    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
1008    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
1009        character were causing crashes (broken optimization).
1011    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
1012        \p or \P) caused a compile-time loop.
1014    28. More problems have arisen in unanchored patterns when CRLF is a valid line
1015        break. For example, the unstudied pattern [\r\n]A does not match the string
1016        "\r\nA" because change 7.0/46 below moves the current point on by two
1017        characters after failing to match at the start. However, the pattern \nA
1018        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
1019        the same is true. There doesn't seem any very clean way out of this, but
1020        what I have chosen to do makes the common cases work: PCRE now takes note
1021        of whether there can be an explicit match for \r or \n anywhere in the
1022        pattern, and if so, 7.0/46 no longer applies. As part of this change,
1023        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
1024        pattern has explicit CR or LF references.
1026    29. Added (*CR) etc for changing newline setting at start of pattern.
1029    Version 7.2 19-Jun-07
1030  ---------------------  ---------------------
1032   1. If the fr_FR locale cannot be found for test 3, try the "french" locale,   1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
# Line 21  Version 7.2 01-May-07 Line 1046  Version 7.2 01-May-07
1046      stack recursion. This gives a massive performance boost under BSD, but just      stack recursion. This gives a massive performance boost under BSD, but just
1047      a small improvement under Linux. However, it saves one field in the frame      a small improvement under Linux. However, it saves one field in the frame
1048      in all cases.      in all cases.
1050   6. Added more features from the forthcoming Perl 5.10:   6. Added more features from the forthcoming Perl 5.10:
1052      (a) (?-n) (where n is a string of digits) is a relative subroutine or      (a) (?-n) (where n is a string of digits) is a relative subroutine or
1053          recursion call. It refers to the nth most recently opened parentheses.          recursion call. It refers to the nth most recently opened parentheses.
1055      (b) (?+n) is also a relative subroutine call; it refers to the nth next      (b) (?+n) is also a relative subroutine call; it refers to the nth next
1056          to be opened parentheses.          to be opened parentheses.
1058      (c) Conditions that refer to capturing parentheses can be specified      (c) Conditions that refer to capturing parentheses can be specified
1059          relatively, for example, (?(-2)... or (?(+3)...          relatively, for example, (?(-2)... or (?(+3)...
1061      (d) \K resets the start of the current match so that everything before      (d) \K resets the start of the current match so that everything before
1062          is not part of it.          is not part of it.
1064        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
1066        (f) \g{name} is another synonym - part of Perl 5.10's unification of
1067            reference syntax.
1069        (g) (?| introduces a group in which the numbering of parentheses in each
1070            alternative starts with the same number.
1072        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
1074     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
1077     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
1078        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
1079        for detecting groups that can match an empty string.
1081     9. A pattern with a very large number of alternatives (more than several
1082        hundred) was running out of internal workspace during the pre-compile
1083        phase, where pcre_compile() figures out how much memory will be needed. A
1084        bit of new cunning has reduced the workspace needed for groups with
1085        alternatives. The 1000-alternative test pattern now uses 12 bytes of
1086        workspace instead of running out of the 4096 that are available.
1088    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
1090    11. Applied patch from Google to remove an optimization that didn't quite work.
1091        The report of the bug said:
1093          pcrecpp::RE("a*").FullMatch("aaa") matches, while
1094          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
1095          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
1097    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
1098        it matched the wrong number of bytes.
1101  Version 7.1 24-Apr-07  Version 7.1 24-Apr-07

Removed from v.168  
changed lines
  Added in v.488

  ViewVC Help
Powered by ViewVC 1.1.5