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

Diff of /code/trunk/ChangeLog

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

revision 195 by ph10, Mon Jul 30 13:23:28 2007 UTC revision 393 by ph10, Tue Mar 17 21:47:54 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 05-Jul-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.
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    
73    Version 7.8 05-Sep-08
74    ---------------------
75    
76    1.  Replaced UCP searching code with optimized version as implemented for Ad
77        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
78        stage table and inline lookup instead of a function, giving speed ups of 2
79        to 5 times on some simple patterns that I tested. Permission was given to
80        distribute the MultiStage2.py script that generates the tables (it's not in
81        the tarball, but is in the Subversion repository).
82    
83    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
84        scripts.
85    
86    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
87        a group with a zero qualifier. The result of the study could be incorrect,
88        or the function might crash, depending on the pattern.
89    
90    4.  Caseless matching was not working for non-ASCII characters in back
91        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
92        It now works when Unicode Property Support is available.
93    
94    5.  In pcretest, an escape such as \x{de} in the data was always generating
95        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
96        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
97        truncation.
98    
99    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
100    
101    7.  Added two (int) casts to pcregrep when printing the difference of two
102        pointers, in case they are 64-bit values.
103    
104    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
105        test 2 if it fails.
106    
107    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
108        and a #define of that name to empty if it is not externally set. This is to
109        allow users of MSVC to set it if necessary.
110    
111    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
112        the convenience functions in the pcre_get.c source file.
113    
114    11. An option change at the start of a pattern that had top-level alternatives
115        could cause overwriting and/or a crash. This command provoked a crash in
116        some environments:
117    
118          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
119    
120        This potential security problem was recorded as CVE-2008-2371.
121    
122    12. For a pattern where the match had to start at the beginning or immediately
123        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
124        pcre_dfa_exec() could read past the end of the passed subject if there was
125        no match. To help with detecting such bugs (e.g. with valgrind), I modified
126        pcretest so that it places the subject at the end of its malloc-ed buffer.
127    
128    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
129        exec() might read past the end of the data buffer in UTF-8 mode.
130    
131    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
132        the data contained the byte 0x85 as part of a UTF-8 character within its
133        first line. This applied both to normal and DFA matching.
134    
135    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
136        /^[^d]*?$/8 failed to match "abc".
137    
138    16. Added a missing copyright notice to pcrecpp_internal.h.
139    
140    17. Make it more clear in the documentation that values returned from
141        pcre_exec() in ovector are byte offsets, not character counts.
142    
143    18. Tidied a few places to stop certain compilers from issuing warnings.
144    
145    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
146        supplied by Stefan Weber. I made a further small update for 7.8 because
147        there is a change of source arrangements: the pcre_searchfuncs.c module is
148        replaced by pcre_ucd.c.
149    
150    
151    Version 7.7 07-May-08
152    ---------------------
153    
154    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
155        a string to a long long, pretend we don't even have a long long." This is
156        done by checking for the strtoq, strtoll, and _strtoi64 functions.
157    
158    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
159        pre-7.6 versions, which defined a global no_arg variable instead of putting
160        it in the RE class. (See also #8 below.)
161    
162    3.  Remove a line of dead code, identified by coverity and reported by Nuno
163        Lopes.
164    
165    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
166    
167        (1) The include/exclude patterns were being applied to the whole pathnames
168            of files, instead of just to the final components.
169    
170        (2) If there was more than one level of directory, the subdirectories were
171            skipped unless they satisfied the include/exclude conditions. This is
172            inconsistent with GNU grep (and could even be seen as contrary to the
173            pcregrep specification - which I improved to make it absolutely clear).
174            The action now is always to scan all levels of directory, and just
175            apply the include/exclude patterns to regular files.
176    
177    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
178        --exclude_dir in the tests to avoid scanning .svn directories.
179    
180    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
181        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
182        doesn't support NULs in patterns.
183    
184    7.  Added some missing "const"s to declarations of static tables in
185        pcre_compile.c and pcre_dfa_exec.c.
186    
187    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
188        caused by fix #2  above. (Subsequently also a second patch to fix the
189        first patch. And a third patch - this was a messy problem.)
190    
191    9.  Applied Craig's patch to remove the use of push_back().
192    
193    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
194        matching function regexec().
195    
196    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
197        which, however, unlike Perl's \g{...}, are subroutine calls, not back
198        references. PCRE supports relative numbers with this syntax (I don't think
199        Oniguruma does).
200    
201    12. Previously, a group with a zero repeat such as (...){0} was completely
202        omitted from the compiled regex. However, this means that if the group
203        was called as a subroutine from elsewhere in the pattern, things went wrong
204        (an internal error was given). Such groups are now left in the compiled
205        pattern, with a new opcode that causes them to be skipped at execution
206        time.
207    
208    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
209        to the way PCRE behaves:
210    
211        (a) A lone ] character is dis-allowed (Perl treats it as data).
212    
213        (b) A back reference to an unmatched subpattern matches an empty string
214            (Perl fails the current match path).
215    
216        (c) A data ] in a character class must be notated as \] because if the
217            first data character in a class is ], it defines an empty class. (In
218            Perl it is not possible to have an empty class.) The empty class []
219            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
220            The negative empty class [^] matches any one character, independently
221            of the DOTALL setting.
222    
223    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
224        non-existent subpattern following a character class starting with ']' and
225        containing () gave an internal compiling error instead of "reference to
226        non-existent subpattern". Fortunately, when the pattern did exist, the
227        compiled code was correct. (When scanning forwards to check for the
228        existencd of the subpattern, it was treating the data ']' as terminating
229        the class, so got the count wrong. When actually compiling, the reference
230        was subsequently set up correctly.)
231    
232    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
233        it was being rejected as not supported by pcre_dfa_exec(), even though
234        other assertions are supported. I have made pcre_dfa_exec() support
235        (*FAIL).
236    
237    16. The implementation of 13c above involved the invention of a new opcode,
238        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
239        cannot be changed at match time, I realized I could make a small
240        improvement to matching performance by compiling OP_ALLANY instead of
241        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
242        on the OP_ANY path.
243    
244    17. Compiling pcretest on Windows with readline support failed without the
245        following two fixes: (1) Make the unistd.h include conditional on
246        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
247    
248    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
249        ncurses library to be included for pcretest when ReadLine support is
250        requested, but also to allow for it to be overridden. This patch came from
251        Daniel Bergström.
252    
253    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
254        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
255        any errors with the current Unicode tables. Thanks to Peter Kankowski for
256        spotting this.
257    
258    
259    Version 7.6 28-Jan-08
260    ---------------------
261    
262    1.  A character class containing a very large number of characters with
263        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
264        overflow.
265    
266    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
267        HAVE_LONG_LONG is not defined.
268    
269    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
270        bring them up to date and include new features. This patch includes:
271    
272        - Fixed PH's badly added libz and libbz2 support.
273        - Fixed a problem with static linking.
274        - Added pcredemo. [But later removed - see 7 below.]
275        - Fixed dftables problem and added an option.
276        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
277            HAVE_LONG_LONG.
278        - Added readline support for pcretest.
279        - Added an listing of the option settings after cmake has run.
280    
281    4.  A user submitted a patch to Makefile that makes it easy to create
282        "pcre.dll" under mingw when using Configure/Make. I added stuff to
283        Makefile.am that cause it to include this special target, without
284        affecting anything else. Note that the same mingw target plus all
285        the other distribution libraries and programs are now supported
286        when configuring with CMake (see 6 below) instead of with
287        Configure/Make.
288    
289    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
290        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
291        exported in the Windows port". It has not yet been confirmed that the patch
292        solves the problem, but it does no harm.
293    
294    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
295        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
296        with CMake, and also correct the comment about stack recursion.
297    
298    7.  Remove the automatic building of pcredemo from the ./configure system and
299        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
300        of a program that users should build themselves after PCRE is installed, so
301        building it automatically is not really right. What is more, it gave
302        trouble in some build environments.
303    
304    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
305    
306    
307    Version 7.5 10-Jan-08
308    ---------------------
309    
310    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
311        values in parens when parsing an RE using the C++ wrapper."
312    
313    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
314        Characters greater than 255 were excluded from the class instead of being
315        included.
316    
317    3.  The same bug as (2) above applied to negated POSIX classes such as
318        [:^space:].
319    
320    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
321        defined or documented. It seems to have been a typo for PCRE_STATIC, so
322        I have changed it.
323    
324    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
325        first named subpattern) and a construct such as (?&a) would reference the
326        first named subpattern whose name started with "a" (in other words, the
327        length check was missing). Both these problems are fixed. "Subpattern name
328        expected" is now given for (?&) (a zero-length name), and this patch also
329        makes it give the same error for \k'' (previously it complained that that
330        was a reference to a non-existent subpattern).
331    
332    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
333        this is right because (?- can be followed by option settings as well as by
334        digits. I have, however, made the messages clearer.
335    
336    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
337        than the number used in the conditional) now cause a compile-time error.
338        This is actually not compatible with Perl, which accepts such patterns, but
339        treats the conditional as always being FALSE (as PCRE used to), but it
340        seems to me that giving a diagnostic is better.
341    
342    8.  Change "alphameric" to the more common word "alphanumeric" in comments
343        and messages.
344    
345    9.  Fix two occurrences of "backslash" in comments that should have been
346        "backspace".
347    
348    10. Remove two redundant lines of code that can never be obeyed (their function
349        was moved elsewhere).
350    
351    11. The program that makes PCRE's Unicode character property table had a bug
352        which caused it to generate incorrect table entries for sequences of
353        characters that have the same character type, but are in different scripts.
354        It amalgamated them into a single range, with the script of the first of
355        them. In other words, some characters were in the wrong script. There were
356        thirteen such cases, affecting characters in the following ranges:
357    
358          U+002b0 - U+002c1
359          U+0060c - U+0060d
360          U+0061e - U+00612
361          U+0064b - U+0065e
362          U+0074d - U+0076d
363          U+01800 - U+01805
364          U+01d00 - U+01d77
365          U+01d9b - U+01dbf
366          U+0200b - U+0200f
367          U+030fc - U+030fe
368          U+03260 - U+0327f
369          U+0fb46 - U+0fbb1
370          U+10450 - U+1049d
371    
372    12. The -o option (show only the matching part of a line) for pcregrep was not
373        compatible with GNU grep in that, if there was more than one match in a
374        line, it showed only the first of them. It now behaves in the same way as
375        GNU grep.
376    
377    13. If the -o and -v options were combined for pcregrep, it printed a blank
378        line for every non-matching line. GNU grep prints nothing, and pcregrep now
379        does the same. The return code can be used to tell if there were any
380        non-matching lines.
381    
382    14. Added --file-offsets and --line-offsets to pcregrep.
383    
384    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
385        infinitely looping recursion. The bug was that positive lookaheads were not
386        being skipped when checking for a possible empty match (negative lookaheads
387        and both kinds of lookbehind were skipped).
388    
389    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
390        inclusion of <windows.h> to before rather than after the definition of
391        INVALID_FILE_ATTRIBUTES (patch from David Byron).
392    
393    17. Specifying a possessive quantifier with a specific limit for a Unicode
394        character property caused pcre_compile() to compile bad code, which led at
395        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
396        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
397        caused the error; without that there was no problem.
398    
399    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
400    
401    19. Added --enable-pcretest-libreadline.
402    
403    20. In pcrecpp.cc, the variable 'count' was incremented twice in
404        RE::GlobalReplace(). As a result, the number of replacements returned was
405        double what it should be. I removed one of the increments, but Craig sent a
406        later patch that removed the other one (the right fix) and added unit tests
407        that check the return values (which was not done before).
408    
409    21. Several CMake things:
410    
411        (1) Arranged that, when cmake is used on Unix, the libraries end up with
412            the names libpcre and libpcreposix, not just pcre and pcreposix.
413    
414        (2) The above change means that pcretest and pcregrep are now correctly
415            linked with the newly-built libraries, not previously installed ones.
416    
417        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
418    
419    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
420        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
421        UTF-8 newline character). The key issue is that the pattern starts .*;
422        this means that the match must be either at the beginning, or after a
423        newline. The bug was in the code for advancing after a failed match and
424        checking that the new position followed a newline. It was not taking
425        account of UTF-8 characters correctly.
426    
427    23. PCRE was behaving differently from Perl in the way it recognized POSIX
428        character classes. PCRE was not treating the sequence [:...:] as a
429        character class unless the ... were all letters. Perl, however, seems to
430        allow any characters between [: and :], though of course it rejects as
431        unknown any "names" that contain non-letters, because all the known class
432        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
433        for example, whereas PCRE did not - it did not recognize a POSIX character
434        class. This seemed a bit dangerous, so the code has been changed to be
435        closer to Perl. The behaviour is not identical to Perl, because PCRE will
436        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
437        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
438        Perl does, and where it didn't before.
439    
440    24. Rewrite so as to remove the single use of %n from pcregrep because in some
441        Windows environments %n is disabled by default.
442    
443    
444    Version 7.4 21-Sep-07
445    ---------------------
446    
447    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
448        means that a class such as [\s] counted as "explicit reference to CR or
449        LF". That isn't really right - the whole point of the change was to try to
450        help when there was an actual mention of one of the two characters. So now
451        the change happens only if \r or \n (or a literal CR or LF) character is
452        encountered.
453    
454    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
455        of both had grown to the point where there were only 3 bits left.
456        Fortunately, there was spare space in the data structure, and so I have
457        moved the internal flags into a new 16-bit field to free up more option
458        bits.
459    
460    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
461        but did not set the internal JCHANGED flag - either of these is enough to
462        control the way the "get" function works - but the PCRE_INFO_JCHANGED
463        facility is supposed to tell if (?J) was ever used, so now (?J) at the
464        start sets both bits.
465    
466    4.  Added options (at build time, compile time, exec time) to change \R from
467        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
468    
469    5.  doc/pcresyntax.html was missing from the distribution.
470    
471    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
472        compatibility, even though it is no longer used.
473    
474    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
475        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
476        windows.h file is present (where different names are used). [This was
477        reversed later after testing - see 16 below.]
478    
479    8.  Changed all #include <config.h> to #include "config.h". There were also
480        some further <pcre.h> cases that I changed to "pcre.h".
481    
482    9.  When pcregrep was used with the --colour option, it missed the line ending
483        sequence off the lines that it output.
484    
485    10. It was pointed out to me that arrays of string pointers cause lots of
486        relocations when a shared library is dynamically loaded. A technique of
487        using a single long string with a table of offsets can drastically reduce
488        these. I have refactored PCRE in four places to do this. The result is
489        dramatic:
490    
491          Originally:                          290
492          After changing UCP table:            187
493          After changing error message table:   43
494          After changing table of "verbs"       36
495          After changing table of Posix names   22
496    
497        Thanks to the folks working on Gregex for glib for this insight.
498    
499    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
500        unicode-properties was also set.
501    
502    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
503    
504    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
505        checked only for CRLF.
506    
507    14. Added casts to pcretest.c to avoid compiler warnings.
508    
509    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
510    
511    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
512        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
513        entirely. This removes changes made in 7 above.
514    
515    17. The CMake files have been updated, and there is now more information about
516        building with CMake in the NON-UNIX-USE document.
517    
518    
519    Version 7.3 28-Aug-07
520  ---------------------  ---------------------
521    
522   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 9  Version 7.3 05-Jul-07 Line 524  Version 7.3 05-Jul-07
524      brackets there is not right, since it causes compilers to look for an      brackets there is not right, since it causes compilers to look for an
525      installed pcre.h, not the version that is in the source that is being      installed pcre.h, not the version that is in the source that is being
526      compiled (which of course may be different). I have changed it back to:      compiled (which of course may be different). I have changed it back to:
527    
528        #include "pcre.h"        #include "pcre.h"
529    
530      I have a vague recollection that the change was concerned with compiling in      I have a vague recollection that the change was concerned with compiling in
531      different directories, but in the new build system, that is taken care of      different directories, but in the new build system, that is taken care of
532      by the VPATH setting the Makefile.      by the VPATH setting the Makefile.
533    
534   2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed   2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
535      when the subject happened to end in the byte 0x85 (e.g. if the last      when the subject happened to end in the byte 0x85 (e.g. if the last
536      character was \x{1ec5}). *Character* 0x85 is one of the "any" newline      character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
# Line 23  Version 7.3 05-Jul-07 Line 538  Version 7.3 05-Jul-07
538      of another character. The bug was that, for an unlimited repeat of . in      of another character. The bug was that, for an unlimited repeat of . in
539      not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by      not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
540      characters when looking for a newline.      characters when looking for a newline.
   
  3. A small performance improvement in the DOTALL UTF-8 mode .* case.  
   
  4. Debugging: adjusted the names of opcodes for different kinds of parentheses  
     in debug output.  
   
  5. Arrange to use "%I64d" instead of "%lld" for long printing in the pcrecpp  
     unittest when running under MinGW.  
   
  6. ESC_K was left out of the EBCDIC table.  
541    
542     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
543    
544     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
545        in debug output.
546    
547     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
548        long printing in the pcrecpp unittest when running under MinGW.
549    
550     6. ESC_K was left out of the EBCDIC table.
551    
552     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
553        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
554        limit also applies to "virtual nesting" when a pattern is recursive, and in
555        this case 1000 isn't so big. I have been able to remove this limit at the
556        expense of backing off one optimization in certain circumstances. Normally,
557        when pcre_exec() would call its internal match() function recursively and
558        immediately return the result unconditionally, it uses a "tail recursion"
559        feature to save stack. However, when a subpattern that can match an empty
560        string has an unlimited repetition quantifier, it no longer makes this
561        optimization. That gives it a stack frame in which to save the data for
562        checking that an empty string has been matched. Previously this was taken
563        from the 1000-entry workspace that had been reserved. So now there is no
564        explicit limit, but more stack is used.
565    
566     8. Applied Daniel's patches to solve problems with the import/export magic
567        syntax that is required for Windows, and which was going wrong for the
568        pcreposix and pcrecpp parts of the library. These were overlooked when this
569        problem was solved for the main library.
570    
571     9. There were some crude static tests to avoid integer overflow when computing
572        the size of patterns that contain repeated groups with explicit upper
573        limits. As the maximum quantifier is 65535, the maximum group length was
574        set at 30,000 so that the product of these two numbers did not overflow a
575        32-bit integer. However, it turns out that people want to use groups that
576        are longer than 30,000 bytes (though not repeat them that many times).
577        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
578        made it possible to implement the integer overflow checks in a much more
579        dynamic way, which I have now done. The artificial limitation on group
580        length has been removed - we now have only the limit on the total length of
581        the compiled pattern, which depends on the LINK_SIZE setting.
582    
583    10. Fixed a bug in the documentation for get/copy named substring when
584        duplicate names are permitted. If none of the named substrings are set, the
585        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
586        empty string.
587    
588    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
589        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
590        because the ] is interpreted as the first data character and the
591        terminating ] is not found. PCRE has been made compatible with Perl in this
592        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
593        cause memory overwriting.
594    
595    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
596        string has been matched (to stop an infinite loop). It was not recognizing
597        a conditional subpattern that could match an empty string if that
598        subpattern was within another subpattern. For example, it looped when
599        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
600        condition was not nested. This bug has been fixed.
601    
602    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
603        past the start of the subject in the presence of bytes with the top bit
604        set, for example "\x8aBCD".
605    
606    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
607        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
608    
609    14. Optimized (?!) to (*FAIL).
610    
611    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
612        This restricts code points to be within the range 0 to 0x10FFFF, excluding
613        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
614        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
615        does: it's just the validity check that is more restrictive.
616    
617    16. Inserted checks for integer overflows during escape sequence (backslash)
618        processing, and also fixed erroneous offset values for syntax errors during
619        backslash processing.
620    
621    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
622        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
623    
624    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
625        caused an overrun.
626    
627    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
628        something other than just ASCII characters) inside a group that had an
629        unlimited repeat caused a loop at compile time (while checking to see
630        whether the group could match an empty string).
631    
632    20. Debugging a pattern containing \p or \P could cause a crash. For example,
633        [\P{Any}] did so. (Error in the code for printing property names.)
634    
635    21. An orphan \E inside a character class could cause a crash.
636    
637    22. A repeated capturing bracket such as (A)? could cause a wild memory
638        reference during compilation.
639    
640    23. There are several functions in pcre_compile() that scan along a compiled
641        expression for various reasons (e.g. to see if it's fixed length for look
642        behind). There were bugs in these functions when a repeated \p or \P was
643        present in the pattern. These operators have additional parameters compared
644        with \d, etc, and these were not being taken into account when moving along
645        the compiled data. Specifically:
646    
647        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
648            length.
649    
650        (b) An item such as \pL+ within a repeated group could cause crashes or
651            loops.
652    
653        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
654            "reference to non-existent subpattern" error.
655    
656        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
657    
658    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
659        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
660    
661    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
662    
663    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
664        character were causing crashes (broken optimization).
665    
666    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
667        \p or \P) caused a compile-time loop.
668    
669    28. More problems have arisen in unanchored patterns when CRLF is a valid line
670        break. For example, the unstudied pattern [\r\n]A does not match the string
671        "\r\nA" because change 7.0/46 below moves the current point on by two
672        characters after failing to match at the start. However, the pattern \nA
673        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
674        the same is true. There doesn't seem any very clean way out of this, but
675        what I have chosen to do makes the common cases work: PCRE now takes note
676        of whether there can be an explicit match for \r or \n anywhere in the
677        pattern, and if so, 7.0/46 no longer applies. As part of this change,
678        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
679        pattern has explicit CR or LF references.
680    
681    29. Added (*CR) etc for changing newline setting at start of pattern.
682    
683    
684  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07

Legend:
Removed from v.195  
changed lines
  Added in v.393

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12