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

Diff of /code/trunk/ChangeLog

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

revision 217 by ph10, Wed Aug 15 15:21:04 2007 UTC revision 291 by ph10, Wed Dec 26 18:46:46 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 09-Aug-07  Version 7.5 23-Dec-07
5    ---------------------
6    
7    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
8        values in parens when parsing an RE using the C++ wrapper."
9    
10    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
11        Characters greater than 255 were excluded from the class instead of being
12        included.
13    
14    3.  The same bug as (2) above applied to negated POSIX classes such as
15        [:^space:].
16    
17    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
18        defined or documented. It seems to have been a typo for PCRE_STATIC, so
19        I have changed it.
20    
21    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
22        first named subpattern) and a construct such as (?&a) would reference the
23        first named subpattern whose name started with "a" (in other words, the
24        length check was missing). Both these problems are fixed. "Subpattern name
25        expected" is now given for (?&) (a zero-length name), and this patch also
26        makes it give the same error for \k'' (previously it complained that that
27        was a reference to a non-existent subpattern).
28    
29    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
30        this is right because (?- can be followed by option settings as well as by
31        digits. I have, however, made the messages clearer.
32    
33    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
34        than the number used in the conditional) now cause a compile-time error.
35        This is actually not compatible with Perl, which accepts such patterns, but
36        treats the conditional as always being FALSE (as PCRE used to), but it
37        seems to me that giving a diagnostic is better.
38    
39    8.  Change "alphameric" to the more common word "alphanumeric" in comments
40        and messages.
41    
42    9.  Fix two occurrences of "backslash" in comments that should have been
43        "backspace".
44    
45    10. Remove two redundant lines of code that can never be obeyed (their function
46        was moved elsewhere).
47    
48    11. The program that makes PCRE's Unicode character property table had a bug
49        which caused it to generate incorrect table entries for sequences of
50        characters that have the same character type, but are in different scripts.
51        It amalgamated them into a single range, with the script of the first of
52        them. In other words, some characters were in the wrong script. There were
53        thirteen such cases, affecting characters in the following ranges:
54    
55          U+002b0 - U+002c1
56          U+0060c - U+0060d
57          U+0061e - U+00612
58          U+0064b - U+0065e
59          U+0074d - U+0076d
60          U+01800 - U+01805
61          U+01d00 - U+01d77
62          U+01d9b - U+01dbf
63          U+0200b - U+0200f
64          U+030fc - U+030fe
65          U+03260 - U+0327f
66          U+0fb46 - U+0fbb1
67          U+10450 - U+1049d
68    
69    12. The -o option (show only the matching part of a line) for pcregrep was not
70        compatible with GNU grep in that, if there was more than one match in a
71        line, it showed only the first of them. It now behaves in the same way as
72        GNU grep.
73    
74    13. If the -o and -v options were combined for pcregrep, it printed a blank
75        line for every non-matching line. GNU grep prints nothing, and pcregrep now
76        does the same. The return code can be used to tell if there were any
77        non-matching lines.
78    
79    14. Added --file-offsets and --line-offsets to pcregrep.
80    
81    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
82        infinitely looping recursion. The bug was that positive lookaheads were not
83        being skipped when checking for a possible empty match (negative lookaheads
84        and both kinds of lookbehind were skipped).
85    
86    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
87        inclusion of <windows.h> to before rather than after the definition of
88        INVALID_FILE_ATTRIBUTES (patch from David Byron).
89    
90    17. Specifying a possessive quantifier with a specific limit for a Unicode
91        character property caused pcre_compile() to compile bad code, which led at
92        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
93        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
94        caused the error; without that there was no problem.
95    
96    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
97    
98    19. Added --enable-pcretest-libreadline.
99    
100    20. In pcrecpp.cc, the variable 'count' was incremented twice in
101        RE::GlobalReplace(). As a result, the number of replacements returned was
102        double what it should be. I have removed one of the increments.
103    
104    21. Several CMake things:
105    
106        (1) Arranged that, when cmake is used on Unix, the libraries end up with
107            the names libpcre and libpcreposix.
108    
109        (2) Arranged for pcretest and pcregrep to link with the newly-built
110            libraries, not previously installed ones.
111    
112        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
113    
114    
115    Version 7.4 21-Sep-07
116    ---------------------
117    
118    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
119        means that a class such as [\s] counted as "explicit reference to CR or
120        LF". That isn't really right - the whole point of the change was to try to
121        help when there was an actual mention of one of the two characters. So now
122        the change happens only if \r or \n (or a literal CR or LF) character is
123        encountered.
124    
125    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
126        of both had grown to the point where there were only 3 bits left.
127        Fortunately, there was spare space in the data structure, and so I have
128        moved the internal flags into a new 16-bit field to free up more option
129        bits.
130    
131    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
132        but did not set the internal JCHANGED flag - either of these is enough to
133        control the way the "get" function works - but the PCRE_INFO_JCHANGED
134        facility is supposed to tell if (?J) was ever used, so now (?J) at the
135        start sets both bits.
136    
137    4.  Added options (at build time, compile time, exec time) to change \R from
138        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
139    
140    5.  doc/pcresyntax.html was missing from the distribution.
141    
142    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
143        compatibility, even though it is no longer used.
144    
145    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
146        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
147        windows.h file is present (where different names are used). [This was
148        reversed later after testing - see 16 below.]
149    
150    8.  Changed all #include <config.h> to #include "config.h". There were also
151        some further <pcre.h> cases that I changed to "pcre.h".
152    
153    9.  When pcregrep was used with the --colour option, it missed the line ending
154        sequence off the lines that it output.
155    
156    10. It was pointed out to me that arrays of string pointers cause lots of
157        relocations when a shared library is dynamically loaded. A technique of
158        using a single long string with a table of offsets can drastically reduce
159        these. I have refactored PCRE in four places to do this. The result is
160        dramatic:
161    
162          Originally:                          290
163          After changing UCP table:            187
164          After changing error message table:   43
165          After changing table of "verbs"       36
166          After changing table of Posix names   22
167    
168        Thanks to the folks working on Gregex for glib for this insight.
169    
170    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
171        unicode-properties was also set.
172    
173    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
174    
175    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
176        checked only for CRLF.
177    
178    14. Added casts to pcretest.c to avoid compiler warnings.
179    
180    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
181    
182    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
183        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
184        entirely. This removes changes made in 7 above.
185    
186    17. The CMake files have been updated, and there is now more information about
187        building with CMake in the NON-UNIX-USE document.
188    
189    
190    Version 7.3 28-Aug-07
191  ---------------------  ---------------------
192    
193   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 98  Version 7.3 09-Aug-07 Line 284  Version 7.3 09-Aug-07
284      the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the      the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
285      full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still      full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
286      does: it's just the validity check that is more restrictive.      does: it's just the validity check that is more restrictive.
287    
288  16. Inserted checks for integer overflows during escape sequence (backslash)  16. Inserted checks for integer overflows during escape sequence (backslash)
289      processing, and also fixed erroneous offset values for syntax errors during      processing, and also fixed erroneous offset values for syntax errors during
290      backslash processing.      backslash processing.
291    
292  17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)  17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
293      for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".      for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
294    
295  18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"  18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
296      caused an overrun.      caused an overrun.
297    
298  19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with  19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
299      something other than just ASCII characters) inside a group that had an      something other than just ASCII characters) inside a group that had an
300      unlimited repeat caused a loop at compile time (while checking to see      unlimited repeat caused a loop at compile time (while checking to see
301      whether the group could match an empty string).      whether the group could match an empty string).
302    
303  20. Debugging a pattern containing \p or \P could cause a crash. For example,  20. Debugging a pattern containing \p or \P could cause a crash. For example,
304      [\P{Any}] did so. (Error in the code for printing property names.)      [\P{Any}] did so. (Error in the code for printing property names.)
305    
306    21. An orphan \E inside a character class could cause a crash.
307    
308    22. A repeated capturing bracket such as (A)? could cause a wild memory
309        reference during compilation.
310    
311    23. There are several functions in pcre_compile() that scan along a compiled
312        expression for various reasons (e.g. to see if it's fixed length for look
313        behind). There were bugs in these functions when a repeated \p or \P was
314        present in the pattern. These operators have additional parameters compared
315        with \d, etc, and these were not being taken into account when moving along
316        the compiled data. Specifically:
317    
318        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
319            length.
320    
321        (b) An item such as \pL+ within a repeated group could cause crashes or
322            loops.
323    
324        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
325            "reference to non-existent subpattern" error.
326    
327        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
328    
329    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
330        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
331    
332    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
333    
334    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
335        character were causing crashes (broken optimization).
336    
337    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
338        \p or \P) caused a compile-time loop.
339    
340    28. More problems have arisen in unanchored patterns when CRLF is a valid line
341        break. For example, the unstudied pattern [\r\n]A does not match the string
342        "\r\nA" because change 7.0/46 below moves the current point on by two
343        characters after failing to match at the start. However, the pattern \nA
344        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
345        the same is true. There doesn't seem any very clean way out of this, but
346        what I have chosen to do makes the common cases work: PCRE now takes note
347        of whether there can be an explicit match for \r or \n anywhere in the
348        pattern, and if so, 7.0/46 no longer applies. As part of this change,
349        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
350        pattern has explicit CR or LF references.
351    
352    29. Added (*CR) etc for changing newline setting at start of pattern.
353    
354    
355  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
356  ---------------------  ---------------------

Legend:
Removed from v.217  
changed lines
  Added in v.291

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12