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

Diff of /code/trunk/ChangeLog

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

revision 284 by ph10, Fri Dec 7 20:01:16 2007 UTC revision 388 by ph10, Wed Mar 11 17:03:17 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.5 12-Nov-07  Version 7.9 xx-xxx-09
5    ---------------------
6    
7    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
8        (pcretest), all targets were linked against these libraries. This included
9        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
10        libraries. This caused unwanted dependencies to be created. This problem
11        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
12        pcretest is linked with readline.
13    
14    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
15        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
16        moved outside it again, because FALSE and TRUE are already defined in AIX,
17        but BOOL is not.
18    
19    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
20        PCRE_MATCH_LIMIT_RETURSION values as ints, when they should be long ints.
21    
22    4.  The pcregrep documentation said spaces were inserted as well as colons (or
23        hyphens) following file names and line numbers when outputting matching
24        lines. This is not true; no spaces are inserted. I have also clarified the
25        wording for the --colour (or --color) option.
26    
27    5.  In pcregrep, when --colour was used with -o, the list of matching strings
28        was not coloured; this is different to GNU grep, so I have changed it to be
29        the same.
30    
31    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
32        each matching line was coloured. Now it goes on to look for further matches
33        of any of the test patterns, which is the same behaviour as GNU grep.
34    
35    7.  A pattern that could match an empty string could cause pcregrep to loop; it
36        doesn't make sense to accept an empty string match in pcregrep, so I have
37        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
38        seems to be how GNU grep behaves.
39    
40    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
41        start or after a newline", because the conditional assertion was not being
42        correctly handled. The rule now is that both the assertion and what follows
43        in the first alternative must satisfy the test.
44    
45    9.  If auto-callout was enabled in a pattern with a conditional group, PCRE
46        could crash during matching.
47    
48    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
49        used for matching.
50    
51    11. Unicode property support in character classes was not working for
52        characters (bytes) greater than 127 when not in UTF-8 mode.
53    
54    12. Added the -M command line option to pcretest.
55    
56    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
57    
58    
59    Version 7.8 05-Sep-08
60    ---------------------
61    
62    1.  Replaced UCP searching code with optimized version as implemented for Ad
63        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
64        stage table and inline lookup instead of a function, giving speed ups of 2
65        to 5 times on some simple patterns that I tested. Permission was given to
66        distribute the MultiStage2.py script that generates the tables (it's not in
67        the tarball, but is in the Subversion repository).
68    
69    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
70        scripts.
71    
72    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
73        a group with a zero qualifier. The result of the study could be incorrect,
74        or the function might crash, depending on the pattern.
75    
76    4.  Caseless matching was not working for non-ASCII characters in back
77        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
78        It now works when Unicode Property Support is available.
79    
80    5.  In pcretest, an escape such as \x{de} in the data was always generating
81        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
82        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
83        truncation.
84    
85    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
86    
87    7.  Added two (int) casts to pcregrep when printing the difference of two
88        pointers, in case they are 64-bit values.
89    
90    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
91        test 2 if it fails.
92    
93    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
94        and a #define of that name to empty if it is not externally set. This is to
95        allow users of MSVC to set it if necessary.
96    
97    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
98        the convenience functions in the pcre_get.c source file.
99    
100    11. An option change at the start of a pattern that had top-level alternatives
101        could cause overwriting and/or a crash. This command provoked a crash in
102        some environments:
103    
104          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
105    
106        This potential security problem was recorded as CVE-2008-2371.
107    
108    12. For a pattern where the match had to start at the beginning or immediately
109        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
110        pcre_dfa_exec() could read past the end of the passed subject if there was
111        no match. To help with detecting such bugs (e.g. with valgrind), I modified
112        pcretest so that it places the subject at the end of its malloc-ed buffer.
113    
114    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
115        exec() might read past the end of the data buffer in UTF-8 mode.
116    
117    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
118        the data contained the byte 0x85 as part of a UTF-8 character within its
119        first line. This applied both to normal and DFA matching.
120    
121    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
122        /^[^d]*?$/8 failed to match "abc".
123    
124    16. Added a missing copyright notice to pcrecpp_internal.h.
125    
126    17. Make it more clear in the documentation that values returned from
127        pcre_exec() in ovector are byte offsets, not character counts.
128    
129    18. Tidied a few places to stop certain compilers from issuing warnings.
130    
131    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
132        supplied by Stefan Weber. I made a further small update for 7.8 because
133        there is a change of source arrangements: the pcre_searchfuncs.c module is
134        replaced by pcre_ucd.c.
135    
136    
137    Version 7.7 07-May-08
138    ---------------------
139    
140    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
141        a string to a long long, pretend we don't even have a long long." This is
142        done by checking for the strtoq, strtoll, and _strtoi64 functions.
143    
144    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
145        pre-7.6 versions, which defined a global no_arg variable instead of putting
146        it in the RE class. (See also #8 below.)
147    
148    3.  Remove a line of dead code, identified by coverity and reported by Nuno
149        Lopes.
150    
151    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
152    
153        (1) The include/exclude patterns were being applied to the whole pathnames
154            of files, instead of just to the final components.
155    
156        (2) If there was more than one level of directory, the subdirectories were
157            skipped unless they satisfied the include/exclude conditions. This is
158            inconsistent with GNU grep (and could even be seen as contrary to the
159            pcregrep specification - which I improved to make it absolutely clear).
160            The action now is always to scan all levels of directory, and just
161            apply the include/exclude patterns to regular files.
162    
163    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
164        --exclude_dir in the tests to avoid scanning .svn directories.
165    
166    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
167        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
168        doesn't support NULs in patterns.
169    
170    7.  Added some missing "const"s to declarations of static tables in
171        pcre_compile.c and pcre_dfa_exec.c.
172    
173    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
174        caused by fix #2  above. (Subsequently also a second patch to fix the
175        first patch. And a third patch - this was a messy problem.)
176    
177    9.  Applied Craig's patch to remove the use of push_back().
178    
179    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
180        matching function regexec().
181    
182    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
183        which, however, unlike Perl's \g{...}, are subroutine calls, not back
184        references. PCRE supports relative numbers with this syntax (I don't think
185        Oniguruma does).
186    
187    12. Previously, a group with a zero repeat such as (...){0} was completely
188        omitted from the compiled regex. However, this means that if the group
189        was called as a subroutine from elsewhere in the pattern, things went wrong
190        (an internal error was given). Such groups are now left in the compiled
191        pattern, with a new opcode that causes them to be skipped at execution
192        time.
193    
194    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
195        to the way PCRE behaves:
196    
197        (a) A lone ] character is dis-allowed (Perl treats it as data).
198    
199        (b) A back reference to an unmatched subpattern matches an empty string
200            (Perl fails the current match path).
201    
202        (c) A data ] in a character class must be notated as \] because if the
203            first data character in a class is ], it defines an empty class. (In
204            Perl it is not possible to have an empty class.) The empty class []
205            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
206            The negative empty class [^] matches any one character, independently
207            of the DOTALL setting.
208    
209    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
210        non-existent subpattern following a character class starting with ']' and
211        containing () gave an internal compiling error instead of "reference to
212        non-existent subpattern". Fortunately, when the pattern did exist, the
213        compiled code was correct. (When scanning forwards to check for the
214        existencd of the subpattern, it was treating the data ']' as terminating
215        the class, so got the count wrong. When actually compiling, the reference
216        was subsequently set up correctly.)
217    
218    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
219        it was being rejected as not supported by pcre_dfa_exec(), even though
220        other assertions are supported. I have made pcre_dfa_exec() support
221        (*FAIL).
222    
223    16. The implementation of 13c above involved the invention of a new opcode,
224        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
225        cannot be changed at match time, I realized I could make a small
226        improvement to matching performance by compiling OP_ALLANY instead of
227        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
228        on the OP_ANY path.
229    
230    17. Compiling pcretest on Windows with readline support failed without the
231        following two fixes: (1) Make the unistd.h include conditional on
232        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
233    
234    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
235        ncurses library to be included for pcretest when ReadLine support is
236        requested, but also to allow for it to be overridden. This patch came from
237        Daniel Bergström.
238    
239    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
240        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
241        any errors with the current Unicode tables. Thanks to Peter Kankowski for
242        spotting this.
243    
244    
245    Version 7.6 28-Jan-08
246    ---------------------
247    
248    1.  A character class containing a very large number of characters with
249        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
250        overflow.
251    
252    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
253        HAVE_LONG_LONG is not defined.
254    
255    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
256        bring them up to date and include new features. This patch includes:
257    
258        - Fixed PH's badly added libz and libbz2 support.
259        - Fixed a problem with static linking.
260        - Added pcredemo. [But later removed - see 7 below.]
261        - Fixed dftables problem and added an option.
262        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
263            HAVE_LONG_LONG.
264        - Added readline support for pcretest.
265        - Added an listing of the option settings after cmake has run.
266    
267    4.  A user submitted a patch to Makefile that makes it easy to create
268        "pcre.dll" under mingw when using Configure/Make. I added stuff to
269        Makefile.am that cause it to include this special target, without
270        affecting anything else. Note that the same mingw target plus all
271        the other distribution libraries and programs are now supported
272        when configuring with CMake (see 6 below) instead of with
273        Configure/Make.
274    
275    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
276        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
277        exported in the Windows port". It has not yet been confirmed that the patch
278        solves the problem, but it does no harm.
279    
280    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
281        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
282        with CMake, and also correct the comment about stack recursion.
283    
284    7.  Remove the automatic building of pcredemo from the ./configure system and
285        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
286        of a program that users should build themselves after PCRE is installed, so
287        building it automatically is not really right. What is more, it gave
288        trouble in some build environments.
289    
290    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
291    
292    
293    Version 7.5 10-Jan-08
294  ---------------------  ---------------------
295    
296  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
297      values in parens when parsing an RE using the C++ wrapper."      values in parens when parsing an RE using the C++ wrapper."
298    
299  2.  Negative specials like \S did not work in character classes in UTF-8 mode.  2.  Negative specials like \S did not work in character classes in UTF-8 mode.
300      Characters greater than 255 were excluded from the class instead of being      Characters greater than 255 were excluded from the class instead of being
301      included.      included.
302    
303  3.  The same bug as (2) above applied to negated POSIX classes such as  3.  The same bug as (2) above applied to negated POSIX classes such as
304      [:^space:].      [:^space:].
305    
306  4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it  4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
307      defined or documented. It seems to have been a typo for PCRE_STATIC, so      defined or documented. It seems to have been a typo for PCRE_STATIC, so
308      I have changed it.      I have changed it.
309    
310  5.  The construct (?&) was not diagnosed as a syntax error (it referenced the  5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
311      first named subpattern) and a construct such as (?&a) would reference the      first named subpattern) and a construct such as (?&a) would reference the
312      first named subpattern whose name started with "a" (in other words, the      first named subpattern whose name started with "a" (in other words, the
313      length check was missing). Both these problems are fixed. "Subpattern name      length check was missing). Both these problems are fixed. "Subpattern name
314      expected" is now given for (?&) (a zero-length name), and this patch also      expected" is now given for (?&) (a zero-length name), and this patch also
315      makes it give the same error for \k'' (previously it complained that that      makes it give the same error for \k'' (previously it complained that that
316      was a reference to a non-existent subpattern).      was a reference to a non-existent subpattern).
317    
318  6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;  6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
319      this is right because (?- can be followed by option settings as well as by      this is right because (?- can be followed by option settings as well as by
320      digits. I have, however, made the messages clearer.      digits. I have, however, made the messages clearer.
321    
322  7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns  7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
323      than the number used in the conditional) now cause a compile-time error.      than the number used in the conditional) now cause a compile-time error.
324      This is actually not compatible with Perl, which accepts such patterns, but      This is actually not compatible with Perl, which accepts such patterns, but
325      treats the conditional as always being FALSE (as PCRE used to), but it      treats the conditional as always being FALSE (as PCRE used to), but it
326      seems to me that giving a diagnostic is better.      seems to me that giving a diagnostic is better.
327    
328  8.  Change "alphameric" to the more common word "alphanumeric" in comments  8.  Change "alphameric" to the more common word "alphanumeric" in comments
329      and messages.      and messages.
330    
331  9.  Fix two occurrences of "backslash" in comments that should have been  9.  Fix two occurrences of "backslash" in comments that should have been
332      "backspace".      "backspace".
333    
334  10. Remove two redundant lines of code that can never be obeyed (their function  10. Remove two redundant lines of code that can never be obeyed (their function
335      was moved elsewhere).      was moved elsewhere).
336    
337  11. The program that makes PCRE's Unicode character property table had a bug  11. The program that makes PCRE's Unicode character property table had a bug
338      which caused it to generate incorrect table entries for sequences of      which caused it to generate incorrect table entries for sequences of
339      characters that have the same character type, but are in different scripts.      characters that have the same character type, but are in different scripts.
340      It amalgamated them into a single range, with the script of the first of      It amalgamated them into a single range, with the script of the first of
341      them. In other words, some characters were in the wrong script. There were      them. In other words, some characters were in the wrong script. There were
342      thirteen such cases, affecting characters in the following ranges:      thirteen such cases, affecting characters in the following ranges:
343    
344        U+002b0 - U+002c1        U+002b0 - U+002c1
345        U+0060c - U+0060d        U+0060c - U+0060d
346        U+0061e - U+00612        U+0061e - U+00612
347        U+0064b - U+0065e        U+0064b - U+0065e
348        U+0074d - U+0076d        U+0074d - U+0076d
349        U+01800 - U+01805        U+01800 - U+01805
# Line 65  Version 7.5 12-Nov-07 Line 354  Version 7.5 12-Nov-07
354        U+03260 - U+0327f        U+03260 - U+0327f
355        U+0fb46 - U+0fbb1        U+0fb46 - U+0fbb1
356        U+10450 - U+1049d        U+10450 - U+1049d
357    
358  12. The -o option (show only the matching part of a line) for pcregrep was not  12. The -o option (show only the matching part of a line) for pcregrep was not
359      compatible with GNU grep in that, if there was more than one match in a      compatible with GNU grep in that, if there was more than one match in a
360      line, it showed only the first of them. It now behaves in the same way as      line, it showed only the first of them. It now behaves in the same way as
361      GNU grep.      GNU grep.
362    
363  13. If the -o and -v options were combined for pcregrep, it printed a blank  13. If the -o and -v options were combined for pcregrep, it printed a blank
364      line for every non-matching line. GNU grep prints nothing, and pcregrep now      line for every non-matching line. GNU grep prints nothing, and pcregrep now
365      does the same. The return code can be used to tell if there were any      does the same. The return code can be used to tell if there were any
366      non-matching lines.      non-matching lines.
367    
368  14. The pattern (?=something)(?R) was not being diagnosed as a potentially  14. Added --file-offsets and --line-offsets to pcregrep.
369    
370    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
371      infinitely looping recursion. The bug was that positive lookaheads were not      infinitely looping recursion. The bug was that positive lookaheads were not
372      being skipped when checking for a possible empty match (negative lookaheads      being skipped when checking for a possible empty match (negative lookaheads
373      and both kinds of lookbehind were skipped).      and both kinds of lookbehind were skipped).
374    
375  15. Fixed two typos in the Windows-only code in pcregrep.c, and moved the  16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
376      inclusion of <windows.h> to before rather than after the definition of      inclusion of <windows.h> to before rather than after the definition of
377      INVALID_FILE_ATTRIBUTES (patch from David Byron).      INVALID_FILE_ATTRIBUTES (patch from David Byron).
378    
379    17. Specifying a possessive quantifier with a specific limit for a Unicode
380        character property caused pcre_compile() to compile bad code, which led at
381        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
382        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
383        caused the error; without that there was no problem.
384    
385    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
386    
387    19. Added --enable-pcretest-libreadline.
388    
389    20. In pcrecpp.cc, the variable 'count' was incremented twice in
390        RE::GlobalReplace(). As a result, the number of replacements returned was
391        double what it should be. I removed one of the increments, but Craig sent a
392        later patch that removed the other one (the right fix) and added unit tests
393        that check the return values (which was not done before).
394    
395    21. Several CMake things:
396    
397        (1) Arranged that, when cmake is used on Unix, the libraries end up with
398            the names libpcre and libpcreposix, not just pcre and pcreposix.
399    
400        (2) The above change means that pcretest and pcregrep are now correctly
401            linked with the newly-built libraries, not previously installed ones.
402    
403        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
404    
405    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
406        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
407        UTF-8 newline character). The key issue is that the pattern starts .*;
408        this means that the match must be either at the beginning, or after a
409        newline. The bug was in the code for advancing after a failed match and
410        checking that the new position followed a newline. It was not taking
411        account of UTF-8 characters correctly.
412    
413    23. PCRE was behaving differently from Perl in the way it recognized POSIX
414        character classes. PCRE was not treating the sequence [:...:] as a
415        character class unless the ... were all letters. Perl, however, seems to
416        allow any characters between [: and :], though of course it rejects as
417        unknown any "names" that contain non-letters, because all the known class
418        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
419        for example, whereas PCRE did not - it did not recognize a POSIX character
420        class. This seemed a bit dangerous, so the code has been changed to be
421        closer to Perl. The behaviour is not identical to Perl, because PCRE will
422        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
423        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
424        Perl does, and where it didn't before.
425    
426    24. Rewrite so as to remove the single use of %n from pcregrep because in some
427        Windows environments %n is disabled by default.
428    
429    
430  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07
431  ---------------------  ---------------------

Legend:
Removed from v.284  
changed lines
  Added in v.388

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12