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

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

  ViewVC Help
Powered by ViewVC 1.1.5