ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 213 by ph10, Wed Aug 15 11:34:14 2007 UTC revision 391 by ph10, Tue Mar 17 21:16:01 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.3 09-Aug-07  Version 7.9 xx-xxx-09
5    ---------------------
7    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
8        (pcretest), all targets were linked against these libraries. This included
9        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
10        libraries. This caused unwanted dependencies to be created. This problem
11        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
12        pcretest is linked with readline.
14    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
15        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
16        moved outside it again, because FALSE and TRUE are already defined in AIX,
17        but BOOL is not.
19    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
20        PCRE_MATCH_LIMIT_RETURSION values as ints, when they should be long ints.
22    4.  The pcregrep documentation said spaces were inserted as well as colons (or
23        hyphens) following file names and line numbers when outputting matching
24        lines. This is not true; no spaces are inserted. I have also clarified the
25        wording for the --colour (or --color) option.
27    5.  In pcregrep, when --colour was used with -o, the list of matching strings
28        was not coloured; this is different to GNU grep, so I have changed it to be
29        the same.
31    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
32        each matching line was coloured. Now it goes on to look for further matches
33        of any of the test patterns, which is the same behaviour as GNU grep.
35    7.  A pattern that could match an empty string could cause pcregrep to loop; it
36        doesn't make sense to accept an empty string match in pcregrep, so I have
37        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
38        seems to be how GNU grep behaves.
40    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
41        start or after a newline", because the conditional assertion was not being
42        correctly handled. The rule now is that both the assertion and what follows
43        in the first alternative must satisfy the test.
45    9.  If auto-callout was enabled in a pattern with a conditional group, PCRE
46        could crash during matching.
48    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
49        used for matching.
51    11. Unicode property support in character classes was not working for
52        characters (bytes) greater than 127 when not in UTF-8 mode.
54    12. Added the -M command line option to pcretest.
56    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
58    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
60    16. Added comments and documentation about mis-use of no_arg in the C++
61        wrapper.
63    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
64        from Martin Jerabek that uses macro names for all relevant character and
65        string constants.
68    Version 7.8 05-Sep-08
69    ---------------------
71    1.  Replaced UCP searching code with optimized version as implemented for Ad
72        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
73        stage table and inline lookup instead of a function, giving speed ups of 2
74        to 5 times on some simple patterns that I tested. Permission was given to
75        distribute the MultiStage2.py script that generates the tables (it's not in
76        the tarball, but is in the Subversion repository).
78    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
79        scripts.
81    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
82        a group with a zero qualifier. The result of the study could be incorrect,
83        or the function might crash, depending on the pattern.
85    4.  Caseless matching was not working for non-ASCII characters in back
86        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
87        It now works when Unicode Property Support is available.
89    5.  In pcretest, an escape such as \x{de} in the data was always generating
90        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
91        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
92        truncation.
94    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
96    7.  Added two (int) casts to pcregrep when printing the difference of two
97        pointers, in case they are 64-bit values.
99    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
100        test 2 if it fails.
102    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
103        and a #define of that name to empty if it is not externally set. This is to
104        allow users of MSVC to set it if necessary.
106    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
107        the convenience functions in the pcre_get.c source file.
109    11. An option change at the start of a pattern that had top-level alternatives
110        could cause overwriting and/or a crash. This command provoked a crash in
111        some environments:
113          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
115        This potential security problem was recorded as CVE-2008-2371.
117    12. For a pattern where the match had to start at the beginning or immediately
118        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
119        pcre_dfa_exec() could read past the end of the passed subject if there was
120        no match. To help with detecting such bugs (e.g. with valgrind), I modified
121        pcretest so that it places the subject at the end of its malloc-ed buffer.
123    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
124        exec() might read past the end of the data buffer in UTF-8 mode.
126    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
127        the data contained the byte 0x85 as part of a UTF-8 character within its
128        first line. This applied both to normal and DFA matching.
130    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
131        /^[^d]*?$/8 failed to match "abc".
133    16. Added a missing copyright notice to pcrecpp_internal.h.
135    17. Make it more clear in the documentation that values returned from
136        pcre_exec() in ovector are byte offsets, not character counts.
138    18. Tidied a few places to stop certain compilers from issuing warnings.
140    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
141        supplied by Stefan Weber. I made a further small update for 7.8 because
142        there is a change of source arrangements: the pcre_searchfuncs.c module is
143        replaced by pcre_ucd.c.
146    Version 7.7 07-May-08
147    ---------------------
149    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
150        a string to a long long, pretend we don't even have a long long." This is
151        done by checking for the strtoq, strtoll, and _strtoi64 functions.
153    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
154        pre-7.6 versions, which defined a global no_arg variable instead of putting
155        it in the RE class. (See also #8 below.)
157    3.  Remove a line of dead code, identified by coverity and reported by Nuno
158        Lopes.
160    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
162        (1) The include/exclude patterns were being applied to the whole pathnames
163            of files, instead of just to the final components.
165        (2) If there was more than one level of directory, the subdirectories were
166            skipped unless they satisfied the include/exclude conditions. This is
167            inconsistent with GNU grep (and could even be seen as contrary to the
168            pcregrep specification - which I improved to make it absolutely clear).
169            The action now is always to scan all levels of directory, and just
170            apply the include/exclude patterns to regular files.
172    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
173        --exclude_dir in the tests to avoid scanning .svn directories.
175    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
176        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
177        doesn't support NULs in patterns.
179    7.  Added some missing "const"s to declarations of static tables in
180        pcre_compile.c and pcre_dfa_exec.c.
182    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
183        caused by fix #2  above. (Subsequently also a second patch to fix the
184        first patch. And a third patch - this was a messy problem.)
186    9.  Applied Craig's patch to remove the use of push_back().
188    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
189        matching function regexec().
191    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
192        which, however, unlike Perl's \g{...}, are subroutine calls, not back
193        references. PCRE supports relative numbers with this syntax (I don't think
194        Oniguruma does).
196    12. Previously, a group with a zero repeat such as (...){0} was completely
197        omitted from the compiled regex. However, this means that if the group
198        was called as a subroutine from elsewhere in the pattern, things went wrong
199        (an internal error was given). Such groups are now left in the compiled
200        pattern, with a new opcode that causes them to be skipped at execution
201        time.
203    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
204        to the way PCRE behaves:
206        (a) A lone ] character is dis-allowed (Perl treats it as data).
208        (b) A back reference to an unmatched subpattern matches an empty string
209            (Perl fails the current match path).
211        (c) A data ] in a character class must be notated as \] because if the
212            first data character in a class is ], it defines an empty class. (In
213            Perl it is not possible to have an empty class.) The empty class []
214            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
215            The negative empty class [^] matches any one character, independently
216            of the DOTALL setting.
218    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
219        non-existent subpattern following a character class starting with ']' and
220        containing () gave an internal compiling error instead of "reference to
221        non-existent subpattern". Fortunately, when the pattern did exist, the
222        compiled code was correct. (When scanning forwards to check for the
223        existencd of the subpattern, it was treating the data ']' as terminating
224        the class, so got the count wrong. When actually compiling, the reference
225        was subsequently set up correctly.)
227    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
228        it was being rejected as not supported by pcre_dfa_exec(), even though
229        other assertions are supported. I have made pcre_dfa_exec() support
230        (*FAIL).
232    16. The implementation of 13c above involved the invention of a new opcode,
233        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
234        cannot be changed at match time, I realized I could make a small
235        improvement to matching performance by compiling OP_ALLANY instead of
236        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
237        on the OP_ANY path.
239    17. Compiling pcretest on Windows with readline support failed without the
240        following two fixes: (1) Make the unistd.h include conditional on
241        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
243    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
244        ncurses library to be included for pcretest when ReadLine support is
245        requested, but also to allow for it to be overridden. This patch came from
246        Daniel Bergström.
248    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
249        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
250        any errors with the current Unicode tables. Thanks to Peter Kankowski for
251        spotting this.
254    Version 7.6 28-Jan-08
255    ---------------------
257    1.  A character class containing a very large number of characters with
258        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
259        overflow.
261    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
262        HAVE_LONG_LONG is not defined.
264    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
265        bring them up to date and include new features. This patch includes:
267        - Fixed PH's badly added libz and libbz2 support.
268        - Fixed a problem with static linking.
269        - Added pcredemo. [But later removed - see 7 below.]
270        - Fixed dftables problem and added an option.
271        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
272            HAVE_LONG_LONG.
273        - Added readline support for pcretest.
274        - Added an listing of the option settings after cmake has run.
276    4.  A user submitted a patch to Makefile that makes it easy to create
277        "pcre.dll" under mingw when using Configure/Make. I added stuff to
278        Makefile.am that cause it to include this special target, without
279        affecting anything else. Note that the same mingw target plus all
280        the other distribution libraries and programs are now supported
281        when configuring with CMake (see 6 below) instead of with
282        Configure/Make.
284    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
285        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
286        exported in the Windows port". It has not yet been confirmed that the patch
287        solves the problem, but it does no harm.
289    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
290        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
291        with CMake, and also correct the comment about stack recursion.
293    7.  Remove the automatic building of pcredemo from the ./configure system and
294        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
295        of a program that users should build themselves after PCRE is installed, so
296        building it automatically is not really right. What is more, it gave
297        trouble in some build environments.
299    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
302    Version 7.5 10-Jan-08
303    ---------------------
305    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
306        values in parens when parsing an RE using the C++ wrapper."
308    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
309        Characters greater than 255 were excluded from the class instead of being
310        included.
312    3.  The same bug as (2) above applied to negated POSIX classes such as
313        [:^space:].
315    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
316        defined or documented. It seems to have been a typo for PCRE_STATIC, so
317        I have changed it.
319    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
320        first named subpattern) and a construct such as (?&a) would reference the
321        first named subpattern whose name started with "a" (in other words, the
322        length check was missing). Both these problems are fixed. "Subpattern name
323        expected" is now given for (?&) (a zero-length name), and this patch also
324        makes it give the same error for \k'' (previously it complained that that
325        was a reference to a non-existent subpattern).
327    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
328        this is right because (?- can be followed by option settings as well as by
329        digits. I have, however, made the messages clearer.
331    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
332        than the number used in the conditional) now cause a compile-time error.
333        This is actually not compatible with Perl, which accepts such patterns, but
334        treats the conditional as always being FALSE (as PCRE used to), but it
335        seems to me that giving a diagnostic is better.
337    8.  Change "alphameric" to the more common word "alphanumeric" in comments
338        and messages.
340    9.  Fix two occurrences of "backslash" in comments that should have been
341        "backspace".
343    10. Remove two redundant lines of code that can never be obeyed (their function
344        was moved elsewhere).
346    11. The program that makes PCRE's Unicode character property table had a bug
347        which caused it to generate incorrect table entries for sequences of
348        characters that have the same character type, but are in different scripts.
349        It amalgamated them into a single range, with the script of the first of
350        them. In other words, some characters were in the wrong script. There were
351        thirteen such cases, affecting characters in the following ranges:
353          U+002b0 - U+002c1
354          U+0060c - U+0060d
355          U+0061e - U+00612
356          U+0064b - U+0065e
357          U+0074d - U+0076d
358          U+01800 - U+01805
359          U+01d00 - U+01d77
360          U+01d9b - U+01dbf
361          U+0200b - U+0200f
362          U+030fc - U+030fe
363          U+03260 - U+0327f
364          U+0fb46 - U+0fbb1
365          U+10450 - U+1049d
367    12. The -o option (show only the matching part of a line) for pcregrep was not
368        compatible with GNU grep in that, if there was more than one match in a
369        line, it showed only the first of them. It now behaves in the same way as
370        GNU grep.
372    13. If the -o and -v options were combined for pcregrep, it printed a blank
373        line for every non-matching line. GNU grep prints nothing, and pcregrep now
374        does the same. The return code can be used to tell if there were any
375        non-matching lines.
377    14. Added --file-offsets and --line-offsets to pcregrep.
379    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
380        infinitely looping recursion. The bug was that positive lookaheads were not
381        being skipped when checking for a possible empty match (negative lookaheads
382        and both kinds of lookbehind were skipped).
384    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
385        inclusion of <windows.h> to before rather than after the definition of
386        INVALID_FILE_ATTRIBUTES (patch from David Byron).
388    17. Specifying a possessive quantifier with a specific limit for a Unicode
389        character property caused pcre_compile() to compile bad code, which led at
390        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
391        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
392        caused the error; without that there was no problem.
394    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
396    19. Added --enable-pcretest-libreadline.
398    20. In pcrecpp.cc, the variable 'count' was incremented twice in
399        RE::GlobalReplace(). As a result, the number of replacements returned was
400        double what it should be. I removed one of the increments, but Craig sent a
401        later patch that removed the other one (the right fix) and added unit tests
402        that check the return values (which was not done before).
404    21. Several CMake things:
406        (1) Arranged that, when cmake is used on Unix, the libraries end up with
407            the names libpcre and libpcreposix, not just pcre and pcreposix.
409        (2) The above change means that pcretest and pcregrep are now correctly
410            linked with the newly-built libraries, not previously installed ones.
414    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
415        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
416        UTF-8 newline character). The key issue is that the pattern starts .*;
417        this means that the match must be either at the beginning, or after a
418        newline. The bug was in the code for advancing after a failed match and
419        checking that the new position followed a newline. It was not taking
420        account of UTF-8 characters correctly.
422    23. PCRE was behaving differently from Perl in the way it recognized POSIX
423        character classes. PCRE was not treating the sequence [:...:] as a
424        character class unless the ... were all letters. Perl, however, seems to
425        allow any characters between [: and :], though of course it rejects as
426        unknown any "names" that contain non-letters, because all the known class
427        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
428        for example, whereas PCRE did not - it did not recognize a POSIX character
429        class. This seemed a bit dangerous, so the code has been changed to be
430        closer to Perl. The behaviour is not identical to Perl, because PCRE will
431        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
432        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
433        Perl does, and where it didn't before.
435    24. Rewrite so as to remove the single use of %n from pcregrep because in some
436        Windows environments %n is disabled by default.
439    Version 7.4 21-Sep-07
440    ---------------------
442    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
443        means that a class such as [\s] counted as "explicit reference to CR or
444        LF". That isn't really right - the whole point of the change was to try to
445        help when there was an actual mention of one of the two characters. So now
446        the change happens only if \r or \n (or a literal CR or LF) character is
447        encountered.
449    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
450        of both had grown to the point where there were only 3 bits left.
451        Fortunately, there was spare space in the data structure, and so I have
452        moved the internal flags into a new 16-bit field to free up more option
453        bits.
455    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
456        but did not set the internal JCHANGED flag - either of these is enough to
457        control the way the "get" function works - but the PCRE_INFO_JCHANGED
458        facility is supposed to tell if (?J) was ever used, so now (?J) at the
459        start sets both bits.
461    4.  Added options (at build time, compile time, exec time) to change \R from
462        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
464    5.  doc/pcresyntax.html was missing from the distribution.
466    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
467        compatibility, even though it is no longer used.
469    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
470        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
471        windows.h file is present (where different names are used). [This was
472        reversed later after testing - see 16 below.]
474    8.  Changed all #include <config.h> to #include "config.h". There were also
475        some further <pcre.h> cases that I changed to "pcre.h".
477    9.  When pcregrep was used with the --colour option, it missed the line ending
478        sequence off the lines that it output.
480    10. It was pointed out to me that arrays of string pointers cause lots of
481        relocations when a shared library is dynamically loaded. A technique of
482        using a single long string with a table of offsets can drastically reduce
483        these. I have refactored PCRE in four places to do this. The result is
484        dramatic:
486          Originally:                          290
487          After changing UCP table:            187
488          After changing error message table:   43
489          After changing table of "verbs"       36
490          After changing table of Posix names   22
492        Thanks to the folks working on Gregex for glib for this insight.
494    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
495        unicode-properties was also set.
497    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
499    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
500        checked only for CRLF.
502    14. Added casts to pcretest.c to avoid compiler warnings.
504    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
506    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
507        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
508        entirely. This removes changes made in 7 above.
510    17. The CMake files have been updated, and there is now more information about
511        building with CMake in the NON-UNIX-USE document.
514    Version 7.3 28-Aug-07
515  ---------------------  ---------------------
517   1. In the rejigging of the build system that eventually resulted in 7.1, the   1. In the rejigging of the build system that eventually resulted in 7.1, the
# Line 98  Version 7.3 09-Aug-07 Line 608  Version 7.3 09-Aug-07
608      the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the      the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
609      full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still      full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
610      does: it's just the validity check that is more restrictive.      does: it's just the validity check that is more restrictive.
612  16. Inserted checks for integer overflows during escape sequence (backslash)  16. Inserted checks for integer overflows during escape sequence (backslash)
613      processing, and also fixed erroneous offset values for syntax errors during      processing, and also fixed erroneous offset values for syntax errors during
614      backslash processing.      backslash processing.
616    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
617        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
619    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
620        caused an overrun.
622    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
623        something other than just ASCII characters) inside a group that had an
624        unlimited repeat caused a loop at compile time (while checking to see
625        whether the group could match an empty string).
627    20. Debugging a pattern containing \p or \P could cause a crash. For example,
628        [\P{Any}] did so. (Error in the code for printing property names.)
630    21. An orphan \E inside a character class could cause a crash.
632    22. A repeated capturing bracket such as (A)? could cause a wild memory
633        reference during compilation.
635    23. There are several functions in pcre_compile() that scan along a compiled
636        expression for various reasons (e.g. to see if it's fixed length for look
637        behind). There were bugs in these functions when a repeated \p or \P was
638        present in the pattern. These operators have additional parameters compared
639        with \d, etc, and these were not being taken into account when moving along
640        the compiled data. Specifically:
642        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
643            length.
645        (b) An item such as \pL+ within a repeated group could cause crashes or
646            loops.
648        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
649            "reference to non-existent subpattern" error.
651        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
653    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
654        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
656    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
658    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
659        character were causing crashes (broken optimization).
661    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
662        \p or \P) caused a compile-time loop.
664    28. More problems have arisen in unanchored patterns when CRLF is a valid line
665        break. For example, the unstudied pattern [\r\n]A does not match the string
666        "\r\nA" because change 7.0/46 below moves the current point on by two
667        characters after failing to match at the start. However, the pattern \nA
668        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
669        the same is true. There doesn't seem any very clean way out of this, but
670        what I have chosen to do makes the common cases work: PCRE now takes note
671        of whether there can be an explicit match for \r or \n anywhere in the
672        pattern, and if so, 7.0/46 no longer applies. As part of this change,
673        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
674        pattern has explicit CR or LF references.
676    29. Added (*CR) etc for changing newline setting at start of pattern.
679  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07

Removed from v.213  
changed lines
  Added in v.391

  ViewVC Help
Powered by ViewVC 1.1.5