/[pcre]/code/tags/pcre-8.01/ChangeLog
ViewVC logotype

Diff of /code/tags/pcre-8.01/ChangeLog

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

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

Legend:
Removed from v.218  
changed lines
  Added in v.331

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12