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

Diff of /code/trunk/ChangeLog

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

revision 211 by ph10, Thu Aug 9 09:52:43 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  ------------------  ------------------
3    
4  Version 7.3 05-Jul-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    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.
14    
15    3.  Remove a line of dead code, identified by coverity and reported by Nuno
16        Lopes.
17    
18    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
19    
20        (1) The include/exclude patterns were being applied to the whole pathnames
21            of files, instead of just to the final components.
22    
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.
29    
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.
32    
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.
36    
37    7.  Added some missing "const"s to declarations of static tables in
38        pcre_compile.c and pcre_dfa_exec.c.
39    
40    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
41        caused by fix #2  above.
42    
43    
44    Version 7.6 28-Jan-08
45    ---------------------
46    
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.
50    
51    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
52        HAVE_LONG_LONG is not defined.
53    
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:
56    
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.
65    
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.
73    
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.
78    
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.
82    
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.
88    
89    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
90    
91    
92    Version 7.5 10-Jan-08
93    ---------------------
94    
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."
97    
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.
101    
102    3.  The same bug as (2) above applied to negated POSIX classes such as
103        [:^space:].
104    
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.
108    
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).
116    
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.
120    
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.
126    
127    8.  Change "alphameric" to the more common word "alphanumeric" in comments
128        and messages.
129    
130    9.  Fix two occurrences of "backslash" in comments that should have been
131        "backspace".
132    
133    10. Remove two redundant lines of code that can never be obeyed (their function
134        was moved elsewhere).
135    
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:
142    
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
156    
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.
161    
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.
166    
167    14. Added --file-offsets and --line-offsets to pcregrep.
168    
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).
173    
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).
177    
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.
183    
184    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
185    
186    19. Added --enable-pcretest-libreadline.
187    
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).
193    
194    21. Several CMake things:
195    
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.
198    
199        (2) The above change means that pcretest and pcregrep are now correctly
200            linked with the newly-built libraries, not previously installed ones.
201    
202        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
203    
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.
211    
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.
224    
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.
227    
228    
229    Version 7.4 21-Sep-07
230    ---------------------
231    
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.
238    
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.
244    
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.
250    
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.
253    
254    5.  doc/pcresyntax.html was missing from the distribution.
255    
256    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
257        compatibility, even though it is no longer used.
258    
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.]
263    
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".
266    
267    9.  When pcregrep was used with the --colour option, it missed the line ending
268        sequence off the lines that it output.
269    
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:
275    
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
281    
282        Thanks to the folks working on Gregex for glib for this insight.
283    
284    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
285        unicode-properties was also set.
286    
287    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
288    
289    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
290        checked only for CRLF.
291    
292    14. Added casts to pcretest.c to avoid compiler warnings.
293    
294    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
295    
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.
299    
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.
302    
303    
304    Version 7.3 28-Aug-07
305  ---------------------  ---------------------
306    
307   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 93  Version 7.3 05-Jul-07 Line 393  Version 7.3 05-Jul-07
393    
394  14. Optimized (?!) to (*FAIL).  14. Optimized (?!) to (*FAIL).
395    
396  15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.  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      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      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      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.      does: it's just the validity check that is more restrictive.
401    
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.
405    
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".
408    
409    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
410        caused an overrun.
411    
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).
416    
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.)
419    
420    21. An orphan \E inside a character class could cause a crash.
421    
422    22. A repeated capturing bracket such as (A)? could cause a wild memory
423        reference during compilation.
424    
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:
431    
432        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
433            length.
434    
435        (b) An item such as \pL+ within a repeated group could cause crashes or
436            loops.
437    
438        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
439            "reference to non-existent subpattern" error.
440    
441        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
442    
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").
445    
446    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
447    
448    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
449        character were causing crashes (broken optimization).
450    
451    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
452        \p or \P) caused a compile-time loop.
453    
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.
465    
466    29. Added (*CR) etc for changing newline setting at start of pattern.
467    
468    
469  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07

Legend:
Removed from v.211  
changed lines
  Added in v.328

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12