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

  ViewVC Help
Powered by ViewVC 1.1.5