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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.285  
changed lines
  Added in v.383

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12