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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.161  
changed lines
  Added in v.321

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12