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

Diff of /code/trunk/ChangeLog

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

revision 344 by ph10, Tue Apr 22 09:16:15 2008 UTC revision 385 by ph10, Sun Mar 8 16:56:58 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.7 05-Mar-08  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    
55    Version 7.8 05-Sep-08
56    ---------------------
57    
58    1.  Replaced UCP searching code with optimized version as implemented for Ad
59        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
60        stage table and inline lookup instead of a function, giving speed ups of 2
61        to 5 times on some simple patterns that I tested. Permission was given to
62        distribute the MultiStage2.py script that generates the tables (it's not in
63        the tarball, but is in the Subversion repository).
64    
65    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
66        scripts.
67    
68    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
69        a group with a zero qualifier. The result of the study could be incorrect,
70        or the function might crash, depending on the pattern.
71    
72    4.  Caseless matching was not working for non-ASCII characters in back
73        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
74        It now works when Unicode Property Support is available.
75    
76    5.  In pcretest, an escape such as \x{de} in the data was always generating
77        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
78        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
79        truncation.
80    
81    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
82    
83    7.  Added two (int) casts to pcregrep when printing the difference of two
84        pointers, in case they are 64-bit values.
85    
86    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
87        test 2 if it fails.
88    
89    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
90        and a #define of that name to empty if it is not externally set. This is to
91        allow users of MSVC to set it if necessary.
92    
93    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
94        the convenience functions in the pcre_get.c source file.
95    
96    11. An option change at the start of a pattern that had top-level alternatives
97        could cause overwriting and/or a crash. This command provoked a crash in
98        some environments:
99    
100          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
101    
102        This potential security problem was recorded as CVE-2008-2371.
103    
104    12. For a pattern where the match had to start at the beginning or immediately
105        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
106        pcre_dfa_exec() could read past the end of the passed subject if there was
107        no match. To help with detecting such bugs (e.g. with valgrind), I modified
108        pcretest so that it places the subject at the end of its malloc-ed buffer.
109    
110    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
111        exec() might read past the end of the data buffer in UTF-8 mode.
112    
113    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
114        the data contained the byte 0x85 as part of a UTF-8 character within its
115        first line. This applied both to normal and DFA matching.
116    
117    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
118        /^[^d]*?$/8 failed to match "abc".
119    
120    16. Added a missing copyright notice to pcrecpp_internal.h.
121    
122    17. Make it more clear in the documentation that values returned from
123        pcre_exec() in ovector are byte offsets, not character counts.
124    
125    18. Tidied a few places to stop certain compilers from issuing warnings.
126    
127    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
128        supplied by Stefan Weber. I made a further small update for 7.8 because
129        there is a change of source arrangements: the pcre_searchfuncs.c module is
130        replaced by pcre_ucd.c.
131    
132    
133    Version 7.7 07-May-08
134  ---------------------  ---------------------
135    
136  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
137      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
138      done by checking for the strtoq, strtoll, and _strtoi64 functions.      done by checking for the strtoq, strtoll, and _strtoi64 functions.
139    
140  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
141      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
142      it in the RE class. (See also #8 below.)      it in the RE class. (See also #8 below.)
143    
144  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
145      Lopes.      Lopes.
146    
147  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
148    
149      (1) The include/exclude patterns were being applied to the whole pathnames      (1) The include/exclude patterns were being applied to the whole pathnames
150          of files, instead of just to the final components.          of files, instead of just to the final components.
151    
152      (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
153          skipped unless they satisfied the include/exclude conditions. This is          skipped unless they satisfied the include/exclude conditions. This is
154          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
155          pcregrep specification - which I improved to make it absolutely clear).          pcregrep specification - which I improved to make it absolutely clear).
156          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
157          apply the include/exclude patterns to regular files.          apply the include/exclude patterns to regular files.
158    
159  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
160      --exclude_dir in the tests to avoid scanning .svn directories.      --exclude_dir in the tests to avoid scanning .svn directories.
161    
162  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
163      NUL character as backslash + 0 rather than backslash + NUL, because PCRE      NUL character as backslash + 0 rather than backslash + NUL, because PCRE
164      doesn't support NULs in patterns.      doesn't support NULs in patterns.
165    
166  7.  Added some missing "const"s to declarations of static tables in  7.  Added some missing "const"s to declarations of static tables in
167      pcre_compile.c and pcre_dfa_exec.c.      pcre_compile.c and pcre_dfa_exec.c.
168    
169  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
170      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
171      first patch. And a third patch - this was a messy problem.)      first patch. And a third patch - this was a messy problem.)
172    
173  9.  Applied Craig's patch to remove the use of push_back().  9.  Applied Craig's patch to remove the use of push_back().
174    
175  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
176      matching function regexec().      matching function regexec().
177    
178  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',
179      which, however, unlike Perl's \g{...}, are subroutine calls, not back      which, however, unlike Perl's \g{...}, are subroutine calls, not back
180      references. PCRE supports relative numbers with this syntax (I don't think      references. PCRE supports relative numbers with this syntax (I don't think
181      Oniguruma does).      Oniguruma does).
182    
183  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
184      omitted from the compiled regex. However, this means that if the group      omitted from the compiled regex. However, this means that if the group
185      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
186      (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
187      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
188      time.      time.
189    
190  13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes  13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
191      to the way PCRE behaves:      to the way PCRE behaves:
192    
193      (a) A lone ] character is dis-allowed (Perl treats it as data).      (a) A lone ] character is dis-allowed (Perl treats it as data).
194    
195      (b) A back reference to an unmatched subpattern matches an empty string      (b) A back reference to an unmatched subpattern matches an empty string
196          (Perl fails the current match path).          (Perl fails the current match path).
197    
198      (c) A data ] in a character class must be notated as \] because if the      (c) A data ] in a character class must be notated as \] because if the
199          first data character in a class is ], it defines an empty class. (In          first data character in a class is ], it defines an empty class. (In
200          Perl it is not possible to have an empty class.) The empty class []          Perl it is not possible to have an empty class.) The empty class []
201          never matches; it forces failure and is equivalent to (*FAIL) or (?!).          never matches; it forces failure and is equivalent to (*FAIL) or (?!).
202          The negative empty class [^] matches any one character, independently          The negative empty class [^] matches any one character, independently
203          of the DOTALL setting.          of the DOTALL setting.
204    
205  14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a  14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
206      non-existent subpattern following a character class starting with ']' and      non-existent subpattern following a character class starting with ']' and
207      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
208      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
209      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
210      existencd of the subpattern, it was treating the data ']' as terminating      existencd of the subpattern, it was treating the data ']' as terminating
211      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
212      was subsequently set up correctly.)      was subsequently set up correctly.)
213    
214  15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;  15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
215      it was being rejected as not supported by pcre_dfa_exec(), even though      it was being rejected as not supported by pcre_dfa_exec(), even though
216      other assertions are supported. I have made pcre_dfa_exec() support      other assertions are supported. I have made pcre_dfa_exec() support
217      (*FAIL).      (*FAIL).
218    
219  16. The implementation of 13c above involved the invention of a new opcode,  16. The implementation of 13c above involved the invention of a new opcode,
220      OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s      OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
221      cannot be changed at match time, I realized I could make a small      cannot be changed at match time, I realized I could make a small
222      improvement to matching performance by compiling OP_ALLANY instead of      improvement to matching performance by compiling OP_ALLANY instead of
223      OP_ANY for "." when DOTALL was set, and then removing the runtime tests      OP_ANY for "." when DOTALL was set, and then removing the runtime tests
224      on the OP_ANY path.      on the OP_ANY path.
225    
226  17. Compiling pcretest on Windows with readline support failed without the  17. Compiling pcretest on Windows with readline support failed without the
227      following two fixes: (1) Make the unistd.h include conditional on      following two fixes: (1) Make the unistd.h include conditional on
228      HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.      HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
229    
230  18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the  18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
231      ncurses library to be included for pcretest when ReadLine support is      ncurses library to be included for pcretest when ReadLine support is
232      requested, but also to allow for it to be overridden. This patch came from      requested, but also to allow for it to be overridden. This patch came from
233      Daniel Bergström.      Daniel Bergström.
234    
235    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
236        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
237        any errors with the current Unicode tables. Thanks to Peter Kankowski for
238        spotting this.
239    
240    
241  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08

Legend:
Removed from v.344  
changed lines
  Added in v.385

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12