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

Diff of /code/trunk/ChangeLog

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

revision 336 by ph10, Sat Apr 12 15:59:03 2008 UTC revision 407 by ph10, Mon Mar 23 15:29:18 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    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
95        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
96        included within another project.
97    
98    24. Steven Van Ingelgem's patches to add more options to the CMake support,
99        slightly modified by me:
100    
101          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
102              not building pcregrep.
103    
104          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
105              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
106    
107    
108    Version 7.8 05-Sep-08
109    ---------------------
110    
111    1.  Replaced UCP searching code with optimized version as implemented for Ad
112        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
113        stage table and inline lookup instead of a function, giving speed ups of 2
114        to 5 times on some simple patterns that I tested. Permission was given to
115        distribute the MultiStage2.py script that generates the tables (it's not in
116        the tarball, but is in the Subversion repository).
117    
118    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
119        scripts.
120    
121    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
122        a group with a zero qualifier. The result of the study could be incorrect,
123        or the function might crash, depending on the pattern.
124    
125    4.  Caseless matching was not working for non-ASCII characters in back
126        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
127        It now works when Unicode Property Support is available.
128    
129    5.  In pcretest, an escape such as \x{de} in the data was always generating
130        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
131        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
132        truncation.
133    
134    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
135    
136    7.  Added two (int) casts to pcregrep when printing the difference of two
137        pointers, in case they are 64-bit values.
138    
139    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
140        test 2 if it fails.
141    
142    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
143        and a #define of that name to empty if it is not externally set. This is to
144        allow users of MSVC to set it if necessary.
145    
146    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
147        the convenience functions in the pcre_get.c source file.
148    
149    11. An option change at the start of a pattern that had top-level alternatives
150        could cause overwriting and/or a crash. This command provoked a crash in
151        some environments:
152    
153          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
154    
155        This potential security problem was recorded as CVE-2008-2371.
156    
157    12. For a pattern where the match had to start at the beginning or immediately
158        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
159        pcre_dfa_exec() could read past the end of the passed subject if there was
160        no match. To help with detecting such bugs (e.g. with valgrind), I modified
161        pcretest so that it places the subject at the end of its malloc-ed buffer.
162    
163    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
164        exec() might read past the end of the data buffer in UTF-8 mode.
165    
166    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
167        the data contained the byte 0x85 as part of a UTF-8 character within its
168        first line. This applied both to normal and DFA matching.
169    
170    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
171        /^[^d]*?$/8 failed to match "abc".
172    
173    16. Added a missing copyright notice to pcrecpp_internal.h.
174    
175    17. Make it more clear in the documentation that values returned from
176        pcre_exec() in ovector are byte offsets, not character counts.
177    
178    18. Tidied a few places to stop certain compilers from issuing warnings.
179    
180    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
181        supplied by Stefan Weber. I made a further small update for 7.8 because
182        there is a change of source arrangements: the pcre_searchfuncs.c module is
183        replaced by pcre_ucd.c.
184    
185    
186    Version 7.7 07-May-08
187  ---------------------  ---------------------
188    
189  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
190      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
191      done by checking for the strtoq, strtoll, and _strtoi64 functions.      done by checking for the strtoq, strtoll, and _strtoi64 functions.
192    
193  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
194      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
195      it in the RE class. (See also #8 below.)      it in the RE class. (See also #8 below.)
196    
197  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
198      Lopes.      Lopes.
199    
200  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
201    
202      (1) The include/exclude patterns were being applied to the whole pathnames      (1) The include/exclude patterns were being applied to the whole pathnames
203          of files, instead of just to the final components.          of files, instead of just to the final components.
204    
205      (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
206          skipped unless they satisfied the include/exclude conditions. This is          skipped unless they satisfied the include/exclude conditions. This is
207          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
208          pcregrep specification - which I improved to make it absolutely clear).          pcregrep specification - which I improved to make it absolutely clear).
209          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
210          apply the include/exclude patterns to regular files.          apply the include/exclude patterns to regular files.
211    
212  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
213      --exclude_dir in the tests to avoid scanning .svn directories.      --exclude_dir in the tests to avoid scanning .svn directories.
214    
215  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
216      NUL character as backslash + 0 rather than backslash + NUL, because PCRE      NUL character as backslash + 0 rather than backslash + NUL, because PCRE
217      doesn't support NULs in patterns.      doesn't support NULs in patterns.
218    
219  7.  Added some missing "const"s to declarations of static tables in  7.  Added some missing "const"s to declarations of static tables in
220      pcre_compile.c and pcre_dfa_exec.c.      pcre_compile.c and pcre_dfa_exec.c.
221    
222  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
223      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
224      first patch. And a third patch - this was a messy problem.)      first patch. And a third patch - this was a messy problem.)
225    
226  9.  Applied Craig's patch to remove the use of push_back().  9.  Applied Craig's patch to remove the use of push_back().
227    
228  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
229      matching function regexec().      matching function regexec().
230    
231  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',
232      which, however, unlike Perl's \g{...}, are subroutine calls, not back      which, however, unlike Perl's \g{...}, are subroutine calls, not back
233      references. PCRE supports relative numbers with this syntax (I don't think      references. PCRE supports relative numbers with this syntax (I don't think
234      Oniguruma does).      Oniguruma does).
235    
236  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
237      omitted from the compiled regex. However, this means that if the group      omitted from the compiled regex. However, this means that if the group
238      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
239      (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
240      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
241      time.      time.
242    
243  13. Added the PCRE_JAVASCRIPT_COMPAT option. This currently does two things:  13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
244        to the way PCRE behaves:
245    
246      (a) A lone ] character is dis-allowed (Perl treats it as data).      (a) A lone ] character is dis-allowed (Perl treats it as data).
247      (b) A back reference to an unmatched subpattern matches an empty string  
248        (b) A back reference to an unmatched subpattern matches an empty string
249          (Perl fails the current match path).          (Perl fails the current match path).
250    
251        (c) A data ] in a character class must be notated as \] because if the
252            first data character in a class is ], it defines an empty class. (In
253            Perl it is not possible to have an empty class.) The empty class []
254            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
255            The negative empty class [^] matches any one character, independently
256            of the DOTALL setting.
257    
258    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
259        non-existent subpattern following a character class starting with ']' and
260        containing () gave an internal compiling error instead of "reference to
261        non-existent subpattern". Fortunately, when the pattern did exist, the
262        compiled code was correct. (When scanning forwards to check for the
263        existencd of the subpattern, it was treating the data ']' as terminating
264        the class, so got the count wrong. When actually compiling, the reference
265        was subsequently set up correctly.)
266    
267    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
268        it was being rejected as not supported by pcre_dfa_exec(), even though
269        other assertions are supported. I have made pcre_dfa_exec() support
270        (*FAIL).
271    
272    16. The implementation of 13c above involved the invention of a new opcode,
273        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
274        cannot be changed at match time, I realized I could make a small
275        improvement to matching performance by compiling OP_ALLANY instead of
276        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
277        on the OP_ANY path.
278    
279    17. Compiling pcretest on Windows with readline support failed without the
280        following two fixes: (1) Make the unistd.h include conditional on
281        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
282    
283    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
284        ncurses library to be included for pcretest when ReadLine support is
285        requested, but also to allow for it to be overridden. This patch came from
286        Daniel Bergström.
287    
288    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
289        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
290        any errors with the current Unicode tables. Thanks to Peter Kankowski for
291        spotting this.
292    
293    
294  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08
295  ---------------------  ---------------------

Legend:
Removed from v.336  
changed lines
  Added in v.407

  ViewVC Help
Powered by ViewVC 1.1.5