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

Diff of /code/trunk/ChangeLog

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

revision 206 by ph10, Fri Aug 3 14:53:04 2007 UTC revision 351 by ph10, Fri Jul 4 18:27:16 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 05-Jul-07  Version 8.0 02 Jul-08
5    ---------------------
6    
7    1.  Replaced UCP searching code with optimized version as implemented for Ad
8        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
9        stage table and inline lookup instead of a function, giving speed ups of 2
10        to 5 times on some simple patterns that I tested. Permission was given to
11        distribute the MultiStage2.py script that generates the tables (it's not in
12        the tarball, but is in the Subversion repository).
13    
14    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
15        scripts.
16    
17    
18    Version 7.7 07-May-08
19    ---------------------
20    
21    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
22        a string to a long long, pretend we don't even have a long long." This is
23        done by checking for the strtoq, strtoll, and _strtoi64 functions.
24    
25    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
26        pre-7.6 versions, which defined a global no_arg variable instead of putting
27        it in the RE class. (See also #8 below.)
28    
29    3.  Remove a line of dead code, identified by coverity and reported by Nuno
30        Lopes.
31    
32    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
33    
34        (1) The include/exclude patterns were being applied to the whole pathnames
35            of files, instead of just to the final components.
36    
37        (2) If there was more than one level of directory, the subdirectories were
38            skipped unless they satisfied the include/exclude conditions. This is
39            inconsistent with GNU grep (and could even be seen as contrary to the
40            pcregrep specification - which I improved to make it absolutely clear).
41            The action now is always to scan all levels of directory, and just
42            apply the include/exclude patterns to regular files.
43    
44    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
45        --exclude_dir in the tests to avoid scanning .svn directories.
46    
47    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
48        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
49        doesn't support NULs in patterns.
50    
51    7.  Added some missing "const"s to declarations of static tables in
52        pcre_compile.c and pcre_dfa_exec.c.
53    
54    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
55        caused by fix #2  above. (Subsequently also a second patch to fix the
56        first patch. And a third patch - this was a messy problem.)
57    
58    9.  Applied Craig's patch to remove the use of push_back().
59    
60    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
61        matching function regexec().
62    
63    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
64        which, however, unlike Perl's \g{...}, are subroutine calls, not back
65        references. PCRE supports relative numbers with this syntax (I don't think
66        Oniguruma does).
67    
68    12. Previously, a group with a zero repeat such as (...){0} was completely
69        omitted from the compiled regex. However, this means that if the group
70        was called as a subroutine from elsewhere in the pattern, things went wrong
71        (an internal error was given). Such groups are now left in the compiled
72        pattern, with a new opcode that causes them to be skipped at execution
73        time.
74    
75    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
76        to the way PCRE behaves:
77    
78        (a) A lone ] character is dis-allowed (Perl treats it as data).
79    
80        (b) A back reference to an unmatched subpattern matches an empty string
81            (Perl fails the current match path).
82    
83        (c) A data ] in a character class must be notated as \] because if the
84            first data character in a class is ], it defines an empty class. (In
85            Perl it is not possible to have an empty class.) The empty class []
86            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
87            The negative empty class [^] matches any one character, independently
88            of the DOTALL setting.
89    
90    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
91        non-existent subpattern following a character class starting with ']' and
92        containing () gave an internal compiling error instead of "reference to
93        non-existent subpattern". Fortunately, when the pattern did exist, the
94        compiled code was correct. (When scanning forwards to check for the
95        existencd of the subpattern, it was treating the data ']' as terminating
96        the class, so got the count wrong. When actually compiling, the reference
97        was subsequently set up correctly.)
98    
99    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
100        it was being rejected as not supported by pcre_dfa_exec(), even though
101        other assertions are supported. I have made pcre_dfa_exec() support
102        (*FAIL).
103    
104    16. The implementation of 13c above involved the invention of a new opcode,
105        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
106        cannot be changed at match time, I realized I could make a small
107        improvement to matching performance by compiling OP_ALLANY instead of
108        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
109        on the OP_ANY path.
110    
111    17. Compiling pcretest on Windows with readline support failed without the
112        following two fixes: (1) Make the unistd.h include conditional on
113        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
114    
115    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
116        ncurses library to be included for pcretest when ReadLine support is
117        requested, but also to allow for it to be overridden. This patch came from
118        Daniel Bergström.
119    
120    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
121        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
122        any errors with the current Unicode tables. Thanks to Peter Kankowski for
123        spotting this.
124    
125    
126    Version 7.6 28-Jan-08
127    ---------------------
128    
129    1.  A character class containing a very large number of characters with
130        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
131        overflow.
132    
133    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
134        HAVE_LONG_LONG is not defined.
135    
136    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
137        bring them up to date and include new features. This patch includes:
138    
139        - Fixed PH's badly added libz and libbz2 support.
140        - Fixed a problem with static linking.
141        - Added pcredemo. [But later removed - see 7 below.]
142        - Fixed dftables problem and added an option.
143        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
144            HAVE_LONG_LONG.
145        - Added readline support for pcretest.
146        - Added an listing of the option settings after cmake has run.
147    
148    4.  A user submitted a patch to Makefile that makes it easy to create
149        "pcre.dll" under mingw when using Configure/Make. I added stuff to
150        Makefile.am that cause it to include this special target, without
151        affecting anything else. Note that the same mingw target plus all
152        the other distribution libraries and programs are now supported
153        when configuring with CMake (see 6 below) instead of with
154        Configure/Make.
155    
156    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
157        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
158        exported in the Windows port". It has not yet been confirmed that the patch
159        solves the problem, but it does no harm.
160    
161    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
162        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
163        with CMake, and also correct the comment about stack recursion.
164    
165    7.  Remove the automatic building of pcredemo from the ./configure system and
166        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
167        of a program that users should build themselves after PCRE is installed, so
168        building it automatically is not really right. What is more, it gave
169        trouble in some build environments.
170    
171    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
172    
173    
174    Version 7.5 10-Jan-08
175    ---------------------
176    
177    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
178        values in parens when parsing an RE using the C++ wrapper."
179    
180    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
181        Characters greater than 255 were excluded from the class instead of being
182        included.
183    
184    3.  The same bug as (2) above applied to negated POSIX classes such as
185        [:^space:].
186    
187    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
188        defined or documented. It seems to have been a typo for PCRE_STATIC, so
189        I have changed it.
190    
191    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
192        first named subpattern) and a construct such as (?&a) would reference the
193        first named subpattern whose name started with "a" (in other words, the
194        length check was missing). Both these problems are fixed. "Subpattern name
195        expected" is now given for (?&) (a zero-length name), and this patch also
196        makes it give the same error for \k'' (previously it complained that that
197        was a reference to a non-existent subpattern).
198    
199    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
200        this is right because (?- can be followed by option settings as well as by
201        digits. I have, however, made the messages clearer.
202    
203    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
204        than the number used in the conditional) now cause a compile-time error.
205        This is actually not compatible with Perl, which accepts such patterns, but
206        treats the conditional as always being FALSE (as PCRE used to), but it
207        seems to me that giving a diagnostic is better.
208    
209    8.  Change "alphameric" to the more common word "alphanumeric" in comments
210        and messages.
211    
212    9.  Fix two occurrences of "backslash" in comments that should have been
213        "backspace".
214    
215    10. Remove two redundant lines of code that can never be obeyed (their function
216        was moved elsewhere).
217    
218    11. The program that makes PCRE's Unicode character property table had a bug
219        which caused it to generate incorrect table entries for sequences of
220        characters that have the same character type, but are in different scripts.
221        It amalgamated them into a single range, with the script of the first of
222        them. In other words, some characters were in the wrong script. There were
223        thirteen such cases, affecting characters in the following ranges:
224    
225          U+002b0 - U+002c1
226          U+0060c - U+0060d
227          U+0061e - U+00612
228          U+0064b - U+0065e
229          U+0074d - U+0076d
230          U+01800 - U+01805
231          U+01d00 - U+01d77
232          U+01d9b - U+01dbf
233          U+0200b - U+0200f
234          U+030fc - U+030fe
235          U+03260 - U+0327f
236          U+0fb46 - U+0fbb1
237          U+10450 - U+1049d
238    
239    12. The -o option (show only the matching part of a line) for pcregrep was not
240        compatible with GNU grep in that, if there was more than one match in a
241        line, it showed only the first of them. It now behaves in the same way as
242        GNU grep.
243    
244    13. If the -o and -v options were combined for pcregrep, it printed a blank
245        line for every non-matching line. GNU grep prints nothing, and pcregrep now
246        does the same. The return code can be used to tell if there were any
247        non-matching lines.
248    
249    14. Added --file-offsets and --line-offsets to pcregrep.
250    
251    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
252        infinitely looping recursion. The bug was that positive lookaheads were not
253        being skipped when checking for a possible empty match (negative lookaheads
254        and both kinds of lookbehind were skipped).
255    
256    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
257        inclusion of <windows.h> to before rather than after the definition of
258        INVALID_FILE_ATTRIBUTES (patch from David Byron).
259    
260    17. Specifying a possessive quantifier with a specific limit for a Unicode
261        character property caused pcre_compile() to compile bad code, which led at
262        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
263        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
264        caused the error; without that there was no problem.
265    
266    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
267    
268    19. Added --enable-pcretest-libreadline.
269    
270    20. In pcrecpp.cc, the variable 'count' was incremented twice in
271        RE::GlobalReplace(). As a result, the number of replacements returned was
272        double what it should be. I removed one of the increments, but Craig sent a
273        later patch that removed the other one (the right fix) and added unit tests
274        that check the return values (which was not done before).
275    
276    21. Several CMake things:
277    
278        (1) Arranged that, when cmake is used on Unix, the libraries end up with
279            the names libpcre and libpcreposix, not just pcre and pcreposix.
280    
281        (2) The above change means that pcretest and pcregrep are now correctly
282            linked with the newly-built libraries, not previously installed ones.
283    
284        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
285    
286    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
287        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
288        UTF-8 newline character). The key issue is that the pattern starts .*;
289        this means that the match must be either at the beginning, or after a
290        newline. The bug was in the code for advancing after a failed match and
291        checking that the new position followed a newline. It was not taking
292        account of UTF-8 characters correctly.
293    
294    23. PCRE was behaving differently from Perl in the way it recognized POSIX
295        character classes. PCRE was not treating the sequence [:...:] as a
296        character class unless the ... were all letters. Perl, however, seems to
297        allow any characters between [: and :], though of course it rejects as
298        unknown any "names" that contain non-letters, because all the known class
299        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
300        for example, whereas PCRE did not - it did not recognize a POSIX character
301        class. This seemed a bit dangerous, so the code has been changed to be
302        closer to Perl. The behaviour is not identical to Perl, because PCRE will
303        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
304        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
305        Perl does, and where it didn't before.
306    
307    24. Rewrite so as to remove the single use of %n from pcregrep because in some
308        Windows environments %n is disabled by default.
309    
310    
311    Version 7.4 21-Sep-07
312    ---------------------
313    
314    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
315        means that a class such as [\s] counted as "explicit reference to CR or
316        LF". That isn't really right - the whole point of the change was to try to
317        help when there was an actual mention of one of the two characters. So now
318        the change happens only if \r or \n (or a literal CR or LF) character is
319        encountered.
320    
321    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
322        of both had grown to the point where there were only 3 bits left.
323        Fortunately, there was spare space in the data structure, and so I have
324        moved the internal flags into a new 16-bit field to free up more option
325        bits.
326    
327    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
328        but did not set the internal JCHANGED flag - either of these is enough to
329        control the way the "get" function works - but the PCRE_INFO_JCHANGED
330        facility is supposed to tell if (?J) was ever used, so now (?J) at the
331        start sets both bits.
332    
333    4.  Added options (at build time, compile time, exec time) to change \R from
334        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
335    
336    5.  doc/pcresyntax.html was missing from the distribution.
337    
338    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
339        compatibility, even though it is no longer used.
340    
341    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
342        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
343        windows.h file is present (where different names are used). [This was
344        reversed later after testing - see 16 below.]
345    
346    8.  Changed all #include <config.h> to #include "config.h". There were also
347        some further <pcre.h> cases that I changed to "pcre.h".
348    
349    9.  When pcregrep was used with the --colour option, it missed the line ending
350        sequence off the lines that it output.
351    
352    10. It was pointed out to me that arrays of string pointers cause lots of
353        relocations when a shared library is dynamically loaded. A technique of
354        using a single long string with a table of offsets can drastically reduce
355        these. I have refactored PCRE in four places to do this. The result is
356        dramatic:
357    
358          Originally:                          290
359          After changing UCP table:            187
360          After changing error message table:   43
361          After changing table of "verbs"       36
362          After changing table of Posix names   22
363    
364        Thanks to the folks working on Gregex for glib for this insight.
365    
366    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
367        unicode-properties was also set.
368    
369    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
370    
371    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
372        checked only for CRLF.
373    
374    14. Added casts to pcretest.c to avoid compiler warnings.
375    
376    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
377    
378    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
379        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
380        entirely. This removes changes made in 7 above.
381    
382    17. The CMake files have been updated, and there is now more information about
383        building with CMake in the NON-UNIX-USE document.
384    
385    
386    Version 7.3 28-Aug-07
387  ---------------------  ---------------------
388    
389   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 446  Version 7.3 05-Jul-07
446      dynamic way, which I have now done. The artificial limitation on group      dynamic way, which I have now done. The artificial limitation on group
447      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
448      the compiled pattern, which depends on the LINK_SIZE setting.      the compiled pattern, which depends on the LINK_SIZE setting.
449    
450  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
451      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
452      functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an      functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
453      empty string.      empty string.
454    
455  11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E  11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
456      instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,      instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
457      because the ] is interpreted as the first data character and the      because the ] is interpreted as the first data character and the
458      terminating ] is not found. PCRE has been made compatible with Perl in this      terminating ] is not found. PCRE has been made compatible with Perl in this
459      regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could      regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
460      cause memory overwriting.      cause memory overwriting.
461    
462  10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty  10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
463      string has been matched (to stop an infinite loop). It was not recognizing      string has been matched (to stop an infinite loop). It was not recognizing
464      a conditional subpattern that could match an empty string if that      a conditional subpattern that could match an empty string if that
465      subpattern was within another subpattern. For example, it looped when      subpattern was within another subpattern. For example, it looped when
466      trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the      trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
467      condition was not nested. This bug has been fixed.      condition was not nested. This bug has been fixed.
468    
469    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
470        past the start of the subject in the presence of bytes with the top bit
471        set, for example "\x8aBCD".
472    
473    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
474        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
475    
476    14. Optimized (?!) to (*FAIL).
477    
478    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
479        This restricts code points to be within the range 0 to 0x10FFFF, excluding
480        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
481        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
482        does: it's just the validity check that is more restrictive.
483    
484    16. Inserted checks for integer overflows during escape sequence (backslash)
485        processing, and also fixed erroneous offset values for syntax errors during
486        backslash processing.
487    
488    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
489        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
490    
491    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
492        caused an overrun.
493    
494    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
495        something other than just ASCII characters) inside a group that had an
496        unlimited repeat caused a loop at compile time (while checking to see
497        whether the group could match an empty string).
498    
499    20. Debugging a pattern containing \p or \P could cause a crash. For example,
500        [\P{Any}] did so. (Error in the code for printing property names.)
501    
502    21. An orphan \E inside a character class could cause a crash.
503    
504    22. A repeated capturing bracket such as (A)? could cause a wild memory
505        reference during compilation.
506    
507    23. There are several functions in pcre_compile() that scan along a compiled
508        expression for various reasons (e.g. to see if it's fixed length for look
509        behind). There were bugs in these functions when a repeated \p or \P was
510        present in the pattern. These operators have additional parameters compared
511        with \d, etc, and these were not being taken into account when moving along
512        the compiled data. Specifically:
513    
514        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
515            length.
516    
517        (b) An item such as \pL+ within a repeated group could cause crashes or
518            loops.
519    
520        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
521            "reference to non-existent subpattern" error.
522    
523        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
524    
525    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
526        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
527    
528    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
529    
530    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
531        character were causing crashes (broken optimization).
532    
533    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
534        \p or \P) caused a compile-time loop.
535    
536    28. More problems have arisen in unanchored patterns when CRLF is a valid line
537        break. For example, the unstudied pattern [\r\n]A does not match the string
538        "\r\nA" because change 7.0/46 below moves the current point on by two
539        characters after failing to match at the start. However, the pattern \nA
540        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
541        the same is true. There doesn't seem any very clean way out of this, but
542        what I have chosen to do makes the common cases work: PCRE now takes note
543        of whether there can be an explicit match for \r or \n anywhere in the
544        pattern, and if so, 7.0/46 no longer applies. As part of this change,
545        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
546        pattern has explicit CR or LF references.
547    
548    29. Added (*CR) etc for changing newline setting at start of pattern.
549    
550    
551  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
552  ---------------------  ---------------------

Legend:
Removed from v.206  
changed lines
  Added in v.351

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12