ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.165  
changed lines
  Added in v.328

  ViewVC Help
Powered by ViewVC 1.1.5