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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.161  
changed lines
  Added in v.481

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12