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

Diff of /code/trunk/ChangeLog

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

revision 340 by ph10, Fri Apr 18 20:00:21 2008 UTC revision 373 by ph10, Fri Sep 5 10:25:46 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.7 05-Mar-08  Version 7.8 25-Aug-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    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
60        exec() might read past the end of the data buffer in UTF-8 mode.
61    
62    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
63        the data contained the byte 0x85 as part of a UTF-8 character within its
64        first line. This applied both to normal and DFA matching.
65    
66    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
67        /^[^d]*?$/8 failed to match "abc".
68    
69    16. Added a missing copyright notice to pcrecpp_internal.h.
70    
71    17. Make it more clear in the documentation that values returned from
72        pcre_exec() in ovector are byte offsets, not character counts.
73    
74    18. Tidied a few places to stop certain compilers from issuing warnings.
75    
76    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
77        supplied by Stefan Weber. I made a further small update for 7.8 because
78        there is a change of source arrangements: the pcre_searchfuncs.c module is
79        replaced by pcre_ucd.c.
80    
81    
82    Version 7.7 07-May-08
83  ---------------------  ---------------------
84    
85  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
86      a string to a long long, pretend we don't even have a long long." This is      a string to a long long, pretend we don't even have a long long." This is
87      done by checking for the strtoq, strtoll, and _strtoi64 functions.      done by checking for the strtoq, strtoll, and _strtoi64 functions.
88    
89  2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with  2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
90      pre-7.6 versions, which defined a global no_arg variable instead of putting      pre-7.6 versions, which defined a global no_arg variable instead of putting
91      it in the RE class. (See also #8 below.)      it in the RE class. (See also #8 below.)
92    
93  3.  Remove a line of dead code, identified by coverity and reported by Nuno  3.  Remove a line of dead code, identified by coverity and reported by Nuno
94      Lopes.      Lopes.
95    
96  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
97    
98      (1) The include/exclude patterns were being applied to the whole pathnames      (1) The include/exclude patterns were being applied to the whole pathnames
99          of files, instead of just to the final components.          of files, instead of just to the final components.
100    
101      (2) If there was more than one level of directory, the subdirectories were      (2) If there was more than one level of directory, the subdirectories were
102          skipped unless they satisfied the include/exclude conditions. This is          skipped unless they satisfied the include/exclude conditions. This is
103          inconsistent with GNU grep (and could even be seen as contrary to the          inconsistent with GNU grep (and could even be seen as contrary to the
104          pcregrep specification - which I improved to make it absolutely clear).          pcregrep specification - which I improved to make it absolutely clear).
105          The action now is always to scan all levels of directory, and just          The action now is always to scan all levels of directory, and just
106          apply the include/exclude patterns to regular files.          apply the include/exclude patterns to regular files.
107    
108  5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used  5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
109      --exclude_dir in the tests to avoid scanning .svn directories.      --exclude_dir in the tests to avoid scanning .svn directories.
110    
111  6.  Applied Craig's patch to the QuoteMeta function so that it escapes the  6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
112      NUL character as backslash + 0 rather than backslash + NUL, because PCRE      NUL character as backslash + 0 rather than backslash + NUL, because PCRE
113      doesn't support NULs in patterns.      doesn't support NULs in patterns.
114    
115  7.  Added some missing "const"s to declarations of static tables in  7.  Added some missing "const"s to declarations of static tables in
116      pcre_compile.c and pcre_dfa_exec.c.      pcre_compile.c and pcre_dfa_exec.c.
117    
118  8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was  8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
119      caused by fix #2  above. (Subsequently also a second patch to fix the      caused by fix #2  above. (Subsequently also a second patch to fix the
120      first patch. And a third patch - this was a messy problem.)      first patch. And a third patch - this was a messy problem.)
121    
122  9.  Applied Craig's patch to remove the use of push_back().  9.  Applied Craig's patch to remove the use of push_back().
123    
124  10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX  10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
125      matching function regexec().      matching function regexec().
126    
127  11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',  11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
128      which, however, unlike Perl's \g{...}, are subroutine calls, not back      which, however, unlike Perl's \g{...}, are subroutine calls, not back
129      references. PCRE supports relative numbers with this syntax (I don't think      references. PCRE supports relative numbers with this syntax (I don't think
130      Oniguruma does).      Oniguruma does).
131    
132  12. Previously, a group with a zero repeat such as (...){0} was completely  12. Previously, a group with a zero repeat such as (...){0} was completely
133      omitted from the compiled regex. However, this means that if the group      omitted from the compiled regex. However, this means that if the group
134      was called as a subroutine from elsewhere in the pattern, things went wrong      was called as a subroutine from elsewhere in the pattern, things went wrong
135      (an internal error was given). Such groups are now left in the compiled      (an internal error was given). Such groups are now left in the compiled
136      pattern, with a new opcode that causes them to be skipped at execution      pattern, with a new opcode that causes them to be skipped at execution
137      time.      time.
138    
139  13. Added the PCRE_JAVASCRIPT_COMPAT option. This currently does two things:  13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
140        to the way PCRE behaves:
141    
142      (a) A lone ] character is dis-allowed (Perl treats it as data).      (a) A lone ] character is dis-allowed (Perl treats it as data).
143      (b) A back reference to an unmatched subpattern matches an empty string  
144        (b) A back reference to an unmatched subpattern matches an empty string
145          (Perl fails the current match path).          (Perl fails the current match path).
146    
147  14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a      (c) A data ] in a character class must be notated as \] because if the
148            first data character in a class is ], it defines an empty class. (In
149            Perl it is not possible to have an empty class.) The empty class []
150            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
151            The negative empty class [^] matches any one character, independently
152            of the DOTALL setting.
153    
154    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
155      non-existent subpattern following a character class starting with ']' and      non-existent subpattern following a character class starting with ']' and
156      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
157      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
158      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
159      existencd of the subpattern, it was treating the data ']' as terminating      existencd of the subpattern, it was treating the data ']' as terminating
160      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
161      was subsequently set up correctly.)      was subsequently set up correctly.)
162    
163    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
164        it was being rejected as not supported by pcre_dfa_exec(), even though
165        other assertions are supported. I have made pcre_dfa_exec() support
166        (*FAIL).
167    
168    16. The implementation of 13c above involved the invention of a new opcode,
169        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
170        cannot be changed at match time, I realized I could make a small
171        improvement to matching performance by compiling OP_ALLANY instead of
172        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
173        on the OP_ANY path.
174    
175    17. Compiling pcretest on Windows with readline support failed without the
176        following two fixes: (1) Make the unistd.h include conditional on
177        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
178    
179    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
180        ncurses library to be included for pcretest when ReadLine support is
181        requested, but also to allow for it to be overridden. This patch came from
182        Daniel Bergström.
183    
184    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
185        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
186        any errors with the current Unicode tables. Thanks to Peter Kankowski for
187        spotting this.
188    
189    
190  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08
191  ---------------------  ---------------------
Legend:
Removed from v.340  
changed lines
  Added in v.373
webmaster@exim.org
 ViewVC Help
Powered by ViewVC 1.1.12