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

Diff of /code/trunk/ChangeLog

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

revision 220 by ph10, Thu Aug 16 13:29:39 2007 UTC revision 361 by ph10, Thu Jul 10 16:03:28 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 16-Aug-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    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
18        a group with a zero qualifier. The result of the study could be incorrect,
19        or the function might crash, depending on the pattern.
20    
21    4.  Caseless matching was not working for non-ASCII characters in back
22        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
23        It now works when Unicode Property Support is available.
24    
25    5.  In pcretest, an escape such as \x{de} in the data was always generating
26        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
27        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
28        truncation.
29    
30    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
31    
32    7.  Added two (int) casts to pcregrep when printing the difference of two
33        pointers, in case they are 64-bit values.
34    
35    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
36        test 2 if it fails.
37    
38    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
39        and a #define of that name to empty if it is not externally set. This is to
40        allow users of MSVC to set it if necessary.
41    
42    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
43        the convenience functions in the pcre_get.c source file.
44    
45    11. An option change at the start of a pattern that had top-level alternatives
46        could cause overwriting and/or a crash. This command provoked a crash in
47        some environments:
48    
49          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
50    
51        This potential security problem was recorded as CVE-2008-2371.
52    
53    12. For a pattern where the match had to start at the beginning or immediately
54        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
55        pcre_dfa_exec() could read past the end of the passed subject if there was
56        no match. To help with detecting such bugs (e.g. with valgrind), I modified
57        pcretest so that it places the subject at the end of its malloc-ed buffer.
58    
59    
60    Version 7.7 07-May-08
61    ---------------------
62    
63    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
64        a string to a long long, pretend we don't even have a long long." This is
65        done by checking for the strtoq, strtoll, and _strtoi64 functions.
66    
67    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
68        pre-7.6 versions, which defined a global no_arg variable instead of putting
69        it in the RE class. (See also #8 below.)
70    
71    3.  Remove a line of dead code, identified by coverity and reported by Nuno
72        Lopes.
73    
74    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
75    
76        (1) The include/exclude patterns were being applied to the whole pathnames
77            of files, instead of just to the final components.
78    
79        (2) If there was more than one level of directory, the subdirectories were
80            skipped unless they satisfied the include/exclude conditions. This is
81            inconsistent with GNU grep (and could even be seen as contrary to the
82            pcregrep specification - which I improved to make it absolutely clear).
83            The action now is always to scan all levels of directory, and just
84            apply the include/exclude patterns to regular files.
85    
86    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
87        --exclude_dir in the tests to avoid scanning .svn directories.
88    
89    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
90        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
91        doesn't support NULs in patterns.
92    
93    7.  Added some missing "const"s to declarations of static tables in
94        pcre_compile.c and pcre_dfa_exec.c.
95    
96    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
97        caused by fix #2  above. (Subsequently also a second patch to fix the
98        first patch. And a third patch - this was a messy problem.)
99    
100    9.  Applied Craig's patch to remove the use of push_back().
101    
102    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
103        matching function regexec().
104    
105    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
106        which, however, unlike Perl's \g{...}, are subroutine calls, not back
107        references. PCRE supports relative numbers with this syntax (I don't think
108        Oniguruma does).
109    
110    12. Previously, a group with a zero repeat such as (...){0} was completely
111        omitted from the compiled regex. However, this means that if the group
112        was called as a subroutine from elsewhere in the pattern, things went wrong
113        (an internal error was given). Such groups are now left in the compiled
114        pattern, with a new opcode that causes them to be skipped at execution
115        time.
116    
117    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
118        to the way PCRE behaves:
119    
120        (a) A lone ] character is dis-allowed (Perl treats it as data).
121    
122        (b) A back reference to an unmatched subpattern matches an empty string
123            (Perl fails the current match path).
124    
125        (c) A data ] in a character class must be notated as \] because if the
126            first data character in a class is ], it defines an empty class. (In
127            Perl it is not possible to have an empty class.) The empty class []
128            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
129            The negative empty class [^] matches any one character, independently
130            of the DOTALL setting.
131    
132    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
133        non-existent subpattern following a character class starting with ']' and
134        containing () gave an internal compiling error instead of "reference to
135        non-existent subpattern". Fortunately, when the pattern did exist, the
136        compiled code was correct. (When scanning forwards to check for the
137        existencd of the subpattern, it was treating the data ']' as terminating
138        the class, so got the count wrong. When actually compiling, the reference
139        was subsequently set up correctly.)
140    
141    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
142        it was being rejected as not supported by pcre_dfa_exec(), even though
143        other assertions are supported. I have made pcre_dfa_exec() support
144        (*FAIL).
145    
146    16. The implementation of 13c above involved the invention of a new opcode,
147        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
148        cannot be changed at match time, I realized I could make a small
149        improvement to matching performance by compiling OP_ALLANY instead of
150        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
151        on the OP_ANY path.
152    
153    17. Compiling pcretest on Windows with readline support failed without the
154        following two fixes: (1) Make the unistd.h include conditional on
155        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
156    
157    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
158        ncurses library to be included for pcretest when ReadLine support is
159        requested, but also to allow for it to be overridden. This patch came from
160        Daniel Bergström.
161    
162    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
163        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
164        any errors with the current Unicode tables. Thanks to Peter Kankowski for
165        spotting this.
166    
167    
168    Version 7.6 28-Jan-08
169    ---------------------
170    
171    1.  A character class containing a very large number of characters with
172        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
173        overflow.
174    
175    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
176        HAVE_LONG_LONG is not defined.
177    
178    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
179        bring them up to date and include new features. This patch includes:
180    
181        - Fixed PH's badly added libz and libbz2 support.
182        - Fixed a problem with static linking.
183        - Added pcredemo. [But later removed - see 7 below.]
184        - Fixed dftables problem and added an option.
185        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
186            HAVE_LONG_LONG.
187        - Added readline support for pcretest.
188        - Added an listing of the option settings after cmake has run.
189    
190    4.  A user submitted a patch to Makefile that makes it easy to create
191        "pcre.dll" under mingw when using Configure/Make. I added stuff to
192        Makefile.am that cause it to include this special target, without
193        affecting anything else. Note that the same mingw target plus all
194        the other distribution libraries and programs are now supported
195        when configuring with CMake (see 6 below) instead of with
196        Configure/Make.
197    
198    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
199        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
200        exported in the Windows port". It has not yet been confirmed that the patch
201        solves the problem, but it does no harm.
202    
203    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
204        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
205        with CMake, and also correct the comment about stack recursion.
206    
207    7.  Remove the automatic building of pcredemo from the ./configure system and
208        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
209        of a program that users should build themselves after PCRE is installed, so
210        building it automatically is not really right. What is more, it gave
211        trouble in some build environments.
212    
213    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
214    
215    
216    Version 7.5 10-Jan-08
217    ---------------------
218    
219    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
220        values in parens when parsing an RE using the C++ wrapper."
221    
222    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
223        Characters greater than 255 were excluded from the class instead of being
224        included.
225    
226    3.  The same bug as (2) above applied to negated POSIX classes such as
227        [:^space:].
228    
229    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
230        defined or documented. It seems to have been a typo for PCRE_STATIC, so
231        I have changed it.
232    
233    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
234        first named subpattern) and a construct such as (?&a) would reference the
235        first named subpattern whose name started with "a" (in other words, the
236        length check was missing). Both these problems are fixed. "Subpattern name
237        expected" is now given for (?&) (a zero-length name), and this patch also
238        makes it give the same error for \k'' (previously it complained that that
239        was a reference to a non-existent subpattern).
240    
241    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
242        this is right because (?- can be followed by option settings as well as by
243        digits. I have, however, made the messages clearer.
244    
245    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
246        than the number used in the conditional) now cause a compile-time error.
247        This is actually not compatible with Perl, which accepts such patterns, but
248        treats the conditional as always being FALSE (as PCRE used to), but it
249        seems to me that giving a diagnostic is better.
250    
251    8.  Change "alphameric" to the more common word "alphanumeric" in comments
252        and messages.
253    
254    9.  Fix two occurrences of "backslash" in comments that should have been
255        "backspace".
256    
257    10. Remove two redundant lines of code that can never be obeyed (their function
258        was moved elsewhere).
259    
260    11. The program that makes PCRE's Unicode character property table had a bug
261        which caused it to generate incorrect table entries for sequences of
262        characters that have the same character type, but are in different scripts.
263        It amalgamated them into a single range, with the script of the first of
264        them. In other words, some characters were in the wrong script. There were
265        thirteen such cases, affecting characters in the following ranges:
266    
267          U+002b0 - U+002c1
268          U+0060c - U+0060d
269          U+0061e - U+00612
270          U+0064b - U+0065e
271          U+0074d - U+0076d
272          U+01800 - U+01805
273          U+01d00 - U+01d77
274          U+01d9b - U+01dbf
275          U+0200b - U+0200f
276          U+030fc - U+030fe
277          U+03260 - U+0327f
278          U+0fb46 - U+0fbb1
279          U+10450 - U+1049d
280    
281    12. The -o option (show only the matching part of a line) for pcregrep was not
282        compatible with GNU grep in that, if there was more than one match in a
283        line, it showed only the first of them. It now behaves in the same way as
284        GNU grep.
285    
286    13. If the -o and -v options were combined for pcregrep, it printed a blank
287        line for every non-matching line. GNU grep prints nothing, and pcregrep now
288        does the same. The return code can be used to tell if there were any
289        non-matching lines.
290    
291    14. Added --file-offsets and --line-offsets to pcregrep.
292    
293    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
294        infinitely looping recursion. The bug was that positive lookaheads were not
295        being skipped when checking for a possible empty match (negative lookaheads
296        and both kinds of lookbehind were skipped).
297    
298    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
299        inclusion of <windows.h> to before rather than after the definition of
300        INVALID_FILE_ATTRIBUTES (patch from David Byron).
301    
302    17. Specifying a possessive quantifier with a specific limit for a Unicode
303        character property caused pcre_compile() to compile bad code, which led at
304        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
305        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
306        caused the error; without that there was no problem.
307    
308    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
309    
310    19. Added --enable-pcretest-libreadline.
311    
312    20. In pcrecpp.cc, the variable 'count' was incremented twice in
313        RE::GlobalReplace(). As a result, the number of replacements returned was
314        double what it should be. I removed one of the increments, but Craig sent a
315        later patch that removed the other one (the right fix) and added unit tests
316        that check the return values (which was not done before).
317    
318    21. Several CMake things:
319    
320        (1) Arranged that, when cmake is used on Unix, the libraries end up with
321            the names libpcre and libpcreposix, not just pcre and pcreposix.
322    
323        (2) The above change means that pcretest and pcregrep are now correctly
324            linked with the newly-built libraries, not previously installed ones.
325    
326        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
327    
328    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
329        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
330        UTF-8 newline character). The key issue is that the pattern starts .*;
331        this means that the match must be either at the beginning, or after a
332        newline. The bug was in the code for advancing after a failed match and
333        checking that the new position followed a newline. It was not taking
334        account of UTF-8 characters correctly.
335    
336    23. PCRE was behaving differently from Perl in the way it recognized POSIX
337        character classes. PCRE was not treating the sequence [:...:] as a
338        character class unless the ... were all letters. Perl, however, seems to
339        allow any characters between [: and :], though of course it rejects as
340        unknown any "names" that contain non-letters, because all the known class
341        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
342        for example, whereas PCRE did not - it did not recognize a POSIX character
343        class. This seemed a bit dangerous, so the code has been changed to be
344        closer to Perl. The behaviour is not identical to Perl, because PCRE will
345        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
346        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
347        Perl does, and where it didn't before.
348    
349    24. Rewrite so as to remove the single use of %n from pcregrep because in some
350        Windows environments %n is disabled by default.
351    
352    
353    Version 7.4 21-Sep-07
354    ---------------------
355    
356    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
357        means that a class such as [\s] counted as "explicit reference to CR or
358        LF". That isn't really right - the whole point of the change was to try to
359        help when there was an actual mention of one of the two characters. So now
360        the change happens only if \r or \n (or a literal CR or LF) character is
361        encountered.
362    
363    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
364        of both had grown to the point where there were only 3 bits left.
365        Fortunately, there was spare space in the data structure, and so I have
366        moved the internal flags into a new 16-bit field to free up more option
367        bits.
368    
369    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
370        but did not set the internal JCHANGED flag - either of these is enough to
371        control the way the "get" function works - but the PCRE_INFO_JCHANGED
372        facility is supposed to tell if (?J) was ever used, so now (?J) at the
373        start sets both bits.
374    
375    4.  Added options (at build time, compile time, exec time) to change \R from
376        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
377    
378    5.  doc/pcresyntax.html was missing from the distribution.
379    
380    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
381        compatibility, even though it is no longer used.
382    
383    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
384        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
385        windows.h file is present (where different names are used). [This was
386        reversed later after testing - see 16 below.]
387    
388    8.  Changed all #include <config.h> to #include "config.h". There were also
389        some further <pcre.h> cases that I changed to "pcre.h".
390    
391    9.  When pcregrep was used with the --colour option, it missed the line ending
392        sequence off the lines that it output.
393    
394    10. It was pointed out to me that arrays of string pointers cause lots of
395        relocations when a shared library is dynamically loaded. A technique of
396        using a single long string with a table of offsets can drastically reduce
397        these. I have refactored PCRE in four places to do this. The result is
398        dramatic:
399    
400          Originally:                          290
401          After changing UCP table:            187
402          After changing error message table:   43
403          After changing table of "verbs"       36
404          After changing table of Posix names   22
405    
406        Thanks to the folks working on Gregex for glib for this insight.
407    
408    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
409        unicode-properties was also set.
410    
411    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
412    
413    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
414        checked only for CRLF.
415    
416    14. Added casts to pcretest.c to avoid compiler warnings.
417    
418    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
419    
420    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
421        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
422        entirely. This removes changes made in 7 above.
423    
424    17. The CMake files have been updated, and there is now more information about
425        building with CMake in the NON-UNIX-USE document.
426    
427    
428    Version 7.3 28-Aug-07
429  ---------------------  ---------------------
430    
431   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 138  Version 7.3 16-Aug-07 Line 562  Version 7.3 16-Aug-07
562      (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
563          "reference to non-existent subpattern" error.          "reference to non-existent subpattern" error.
564    
565        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
566    
567  24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte  24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
568      characters were involved (for example /\S{2}/8g with "A\x{a3}BC").      characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
569    
570    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
571    
572    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
573        character were causing crashes (broken optimization).
574    
575    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
576        \p or \P) caused a compile-time loop.
577    
578    28. More problems have arisen in unanchored patterns when CRLF is a valid line
579        break. For example, the unstudied pattern [\r\n]A does not match the string
580        "\r\nA" because change 7.0/46 below moves the current point on by two
581        characters after failing to match at the start. However, the pattern \nA
582        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
583        the same is true. There doesn't seem any very clean way out of this, but
584        what I have chosen to do makes the common cases work: PCRE now takes note
585        of whether there can be an explicit match for \r or \n anywhere in the
586        pattern, and if so, 7.0/46 no longer applies. As part of this change,
587        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
588        pattern has explicit CR or LF references.
589    
590    29. Added (*CR) etc for changing newline setting at start of pattern.
591    
592    
593  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
594  ---------------------  ---------------------

Legend:
Removed from v.220  
changed lines
  Added in v.361

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12