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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.226  
changed lines
  Added in v.398

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12