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

Diff of /code/trunk/ChangeLog

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

revision 219 by ph10, Thu Aug 16 11:46:40 2007 UTC revision 325 by ph10, Sat Mar 8 17:13:02 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 09-Aug-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    
34    Version 7.6 28-Jan-08
35    ---------------------
36    
37    1.  A character class containing a very large number of characters with
38        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
39        overflow.
40    
41    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
42        HAVE_LONG_LONG is not defined.
43    
44    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
45        bring them up to date and include new features. This patch includes:
46    
47        - Fixed PH's badly added libz and libbz2 support.
48        - Fixed a problem with static linking.
49        - Added pcredemo. [But later removed - see 7 below.]
50        - Fixed dftables problem and added an option.
51        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
52            HAVE_LONG_LONG.
53        - Added readline support for pcretest.
54        - Added an listing of the option settings after cmake has run.
55    
56    4.  A user submitted a patch to Makefile that makes it easy to create
57        "pcre.dll" under mingw when using Configure/Make. I added stuff to
58        Makefile.am that cause it to include this special target, without
59        affecting anything else. Note that the same mingw target plus all
60        the other distribution libraries and programs are now supported
61        when configuring with CMake (see 6 below) instead of with
62        Configure/Make.
63    
64    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
65        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
66        exported in the Windows port". It has not yet been confirmed that the patch
67        solves the problem, but it does no harm.
68    
69    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
70        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
71        with CMake, and also correct the comment about stack recursion.
72    
73    7.  Remove the automatic building of pcredemo from the ./configure system and
74        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
75        of a program that users should build themselves after PCRE is installed, so
76        building it automatically is not really right. What is more, it gave
77        trouble in some build environments.
78    
79    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
80    
81    
82    Version 7.5 10-Jan-08
83    ---------------------
84    
85    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
86        values in parens when parsing an RE using the C++ wrapper."
87    
88    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
89        Characters greater than 255 were excluded from the class instead of being
90        included.
91    
92    3.  The same bug as (2) above applied to negated POSIX classes such as
93        [:^space:].
94    
95    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
96        defined or documented. It seems to have been a typo for PCRE_STATIC, so
97        I have changed it.
98    
99    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
100        first named subpattern) and a construct such as (?&a) would reference the
101        first named subpattern whose name started with "a" (in other words, the
102        length check was missing). Both these problems are fixed. "Subpattern name
103        expected" is now given for (?&) (a zero-length name), and this patch also
104        makes it give the same error for \k'' (previously it complained that that
105        was a reference to a non-existent subpattern).
106    
107    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
108        this is right because (?- can be followed by option settings as well as by
109        digits. I have, however, made the messages clearer.
110    
111    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
112        than the number used in the conditional) now cause a compile-time error.
113        This is actually not compatible with Perl, which accepts such patterns, but
114        treats the conditional as always being FALSE (as PCRE used to), but it
115        seems to me that giving a diagnostic is better.
116    
117    8.  Change "alphameric" to the more common word "alphanumeric" in comments
118        and messages.
119    
120    9.  Fix two occurrences of "backslash" in comments that should have been
121        "backspace".
122    
123    10. Remove two redundant lines of code that can never be obeyed (their function
124        was moved elsewhere).
125    
126    11. The program that makes PCRE's Unicode character property table had a bug
127        which caused it to generate incorrect table entries for sequences of
128        characters that have the same character type, but are in different scripts.
129        It amalgamated them into a single range, with the script of the first of
130        them. In other words, some characters were in the wrong script. There were
131        thirteen such cases, affecting characters in the following ranges:
132    
133          U+002b0 - U+002c1
134          U+0060c - U+0060d
135          U+0061e - U+00612
136          U+0064b - U+0065e
137          U+0074d - U+0076d
138          U+01800 - U+01805
139          U+01d00 - U+01d77
140          U+01d9b - U+01dbf
141          U+0200b - U+0200f
142          U+030fc - U+030fe
143          U+03260 - U+0327f
144          U+0fb46 - U+0fbb1
145          U+10450 - U+1049d
146    
147    12. The -o option (show only the matching part of a line) for pcregrep was not
148        compatible with GNU grep in that, if there was more than one match in a
149        line, it showed only the first of them. It now behaves in the same way as
150        GNU grep.
151    
152    13. If the -o and -v options were combined for pcregrep, it printed a blank
153        line for every non-matching line. GNU grep prints nothing, and pcregrep now
154        does the same. The return code can be used to tell if there were any
155        non-matching lines.
156    
157    14. Added --file-offsets and --line-offsets to pcregrep.
158    
159    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
160        infinitely looping recursion. The bug was that positive lookaheads were not
161        being skipped when checking for a possible empty match (negative lookaheads
162        and both kinds of lookbehind were skipped).
163    
164    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
165        inclusion of <windows.h> to before rather than after the definition of
166        INVALID_FILE_ATTRIBUTES (patch from David Byron).
167    
168    17. Specifying a possessive quantifier with a specific limit for a Unicode
169        character property caused pcre_compile() to compile bad code, which led at
170        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
171        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
172        caused the error; without that there was no problem.
173    
174    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
175    
176    19. Added --enable-pcretest-libreadline.
177    
178    20. In pcrecpp.cc, the variable 'count' was incremented twice in
179        RE::GlobalReplace(). As a result, the number of replacements returned was
180        double what it should be. I removed one of the increments, but Craig sent a
181        later patch that removed the other one (the right fix) and added unit tests
182        that check the return values (which was not done before).
183    
184    21. Several CMake things:
185    
186        (1) Arranged that, when cmake is used on Unix, the libraries end up with
187            the names libpcre and libpcreposix, not just pcre and pcreposix.
188    
189        (2) The above change means that pcretest and pcregrep are now correctly
190            linked with the newly-built libraries, not previously installed ones.
191    
192        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
193    
194    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
195        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
196        UTF-8 newline character). The key issue is that the pattern starts .*;
197        this means that the match must be either at the beginning, or after a
198        newline. The bug was in the code for advancing after a failed match and
199        checking that the new position followed a newline. It was not taking
200        account of UTF-8 characters correctly.
201    
202    23. PCRE was behaving differently from Perl in the way it recognized POSIX
203        character classes. PCRE was not treating the sequence [:...:] as a
204        character class unless the ... were all letters. Perl, however, seems to
205        allow any characters between [: and :], though of course it rejects as
206        unknown any "names" that contain non-letters, because all the known class
207        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
208        for example, whereas PCRE did not - it did not recognize a POSIX character
209        class. This seemed a bit dangerous, so the code has been changed to be
210        closer to Perl. The behaviour is not identical to Perl, because PCRE will
211        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
212        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
213        Perl does, and where it didn't before.
214    
215    24. Rewrite so as to remove the single use of %n from pcregrep because in some
216        Windows environments %n is disabled by default.
217    
218    
219    Version 7.4 21-Sep-07
220    ---------------------
221    
222    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
223        means that a class such as [\s] counted as "explicit reference to CR or
224        LF". That isn't really right - the whole point of the change was to try to
225        help when there was an actual mention of one of the two characters. So now
226        the change happens only if \r or \n (or a literal CR or LF) character is
227        encountered.
228    
229    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
230        of both had grown to the point where there were only 3 bits left.
231        Fortunately, there was spare space in the data structure, and so I have
232        moved the internal flags into a new 16-bit field to free up more option
233        bits.
234    
235    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
236        but did not set the internal JCHANGED flag - either of these is enough to
237        control the way the "get" function works - but the PCRE_INFO_JCHANGED
238        facility is supposed to tell if (?J) was ever used, so now (?J) at the
239        start sets both bits.
240    
241    4.  Added options (at build time, compile time, exec time) to change \R from
242        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
243    
244    5.  doc/pcresyntax.html was missing from the distribution.
245    
246    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
247        compatibility, even though it is no longer used.
248    
249    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
250        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
251        windows.h file is present (where different names are used). [This was
252        reversed later after testing - see 16 below.]
253    
254    8.  Changed all #include <config.h> to #include "config.h". There were also
255        some further <pcre.h> cases that I changed to "pcre.h".
256    
257    9.  When pcregrep was used with the --colour option, it missed the line ending
258        sequence off the lines that it output.
259    
260    10. It was pointed out to me that arrays of string pointers cause lots of
261        relocations when a shared library is dynamically loaded. A technique of
262        using a single long string with a table of offsets can drastically reduce
263        these. I have refactored PCRE in four places to do this. The result is
264        dramatic:
265    
266          Originally:                          290
267          After changing UCP table:            187
268          After changing error message table:   43
269          After changing table of "verbs"       36
270          After changing table of Posix names   22
271    
272        Thanks to the folks working on Gregex for glib for this insight.
273    
274    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
275        unicode-properties was also set.
276    
277    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
278    
279    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
280        checked only for CRLF.
281    
282    14. Added casts to pcretest.c to avoid compiler warnings.
283    
284    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
285    
286    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
287        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
288        entirely. This removes changes made in 7 above.
289    
290    17. The CMake files have been updated, and there is now more information about
291        building with CMake in the NON-UNIX-USE document.
292    
293    
294    Version 7.3 28-Aug-07
295  ---------------------  ---------------------
296    
297   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 388  Version 7.3 09-Aug-07
388      the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the      the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
389      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
390      does: it's just the validity check that is more restrictive.      does: it's just the validity check that is more restrictive.
391    
392  16. Inserted checks for integer overflows during escape sequence (backslash)  16. Inserted checks for integer overflows during escape sequence (backslash)
393      processing, and also fixed erroneous offset values for syntax errors during      processing, and also fixed erroneous offset values for syntax errors during
394      backslash processing.      backslash processing.
395    
396  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)
397      for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".      for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
398    
399  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"
400      caused an overrun.      caused an overrun.
401    
402  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
403      something other than just ASCII characters) inside a group that had an      something other than just ASCII characters) inside a group that had an
404      unlimited repeat caused a loop at compile time (while checking to see      unlimited repeat caused a loop at compile time (while checking to see
405      whether the group could match an empty string).      whether the group could match an empty string).
406    
407  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,
408      [\P{Any}] did so. (Error in the code for printing property names.)      [\P{Any}] did so. (Error in the code for printing property names.)
   
 21. An orphan \E inside a character class could cause a crash.  
409    
410  22. A repeated capturing bracket such as (A)? could cause a wild memory  21. An orphan \E inside a character class could cause a crash.
411    
412    22. A repeated capturing bracket such as (A)? could cause a wild memory
413      reference during compilation.      reference during compilation.
414    
415  23. There are several functions in pcre_compile() that scan along a compiled  23. There are several functions in pcre_compile() that scan along a compiled
416      expression for various reasons (e.g. to see if it's fixed length for look      expression for various reasons (e.g. to see if it's fixed length for look
417      behind). There were bugs in these functions when a repeated \p or \P was      behind). There were bugs in these functions when a repeated \p or \P was
418      present in the pattern. These operators have additional parameters compared      present in the pattern. These operators have additional parameters compared
419      with \d, etc, and these were not being taken into account when moving along      with \d, etc, and these were not being taken into account when moving along
420      the compiled data. Specifically:      the compiled data. Specifically:
421    
422      (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed      (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
423          length.          length.
424    
425      (b) An item such as \pL+ within a repeated group could cause crashes or      (b) An item such as \pL+ within a repeated group could cause crashes or
426          loops.          loops.
427    
428      (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect      (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
429          "reference to non-existent subpattern" error.          "reference to non-existent subpattern" error.
430    
431        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
432    
433  24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte  24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
434      characters were involved (for example /\S{2}/8g with "A\x{a3}BC").      characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
435    
436    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
437    
438    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
439        character were causing crashes (broken optimization).
440    
441    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
442        \p or \P) caused a compile-time loop.
443    
444    28. More problems have arisen in unanchored patterns when CRLF is a valid line
445        break. For example, the unstudied pattern [\r\n]A does not match the string
446        "\r\nA" because change 7.0/46 below moves the current point on by two
447        characters after failing to match at the start. However, the pattern \nA
448        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
449        the same is true. There doesn't seem any very clean way out of this, but
450        what I have chosen to do makes the common cases work: PCRE now takes note
451        of whether there can be an explicit match for \r or \n anywhere in the
452        pattern, and if so, 7.0/46 no longer applies. As part of this change,
453        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
454        pattern has explicit CR or LF references.
455    
456    29. Added (*CR) etc for changing newline setting at start of pattern.
457    
458    
459  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07

Legend:
Removed from v.219  
changed lines
  Added in v.325

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12