ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.313  
changed lines
  Added in v.418

  ViewVC Help
Powered by ViewVC 1.1.5