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

Diff of /code/trunk/ChangeLog

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

revision 341 by ph10, Sat Apr 19 16:41:04 2008 UTC revision 438 by ph10, Sun Sep 6 20:00:47 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.7 05-Mar-08  Version 8.00 ??-???-??
5    ----------------------
6    
7    1.  The table for translating pcre_compile() error codes into POSIX error codes
8        was out-of-date, and there was no check on the pcre_compile() error code
9        being within the table. This could lead to an OK return being given in
10        error.
11    
12    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
13        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
14        in a Windows environment.
15    
16    3.  The pcregrep --count option prints the count for each file even when it is
17        zero, as does GNU grep. However, pcregrep was also printing all files when
18        --files-with-matches was added. Now, when both options are given, it prints
19        counts only for those files that have at least one match. (GNU grep just
20        prints the file name in this circumstance, but including the count seems
21        more useful - otherwise, why use --count?) Also ensured that the
22        combination -clh just lists non-zero counts, with no names.
23    
24    4.  The long form of the pcregrep -F option was incorrectly implemented as
25        --fixed_strings instead of --fixed-strings. This is an incompatible change,
26        but it seems right to fix it, and I didn't think it was worth preserving
27        the old behaviour.
28    
29    5.  The command line items --regex=pattern and --regexp=pattern were not
30        recognized by pcregrep, which required --regex pattern or --regexp pattern
31        (with a space rather than an '='). The man page documented the '=' forms,
32        which are compatible with GNU grep; these now work.
33    
34    6.  No libpcreposix.pc file was created for pkg-config; there was just
35        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
36    
37    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
38        when UCP support is not needed, by modifying the Python script that
39        generates it from Unicode data files. This should not matter if the module
40        is correctly used as a library, but I received one complaint about 50K of
41        unwanted data. My guess is that the person linked everything into his
42        program rather than using a library. Anyway, it does no harm.
43    
44    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
45        was a minimum greater than 1 for a wide character in a possessive
46        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
47        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
48        character. Chaos in the form of incorrect output or a compiling loop could
49        result.
50    
51    9.  The restrictions on what a pattern can contain when partial matching is
52        requested for pcre_exec() have been removed. All patterns can now be
53        partially matched by this function. In addition, if there are at least two
54        slots in the offset vector, the offset of the earliest inspected character
55        for the match and the offset of the end of the subject are set in them when
56        PCRE_ERROR_PARTIAL is returned.
57    
58    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
59        synonymous with PCRE_PARTIAL, for backwards compatibility, and
60        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
61        and may be more useful for multi-segment matching, especially with
62        pcre_exec().
63    
64    11. Partial matching with pcre_exec() is now more intuitive. A partial match
65        used to be given if ever the end of the subject was reached; now it is
66        given only if matching could not proceed because another character was
67        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
68        string "Z", which now yields "no match" instead of "partial match". In the
69        case of pcre_dfa_exec(), "no match" is given if every matching path for the
70        final character ended with (*FAIL).
71    
72    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
73        if the pattern had a "must contain" character that was already found in the
74        earlier partial match, unless partial matching was again requested. For
75        example, with the pattern /dog.(body)?/, the "must contain" character is
76        "g". If the first part-match was for the string "dog", restarting with
77        "sbody" failed. This bug has been fixed.
78    
79    13. The string returned by pcre_dfa_exec() after a partial match has been
80        changed so that it starts at the first inspected character rather than the
81        first character of the match. This makes a difference only if the pattern
82        starts with a lookbehind assertion or \b or \B (\K is not supported by
83        pcre_dfa_exec()). It's an incompatible change, but it makes the two
84        matching functions compatible, and I think it's the right thing to do.
85    
86    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
87        so that the demonstration program is easily available in environments where
88        PCRE has not been installed from source.
89    
90    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
91        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
92        library.
93    
94    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
95        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
96        is not the first non-POSIX option to be added. Clearly some people find
97        these options useful.
98    
99    17. If a caller to the POSIX matching function regexec() passes a non-zero
100        value for nmatch with a NULL value for pmatch, the value of
101        nmatch is forced to zero.
102    
103    18. RunGrepTest did not have a test for the availability of the -u option of
104        the diff command, as RunTest does. It now checks in the same way as
105        RunTest, and also checks for the -b option.
106    
107    19. If an odd number of negated classes containing just a single character
108        interposed, within parentheses, between a forward reference to a named
109        subpattern and the definition of the subpattern, compilation crashed with
110        an internal error, complaining that it could not find the referenced
111        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
112        [The bug was that it was starting one character too far in when skipping
113        over the character class, thus treating the ] as data rather than
114        terminating the class. This meant it could skip too much.]
115    
116    
117    Version 7.9 11-Apr-09
118    ---------------------
119    
120    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
121        (pcretest), all targets were linked against these libraries. This included
122        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
123        libraries. This caused unwanted dependencies to be created. This problem
124        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
125        pcretest is linked with readline.
126    
127    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
128        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
129        moved outside it again, because FALSE and TRUE are already defined in AIX,
130        but BOOL is not.
131    
132    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
133        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
134    
135    4.  The pcregrep documentation said spaces were inserted as well as colons (or
136        hyphens) following file names and line numbers when outputting matching
137        lines. This is not true; no spaces are inserted. I have also clarified the
138        wording for the --colour (or --color) option.
139    
140    5.  In pcregrep, when --colour was used with -o, the list of matching strings
141        was not coloured; this is different to GNU grep, so I have changed it to be
142        the same.
143    
144    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
145        each matching line was coloured. Now it goes on to look for further matches
146        of any of the test patterns, which is the same behaviour as GNU grep.
147    
148    7.  A pattern that could match an empty string could cause pcregrep to loop; it
149        doesn't make sense to accept an empty string match in pcregrep, so I have
150        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
151        seems to be how GNU grep behaves.
152    
153    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
154        start or after a newline", because the conditional assertion was not being
155        correctly handled. The rule now is that both the assertion and what follows
156        in the first alternative must satisfy the test.
157    
158    9.  If auto-callout was enabled in a pattern with a conditional group whose
159        condition was an assertion, PCRE could crash during matching, both with
160        pcre_exec() and pcre_dfa_exec().
161    
162    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
163        used for matching.
164    
165    11. Unicode property support in character classes was not working for
166        characters (bytes) greater than 127 when not in UTF-8 mode.
167    
168    12. Added the -M command line option to pcretest.
169    
170    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
171    
172    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
173    
174    16. Added comments and documentation about mis-use of no_arg in the C++
175        wrapper.
176    
177    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
178        from Martin Jerabek that uses macro names for all relevant character and
179        string constants.
180    
181    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
182        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
183        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
184        these, but not everybody uses configure.
185    
186    19. A conditional group that had only one branch was not being correctly
187        recognized as an item that could match an empty string. This meant that an
188        enclosing group might also not be so recognized, causing infinite looping
189        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
190        with the subject "ab", where knowledge that the repeated group can match
191        nothing is needed in order to break the loop.
192    
193    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
194        exec(), but without supplying a callout function, matching went wrong.
195    
196    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
197        leak if the size of the offset vector was greater than 30. When the vector
198        is smaller, the saved offsets during recursion go onto a local stack
199        vector, but for larger vectors malloc() is used. It was failing to free
200        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
201        error, in fact).
202    
203    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
204        heapframe that is used only when UTF-8 support is enabled. This caused no
205        problem, but was untidy.
206    
207    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
208        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
209        included within another project.
210    
211    24. Steven Van Ingelgem's patches to add more options to the CMake support,
212        slightly modified by me:
213    
214          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
215              not building pcregrep.
216    
217          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
218              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
219    
220    25. Forward references, both numeric and by name, in patterns that made use of
221        duplicate group numbers, could behave incorrectly or give incorrect errors,
222        because when scanning forward to find the reference group, PCRE was not
223        taking into account the duplicate group numbers. A pattern such as
224        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
225    
226    26. Changed a few more instances of "const unsigned char *" to USPTR, making
227        the feature of a custom pointer more persuasive (as requested by a user).
228    
229    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
230        pcretest.c, inside #ifndefs, because it seems they are sometimes already
231        pre-defined.
232    
233    28. Added support for (*UTF8) at the start of a pattern.
234    
235    29. Arrange for flags added by the "release type" setting in CMake to be shown
236        in the configuration summary.
237    
238    
239    Version 7.8 05-Sep-08
240    ---------------------
241    
242    1.  Replaced UCP searching code with optimized version as implemented for Ad
243        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
244        stage table and inline lookup instead of a function, giving speed ups of 2
245        to 5 times on some simple patterns that I tested. Permission was given to
246        distribute the MultiStage2.py script that generates the tables (it's not in
247        the tarball, but is in the Subversion repository).
248    
249    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
250        scripts.
251    
252    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
253        a group with a zero qualifier. The result of the study could be incorrect,
254        or the function might crash, depending on the pattern.
255    
256    4.  Caseless matching was not working for non-ASCII characters in back
257        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
258        It now works when Unicode Property Support is available.
259    
260    5.  In pcretest, an escape such as \x{de} in the data was always generating
261        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
262        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
263        truncation.
264    
265    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
266    
267    7.  Added two (int) casts to pcregrep when printing the difference of two
268        pointers, in case they are 64-bit values.
269    
270    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
271        test 2 if it fails.
272    
273    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
274        and a #define of that name to empty if it is not externally set. This is to
275        allow users of MSVC to set it if necessary.
276    
277    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
278        the convenience functions in the pcre_get.c source file.
279    
280    11. An option change at the start of a pattern that had top-level alternatives
281        could cause overwriting and/or a crash. This command provoked a crash in
282        some environments:
283    
284          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
285    
286        This potential security problem was recorded as CVE-2008-2371.
287    
288    12. For a pattern where the match had to start at the beginning or immediately
289        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
290        pcre_dfa_exec() could read past the end of the passed subject if there was
291        no match. To help with detecting such bugs (e.g. with valgrind), I modified
292        pcretest so that it places the subject at the end of its malloc-ed buffer.
293    
294    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
295        exec() might read past the end of the data buffer in UTF-8 mode.
296    
297    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
298        the data contained the byte 0x85 as part of a UTF-8 character within its
299        first line. This applied both to normal and DFA matching.
300    
301    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
302        /^[^d]*?$/8 failed to match "abc".
303    
304    16. Added a missing copyright notice to pcrecpp_internal.h.
305    
306    17. Make it more clear in the documentation that values returned from
307        pcre_exec() in ovector are byte offsets, not character counts.
308    
309    18. Tidied a few places to stop certain compilers from issuing warnings.
310    
311    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
312        supplied by Stefan Weber. I made a further small update for 7.8 because
313        there is a change of source arrangements: the pcre_searchfuncs.c module is
314        replaced by pcre_ucd.c.
315    
316    
317    Version 7.7 07-May-08
318  ---------------------  ---------------------
319    
320  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
321      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
322      done by checking for the strtoq, strtoll, and _strtoi64 functions.      done by checking for the strtoq, strtoll, and _strtoi64 functions.
323    
324  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
325      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
326      it in the RE class. (See also #8 below.)      it in the RE class. (See also #8 below.)
327    
328  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
329      Lopes.      Lopes.
330    
331  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
332    
333      (1) The include/exclude patterns were being applied to the whole pathnames      (1) The include/exclude patterns were being applied to the whole pathnames
334          of files, instead of just to the final components.          of files, instead of just to the final components.
335    
336      (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
337          skipped unless they satisfied the include/exclude conditions. This is          skipped unless they satisfied the include/exclude conditions. This is
338          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
339          pcregrep specification - which I improved to make it absolutely clear).          pcregrep specification - which I improved to make it absolutely clear).
340          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
341          apply the include/exclude patterns to regular files.          apply the include/exclude patterns to regular files.
342    
343  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
344      --exclude_dir in the tests to avoid scanning .svn directories.      --exclude_dir in the tests to avoid scanning .svn directories.
345    
346  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
347      NUL character as backslash + 0 rather than backslash + NUL, because PCRE      NUL character as backslash + 0 rather than backslash + NUL, because PCRE
348      doesn't support NULs in patterns.      doesn't support NULs in patterns.
349    
350  7.  Added some missing "const"s to declarations of static tables in  7.  Added some missing "const"s to declarations of static tables in
351      pcre_compile.c and pcre_dfa_exec.c.      pcre_compile.c and pcre_dfa_exec.c.
352    
353  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
354      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
355      first patch. And a third patch - this was a messy problem.)      first patch. And a third patch - this was a messy problem.)
356    
357  9.  Applied Craig's patch to remove the use of push_back().  9.  Applied Craig's patch to remove the use of push_back().
358    
359  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
360      matching function regexec().      matching function regexec().
361    
362  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',
363      which, however, unlike Perl's \g{...}, are subroutine calls, not back      which, however, unlike Perl's \g{...}, are subroutine calls, not back
364      references. PCRE supports relative numbers with this syntax (I don't think      references. PCRE supports relative numbers with this syntax (I don't think
365      Oniguruma does).      Oniguruma does).
366    
367  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
368      omitted from the compiled regex. However, this means that if the group      omitted from the compiled regex. However, this means that if the group
369      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
370      (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
371      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
372      time.      time.
373    
374  13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes  13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
375      to the way PCRE behaves:      to the way PCRE behaves:
376    
377      (a) A lone ] character is dis-allowed (Perl treats it as data).      (a) A lone ] character is dis-allowed (Perl treats it as data).
378    
379      (b) A back reference to an unmatched subpattern matches an empty string      (b) A back reference to an unmatched subpattern matches an empty string
380          (Perl fails the current match path).          (Perl fails the current match path).
381    
382      (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
383          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
384          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 []
385          never matches; it forces failure and is equivalent to (*FAIL) or (?!).          never matches; it forces failure and is equivalent to (*FAIL) or (?!).
386          The negative empty class [^] matches any one character, independently          The negative empty class [^] matches any one character, independently
387          of the DOTALL setting.          of the DOTALL setting.
388    
389  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
390      non-existent subpattern following a character class starting with ']' and      non-existent subpattern following a character class starting with ']' and
391      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
392      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
393      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
394      existencd of the subpattern, it was treating the data ']' as terminating      existencd of the subpattern, it was treating the data ']' as terminating
395      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
396      was subsequently set up correctly.)      was subsequently set up correctly.)
397    
398  15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;  15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
399      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
400      other assertions are supported. I have made pcre_dfa_exec() support      other assertions are supported. I have made pcre_dfa_exec() support
401      (*FAIL).      (*FAIL).
402    
403    16. The implementation of 13c above involved the invention of a new opcode,
404        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
405        cannot be changed at match time, I realized I could make a small
406        improvement to matching performance by compiling OP_ALLANY instead of
407        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
408        on the OP_ANY path.
409    
410    17. Compiling pcretest on Windows with readline support failed without the
411        following two fixes: (1) Make the unistd.h include conditional on
412        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
413    
414    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
415        ncurses library to be included for pcretest when ReadLine support is
416        requested, but also to allow for it to be overridden. This patch came from
417        Daniel Bergström.
418    
419    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
420        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
421        any errors with the current Unicode tables. Thanks to Peter Kankowski for
422        spotting this.
423    
424    
425  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08

Legend:
Removed from v.341  
changed lines
  Added in v.438

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12