ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 185 by ph10, Tue Jun 19 13:39:46 2007 UTC revision 327 by ph10, Sat Mar 8 19:38:30 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.2 19-June-07  Version 7.7 05-Mar-08
5    ---------------------
7    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
8        a string to a long long, pretend we don't even have a long long." This is
9        done by checking for the strtoq, strtoll, and _strtoi64 functions.
11    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
12        pre-7.6 versions, which defined a global no_arg variable instead of putting
13        it in the RE class.
15    3.  Remove a line of dead code, identified by coverity and reported by Nuno
16        Lopes.
18    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
20        (1) The include/exclude patterns were being applied to the whole pathnames
21            of files, instead of just to the final components.
23        (2) If there was more than one level of directory, the subdirectories were
24            skipped unless they satisfied the include/exclude conditions. This is
25            inconsistent with GNU grep (and could even be seen as contrary to the
26            pcregrep specification - which I improved to make it absolutely clear).
27            The action now is always to scan all levels of directory, and just
28            apply the include/exclude patterns to regular files.
30    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
31        --exclude_dir in the tests to avoid scanning .svn directories.
33    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
34        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
35        doesn't support NULs in patterns.
37    7.  Added some missing "const"s to declarations of static tables in
38        pcre_compile.c and pcre_dfa_exec.c.
41    Version 7.6 28-Jan-08
42    ---------------------
44    1.  A character class containing a very large number of characters with
45        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
46        overflow.
48    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
49        HAVE_LONG_LONG is not defined.
51    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
52        bring them up to date and include new features. This patch includes:
54        - Fixed PH's badly added libz and libbz2 support.
55        - Fixed a problem with static linking.
56        - Added pcredemo. [But later removed - see 7 below.]
57        - Fixed dftables problem and added an option.
58        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
59            HAVE_LONG_LONG.
60        - Added readline support for pcretest.
61        - Added an listing of the option settings after cmake has run.
63    4.  A user submitted a patch to Makefile that makes it easy to create
64        "pcre.dll" under mingw when using Configure/Make. I added stuff to
65        Makefile.am that cause it to include this special target, without
66        affecting anything else. Note that the same mingw target plus all
67        the other distribution libraries and programs are now supported
68        when configuring with CMake (see 6 below) instead of with
69        Configure/Make.
71    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
72        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
73        exported in the Windows port". It has not yet been confirmed that the patch
74        solves the problem, but it does no harm.
76    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
77        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
78        with CMake, and also correct the comment about stack recursion.
80    7.  Remove the automatic building of pcredemo from the ./configure system and
81        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
82        of a program that users should build themselves after PCRE is installed, so
83        building it automatically is not really right. What is more, it gave
84        trouble in some build environments.
86    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
89    Version 7.5 10-Jan-08
90    ---------------------
92    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
93        values in parens when parsing an RE using the C++ wrapper."
95    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
96        Characters greater than 255 were excluded from the class instead of being
97        included.
99    3.  The same bug as (2) above applied to negated POSIX classes such as
100        [:^space:].
102    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
103        defined or documented. It seems to have been a typo for PCRE_STATIC, so
104        I have changed it.
106    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
107        first named subpattern) and a construct such as (?&a) would reference the
108        first named subpattern whose name started with "a" (in other words, the
109        length check was missing). Both these problems are fixed. "Subpattern name
110        expected" is now given for (?&) (a zero-length name), and this patch also
111        makes it give the same error for \k'' (previously it complained that that
112        was a reference to a non-existent subpattern).
114    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
115        this is right because (?- can be followed by option settings as well as by
116        digits. I have, however, made the messages clearer.
118    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
119        than the number used in the conditional) now cause a compile-time error.
120        This is actually not compatible with Perl, which accepts such patterns, but
121        treats the conditional as always being FALSE (as PCRE used to), but it
122        seems to me that giving a diagnostic is better.
124    8.  Change "alphameric" to the more common word "alphanumeric" in comments
125        and messages.
127    9.  Fix two occurrences of "backslash" in comments that should have been
128        "backspace".
130    10. Remove two redundant lines of code that can never be obeyed (their function
131        was moved elsewhere).
133    11. The program that makes PCRE's Unicode character property table had a bug
134        which caused it to generate incorrect table entries for sequences of
135        characters that have the same character type, but are in different scripts.
136        It amalgamated them into a single range, with the script of the first of
137        them. In other words, some characters were in the wrong script. There were
138        thirteen such cases, affecting characters in the following ranges:
140          U+002b0 - U+002c1
141          U+0060c - U+0060d
142          U+0061e - U+00612
143          U+0064b - U+0065e
144          U+0074d - U+0076d
145          U+01800 - U+01805
146          U+01d00 - U+01d77
147          U+01d9b - U+01dbf
148          U+0200b - U+0200f
149          U+030fc - U+030fe
150          U+03260 - U+0327f
151          U+0fb46 - U+0fbb1
152          U+10450 - U+1049d
154    12. The -o option (show only the matching part of a line) for pcregrep was not
155        compatible with GNU grep in that, if there was more than one match in a
156        line, it showed only the first of them. It now behaves in the same way as
157        GNU grep.
159    13. If the -o and -v options were combined for pcregrep, it printed a blank
160        line for every non-matching line. GNU grep prints nothing, and pcregrep now
161        does the same. The return code can be used to tell if there were any
162        non-matching lines.
164    14. Added --file-offsets and --line-offsets to pcregrep.
166    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
167        infinitely looping recursion. The bug was that positive lookaheads were not
168        being skipped when checking for a possible empty match (negative lookaheads
169        and both kinds of lookbehind were skipped).
171    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
172        inclusion of <windows.h> to before rather than after the definition of
173        INVALID_FILE_ATTRIBUTES (patch from David Byron).
175    17. Specifying a possessive quantifier with a specific limit for a Unicode
176        character property caused pcre_compile() to compile bad code, which led at
177        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
178        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
179        caused the error; without that there was no problem.
181    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
183    19. Added --enable-pcretest-libreadline.
185    20. In pcrecpp.cc, the variable 'count' was incremented twice in
186        RE::GlobalReplace(). As a result, the number of replacements returned was
187        double what it should be. I removed one of the increments, but Craig sent a
188        later patch that removed the other one (the right fix) and added unit tests
189        that check the return values (which was not done before).
191    21. Several CMake things:
193        (1) Arranged that, when cmake is used on Unix, the libraries end up with
194            the names libpcre and libpcreposix, not just pcre and pcreposix.
196        (2) The above change means that pcretest and pcregrep are now correctly
197            linked with the newly-built libraries, not previously installed ones.
201    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
202        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
203        UTF-8 newline character). The key issue is that the pattern starts .*;
204        this means that the match must be either at the beginning, or after a
205        newline. The bug was in the code for advancing after a failed match and
206        checking that the new position followed a newline. It was not taking
207        account of UTF-8 characters correctly.
209    23. PCRE was behaving differently from Perl in the way it recognized POSIX
210        character classes. PCRE was not treating the sequence [:...:] as a
211        character class unless the ... were all letters. Perl, however, seems to
212        allow any characters between [: and :], though of course it rejects as
213        unknown any "names" that contain non-letters, because all the known class
214        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
215        for example, whereas PCRE did not - it did not recognize a POSIX character
216        class. This seemed a bit dangerous, so the code has been changed to be
217        closer to Perl. The behaviour is not identical to Perl, because PCRE will
218        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
219        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
220        Perl does, and where it didn't before.
222    24. Rewrite so as to remove the single use of %n from pcregrep because in some
223        Windows environments %n is disabled by default.
226    Version 7.4 21-Sep-07
227    ---------------------
229    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
230        means that a class such as [\s] counted as "explicit reference to CR or
231        LF". That isn't really right - the whole point of the change was to try to
232        help when there was an actual mention of one of the two characters. So now
233        the change happens only if \r or \n (or a literal CR or LF) character is
234        encountered.
236    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
237        of both had grown to the point where there were only 3 bits left.
238        Fortunately, there was spare space in the data structure, and so I have
239        moved the internal flags into a new 16-bit field to free up more option
240        bits.
242    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
243        but did not set the internal JCHANGED flag - either of these is enough to
244        control the way the "get" function works - but the PCRE_INFO_JCHANGED
245        facility is supposed to tell if (?J) was ever used, so now (?J) at the
246        start sets both bits.
248    4.  Added options (at build time, compile time, exec time) to change \R from
249        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
251    5.  doc/pcresyntax.html was missing from the distribution.
253    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
254        compatibility, even though it is no longer used.
256    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
257        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
258        windows.h file is present (where different names are used). [This was
259        reversed later after testing - see 16 below.]
261    8.  Changed all #include <config.h> to #include "config.h". There were also
262        some further <pcre.h> cases that I changed to "pcre.h".
264    9.  When pcregrep was used with the --colour option, it missed the line ending
265        sequence off the lines that it output.
267    10. It was pointed out to me that arrays of string pointers cause lots of
268        relocations when a shared library is dynamically loaded. A technique of
269        using a single long string with a table of offsets can drastically reduce
270        these. I have refactored PCRE in four places to do this. The result is
271        dramatic:
273          Originally:                          290
274          After changing UCP table:            187
275          After changing error message table:   43
276          After changing table of "verbs"       36
277          After changing table of Posix names   22
279        Thanks to the folks working on Gregex for glib for this insight.
281    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
282        unicode-properties was also set.
284    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
286    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
287        checked only for CRLF.
289    14. Added casts to pcretest.c to avoid compiler warnings.
291    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
293    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
294        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
295        entirely. This removes changes made in 7 above.
297    17. The CMake files have been updated, and there is now more information about
298        building with CMake in the NON-UNIX-USE document.
301    Version 7.3 28-Aug-07
302    ---------------------
304     1. In the rejigging of the build system that eventually resulted in 7.1, the
305        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
306        brackets there is not right, since it causes compilers to look for an
307        installed pcre.h, not the version that is in the source that is being
308        compiled (which of course may be different). I have changed it back to:
310          #include "pcre.h"
312        I have a vague recollection that the change was concerned with compiling in
313        different directories, but in the new build system, that is taken care of
314        by the VPATH setting the Makefile.
316     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
317        when the subject happened to end in the byte 0x85 (e.g. if the last
318        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
319        characters but of course it shouldn't be taken as a newline when it is part
320        of another character. The bug was that, for an unlimited repeat of . in
321        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
322        characters when looking for a newline.
324     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
326     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
327        in debug output.
329     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
330        long printing in the pcrecpp unittest when running under MinGW.
332     6. ESC_K was left out of the EBCDIC table.
334     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
335        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
336        limit also applies to "virtual nesting" when a pattern is recursive, and in
337        this case 1000 isn't so big. I have been able to remove this limit at the
338        expense of backing off one optimization in certain circumstances. Normally,
339        when pcre_exec() would call its internal match() function recursively and
340        immediately return the result unconditionally, it uses a "tail recursion"
341        feature to save stack. However, when a subpattern that can match an empty
342        string has an unlimited repetition quantifier, it no longer makes this
343        optimization. That gives it a stack frame in which to save the data for
344        checking that an empty string has been matched. Previously this was taken
345        from the 1000-entry workspace that had been reserved. So now there is no
346        explicit limit, but more stack is used.
348     8. Applied Daniel's patches to solve problems with the import/export magic
349        syntax that is required for Windows, and which was going wrong for the
350        pcreposix and pcrecpp parts of the library. These were overlooked when this
351        problem was solved for the main library.
353     9. There were some crude static tests to avoid integer overflow when computing
354        the size of patterns that contain repeated groups with explicit upper
355        limits. As the maximum quantifier is 65535, the maximum group length was
356        set at 30,000 so that the product of these two numbers did not overflow a
357        32-bit integer. However, it turns out that people want to use groups that
358        are longer than 30,000 bytes (though not repeat them that many times).
359        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
360        made it possible to implement the integer overflow checks in a much more
361        dynamic way, which I have now done. The artificial limitation on group
362        length has been removed - we now have only the limit on the total length of
363        the compiled pattern, which depends on the LINK_SIZE setting.
365    10. Fixed a bug in the documentation for get/copy named substring when
366        duplicate names are permitted. If none of the named substrings are set, the
367        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
368        empty string.
370    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
371        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
372        because the ] is interpreted as the first data character and the
373        terminating ] is not found. PCRE has been made compatible with Perl in this
374        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
375        cause memory overwriting.
377    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
378        string has been matched (to stop an infinite loop). It was not recognizing
379        a conditional subpattern that could match an empty string if that
380        subpattern was within another subpattern. For example, it looped when
381        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
382        condition was not nested. This bug has been fixed.
384    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
385        past the start of the subject in the presence of bytes with the top bit
386        set, for example "\x8aBCD".
388    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
389        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
391    14. Optimized (?!) to (*FAIL).
393    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
394        This restricts code points to be within the range 0 to 0x10FFFF, excluding
395        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
396        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
397        does: it's just the validity check that is more restrictive.
399    16. Inserted checks for integer overflows during escape sequence (backslash)
400        processing, and also fixed erroneous offset values for syntax errors during
401        backslash processing.
403    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
404        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
406    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
407        caused an overrun.
409    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
410        something other than just ASCII characters) inside a group that had an
411        unlimited repeat caused a loop at compile time (while checking to see
412        whether the group could match an empty string).
414    20. Debugging a pattern containing \p or \P could cause a crash. For example,
415        [\P{Any}] did so. (Error in the code for printing property names.)
417    21. An orphan \E inside a character class could cause a crash.
419    22. A repeated capturing bracket such as (A)? could cause a wild memory
420        reference during compilation.
422    23. There are several functions in pcre_compile() that scan along a compiled
423        expression for various reasons (e.g. to see if it's fixed length for look
424        behind). There were bugs in these functions when a repeated \p or \P was
425        present in the pattern. These operators have additional parameters compared
426        with \d, etc, and these were not being taken into account when moving along
427        the compiled data. Specifically:
429        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
430            length.
432        (b) An item such as \pL+ within a repeated group could cause crashes or
433            loops.
435        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
436            "reference to non-existent subpattern" error.
438        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
440    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
441        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
443    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
445    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
446        character were causing crashes (broken optimization).
448    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
449        \p or \P) caused a compile-time loop.
451    28. More problems have arisen in unanchored patterns when CRLF is a valid line
452        break. For example, the unstudied pattern [\r\n]A does not match the string
453        "\r\nA" because change 7.0/46 below moves the current point on by two
454        characters after failing to match at the start. However, the pattern \nA
455        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
456        the same is true. There doesn't seem any very clean way out of this, but
457        what I have chosen to do makes the common cases work: PCRE now takes note
458        of whether there can be an explicit match for \r or \n anywhere in the
459        pattern, and if so, 7.0/46 no longer applies. As part of this change,
460        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
461        pattern has explicit CR or LF references.
463    29. Added (*CR) etc for changing newline setting at start of pattern.
466    Version 7.2 19-Jun-07
467  ---------------------  ---------------------
469   1. If the fr_FR locale cannot be found for test 3, try the "french" locale,   1. If the fr_FR locale cannot be found for test 3, try the "french" locale,

Removed from v.185  
changed lines
  Added in v.327

  ViewVC Help
Powered by ViewVC 1.1.5