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

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

  ViewVC Help
Powered by ViewVC 1.1.5