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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.326  
changed lines
  Added in v.402

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12