ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 200 by ph10, Wed Aug 1 09:10:40 2007 UTC revision 323 by ph10, Wed Mar 5 17:23:42 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.3 05-Jul-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.
19    Version 7.6 28-Jan-08
20    ---------------------
22    1.  A character class containing a very large number of characters with
23        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
24        overflow.
26    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
27        HAVE_LONG_LONG is not defined.
29    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
30        bring them up to date and include new features. This patch includes:
32        - Fixed PH's badly added libz and libbz2 support.
33        - Fixed a problem with static linking.
34        - Added pcredemo. [But later removed - see 7 below.]
35        - Fixed dftables problem and added an option.
36        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
37            HAVE_LONG_LONG.
38        - Added readline support for pcretest.
39        - Added an listing of the option settings after cmake has run.
41    4.  A user submitted a patch to Makefile that makes it easy to create
42        "pcre.dll" under mingw when using Configure/Make. I added stuff to
43        Makefile.am that cause it to include this special target, without
44        affecting anything else. Note that the same mingw target plus all
45        the other distribution libraries and programs are now supported
46        when configuring with CMake (see 6 below) instead of with
47        Configure/Make.
49    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
50        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
51        exported in the Windows port". It has not yet been confirmed that the patch
52        solves the problem, but it does no harm.
54    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
55        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
56        with CMake, and also correct the comment about stack recursion.
58    7.  Remove the automatic building of pcredemo from the ./configure system and
59        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
60        of a program that users should build themselves after PCRE is installed, so
61        building it automatically is not really right. What is more, it gave
62        trouble in some build environments.
64    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
67    Version 7.5 10-Jan-08
68    ---------------------
70    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
71        values in parens when parsing an RE using the C++ wrapper."
73    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
74        Characters greater than 255 were excluded from the class instead of being
75        included.
77    3.  The same bug as (2) above applied to negated POSIX classes such as
78        [:^space:].
80    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
81        defined or documented. It seems to have been a typo for PCRE_STATIC, so
82        I have changed it.
84    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
85        first named subpattern) and a construct such as (?&a) would reference the
86        first named subpattern whose name started with "a" (in other words, the
87        length check was missing). Both these problems are fixed. "Subpattern name
88        expected" is now given for (?&) (a zero-length name), and this patch also
89        makes it give the same error for \k'' (previously it complained that that
90        was a reference to a non-existent subpattern).
92    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
93        this is right because (?- can be followed by option settings as well as by
94        digits. I have, however, made the messages clearer.
96    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
97        than the number used in the conditional) now cause a compile-time error.
98        This is actually not compatible with Perl, which accepts such patterns, but
99        treats the conditional as always being FALSE (as PCRE used to), but it
100        seems to me that giving a diagnostic is better.
102    8.  Change "alphameric" to the more common word "alphanumeric" in comments
103        and messages.
105    9.  Fix two occurrences of "backslash" in comments that should have been
106        "backspace".
108    10. Remove two redundant lines of code that can never be obeyed (their function
109        was moved elsewhere).
111    11. The program that makes PCRE's Unicode character property table had a bug
112        which caused it to generate incorrect table entries for sequences of
113        characters that have the same character type, but are in different scripts.
114        It amalgamated them into a single range, with the script of the first of
115        them. In other words, some characters were in the wrong script. There were
116        thirteen such cases, affecting characters in the following ranges:
118          U+002b0 - U+002c1
119          U+0060c - U+0060d
120          U+0061e - U+00612
121          U+0064b - U+0065e
122          U+0074d - U+0076d
123          U+01800 - U+01805
124          U+01d00 - U+01d77
125          U+01d9b - U+01dbf
126          U+0200b - U+0200f
127          U+030fc - U+030fe
128          U+03260 - U+0327f
129          U+0fb46 - U+0fbb1
130          U+10450 - U+1049d
132    12. The -o option (show only the matching part of a line) for pcregrep was not
133        compatible with GNU grep in that, if there was more than one match in a
134        line, it showed only the first of them. It now behaves in the same way as
135        GNU grep.
137    13. If the -o and -v options were combined for pcregrep, it printed a blank
138        line for every non-matching line. GNU grep prints nothing, and pcregrep now
139        does the same. The return code can be used to tell if there were any
140        non-matching lines.
142    14. Added --file-offsets and --line-offsets to pcregrep.
144    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
145        infinitely looping recursion. The bug was that positive lookaheads were not
146        being skipped when checking for a possible empty match (negative lookaheads
147        and both kinds of lookbehind were skipped).
149    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
150        inclusion of <windows.h> to before rather than after the definition of
151        INVALID_FILE_ATTRIBUTES (patch from David Byron).
153    17. Specifying a possessive quantifier with a specific limit for a Unicode
154        character property caused pcre_compile() to compile bad code, which led at
155        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
156        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
157        caused the error; without that there was no problem.
159    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
161    19. Added --enable-pcretest-libreadline.
163    20. In pcrecpp.cc, the variable 'count' was incremented twice in
164        RE::GlobalReplace(). As a result, the number of replacements returned was
165        double what it should be. I removed one of the increments, but Craig sent a
166        later patch that removed the other one (the right fix) and added unit tests
167        that check the return values (which was not done before).
169    21. Several CMake things:
171        (1) Arranged that, when cmake is used on Unix, the libraries end up with
172            the names libpcre and libpcreposix, not just pcre and pcreposix.
174        (2) The above change means that pcretest and pcregrep are now correctly
175            linked with the newly-built libraries, not previously installed ones.
179    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
180        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
181        UTF-8 newline character). The key issue is that the pattern starts .*;
182        this means that the match must be either at the beginning, or after a
183        newline. The bug was in the code for advancing after a failed match and
184        checking that the new position followed a newline. It was not taking
185        account of UTF-8 characters correctly.
187    23. PCRE was behaving differently from Perl in the way it recognized POSIX
188        character classes. PCRE was not treating the sequence [:...:] as a
189        character class unless the ... were all letters. Perl, however, seems to
190        allow any characters between [: and :], though of course it rejects as
191        unknown any "names" that contain non-letters, because all the known class
192        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
193        for example, whereas PCRE did not - it did not recognize a POSIX character
194        class. This seemed a bit dangerous, so the code has been changed to be
195        closer to Perl. The behaviour is not identical to Perl, because PCRE will
196        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
197        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
198        Perl does, and where it didn't before.
200    24. Rewrite so as to remove the single use of %n from pcregrep because in some
201        Windows environments %n is disabled by default.
204    Version 7.4 21-Sep-07
205    ---------------------
207    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
208        means that a class such as [\s] counted as "explicit reference to CR or
209        LF". That isn't really right - the whole point of the change was to try to
210        help when there was an actual mention of one of the two characters. So now
211        the change happens only if \r or \n (or a literal CR or LF) character is
212        encountered.
214    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
215        of both had grown to the point where there were only 3 bits left.
216        Fortunately, there was spare space in the data structure, and so I have
217        moved the internal flags into a new 16-bit field to free up more option
218        bits.
220    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
221        but did not set the internal JCHANGED flag - either of these is enough to
222        control the way the "get" function works - but the PCRE_INFO_JCHANGED
223        facility is supposed to tell if (?J) was ever used, so now (?J) at the
224        start sets both bits.
226    4.  Added options (at build time, compile time, exec time) to change \R from
227        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
229    5.  doc/pcresyntax.html was missing from the distribution.
231    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
232        compatibility, even though it is no longer used.
234    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
235        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
236        windows.h file is present (where different names are used). [This was
237        reversed later after testing - see 16 below.]
239    8.  Changed all #include <config.h> to #include "config.h". There were also
240        some further <pcre.h> cases that I changed to "pcre.h".
242    9.  When pcregrep was used with the --colour option, it missed the line ending
243        sequence off the lines that it output.
245    10. It was pointed out to me that arrays of string pointers cause lots of
246        relocations when a shared library is dynamically loaded. A technique of
247        using a single long string with a table of offsets can drastically reduce
248        these. I have refactored PCRE in four places to do this. The result is
249        dramatic:
251          Originally:                          290
252          After changing UCP table:            187
253          After changing error message table:   43
254          After changing table of "verbs"       36
255          After changing table of Posix names   22
257        Thanks to the folks working on Gregex for glib for this insight.
259    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
260        unicode-properties was also set.
262    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
264    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
265        checked only for CRLF.
267    14. Added casts to pcretest.c to avoid compiler warnings.
269    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
271    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
272        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
273        entirely. This removes changes made in 7 above.
275    17. The CMake files have been updated, and there is now more information about
276        building with CMake in the NON-UNIX-USE document.
279    Version 7.3 28-Aug-07
280  ---------------------  ---------------------
282   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 29  Version 7.3 05-Jul-07 Line 304  Version 7.3 05-Jul-07
304   4. Debugging: adjusted the names of opcodes for different kinds of parentheses   4. Debugging: adjusted the names of opcodes for different kinds of parentheses
305      in debug output.      in debug output.
307   5. Arrange to use "%I64d" instead of "%lld" for long printing in the pcrecpp   5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
308      unittest when running under MinGW.      long printing in the pcrecpp unittest when running under MinGW.
310   6. ESC_K was left out of the EBCDIC table.   6. ESC_K was left out of the EBCDIC table.
# Line 53  Version 7.3 05-Jul-07 Line 328  Version 7.3 05-Jul-07
328      pcreposix and pcrecpp parts of the library. These were overlooked when this      pcreposix and pcrecpp parts of the library. These were overlooked when this
329      problem was solved for the main library.      problem was solved for the main library.
331     9. There were some crude static tests to avoid integer overflow when computing
332        the size of patterns that contain repeated groups with explicit upper
333        limits. As the maximum quantifier is 65535, the maximum group length was
334        set at 30,000 so that the product of these two numbers did not overflow a
335        32-bit integer. However, it turns out that people want to use groups that
336        are longer than 30,000 bytes (though not repeat them that many times).
337        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
338        made it possible to implement the integer overflow checks in a much more
339        dynamic way, which I have now done. The artificial limitation on group
340        length has been removed - we now have only the limit on the total length of
341        the compiled pattern, which depends on the LINK_SIZE setting.
343    10. Fixed a bug in the documentation for get/copy named substring when
344        duplicate names are permitted. If none of the named substrings are set, the
345        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
346        empty string.
348    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
349        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
350        because the ] is interpreted as the first data character and the
351        terminating ] is not found. PCRE has been made compatible with Perl in this
352        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
353        cause memory overwriting.
355    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
356        string has been matched (to stop an infinite loop). It was not recognizing
357        a conditional subpattern that could match an empty string if that
358        subpattern was within another subpattern. For example, it looped when
359        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
360        condition was not nested. This bug has been fixed.
362    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
363        past the start of the subject in the presence of bytes with the top bit
364        set, for example "\x8aBCD".
366    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
367        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
369    14. Optimized (?!) to (*FAIL).
371    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
372        This restricts code points to be within the range 0 to 0x10FFFF, excluding
373        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
374        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
375        does: it's just the validity check that is more restrictive.
377    16. Inserted checks for integer overflows during escape sequence (backslash)
378        processing, and also fixed erroneous offset values for syntax errors during
379        backslash processing.
381    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
382        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
384    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
385        caused an overrun.
387    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
388        something other than just ASCII characters) inside a group that had an
389        unlimited repeat caused a loop at compile time (while checking to see
390        whether the group could match an empty string).
392    20. Debugging a pattern containing \p or \P could cause a crash. For example,
393        [\P{Any}] did so. (Error in the code for printing property names.)
395    21. An orphan \E inside a character class could cause a crash.
397    22. A repeated capturing bracket such as (A)? could cause a wild memory
398        reference during compilation.
400    23. There are several functions in pcre_compile() that scan along a compiled
401        expression for various reasons (e.g. to see if it's fixed length for look
402        behind). There were bugs in these functions when a repeated \p or \P was
403        present in the pattern. These operators have additional parameters compared
404        with \d, etc, and these were not being taken into account when moving along
405        the compiled data. Specifically:
407        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
408            length.
410        (b) An item such as \pL+ within a repeated group could cause crashes or
411            loops.
413        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
414            "reference to non-existent subpattern" error.
416        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
418    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
419        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
421    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
423    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
424        character were causing crashes (broken optimization).
426    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
427        \p or \P) caused a compile-time loop.
429    28. More problems have arisen in unanchored patterns when CRLF is a valid line
430        break. For example, the unstudied pattern [\r\n]A does not match the string
431        "\r\nA" because change 7.0/46 below moves the current point on by two
432        characters after failing to match at the start. However, the pattern \nA
433        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
434        the same is true. There doesn't seem any very clean way out of this, but
435        what I have chosen to do makes the common cases work: PCRE now takes note
436        of whether there can be an explicit match for \r or \n anywhere in the
437        pattern, and if so, 7.0/46 no longer applies. As part of this change,
438        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
439        pattern has explicit CR or LF references.
441    29. Added (*CR) etc for changing newline setting at start of pattern.
444  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
445  ---------------------  ---------------------

Removed from v.200  
changed lines
  Added in v.323

ViewVC Help
Powered by ViewVC 1.1.12