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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.208  
changed lines
  Added in v.324

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12