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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.203  
changed lines
  Added in v.335

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12