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

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

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12