ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 314 by ph10, Fri Jan 25 17:09:21 2008 UTC revision 411 by ph10, Fri Apr 10 15:40:21 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.6 21-Jan-08  Version 7.9 10-Apr-09
5    ---------------------
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.
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.
19    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
20        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
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.
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.
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.
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.
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.
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().
49    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
50        used for matching.
52    11. Unicode property support in character classes was not working for
53        characters (bytes) greater than 127 when not in UTF-8 mode.
55    12. Added the -M command line option to pcretest.
57    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
59    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
61    16. Added comments and documentation about mis-use of no_arg in the C++
62        wrapper.
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.
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.
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.
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.
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).
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.
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.
98    24. Steven Van Ingelgem's patches to add more options to the CMake support,
99        slightly modified by me:
101          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
102              not building pcregrep.
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.
107    25. Forward references, both numeric and by name, in patterns that made use of
108        duplicate group numbers, could behave incorrectly or give incorrect errors,
109        because when scanning forward to find the reference group, PCRE was not
110        taking into account the duplicate group numbers. A pattern such as
111        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
113    26. Changed a few more instances of "const unsigned char *" to USPTR, making
114        the feature of a custom pointer more persuasive (as requested by a user).
116    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
117        pcretest.c, inside #ifndefs, because it seems they are sometimes already
118        pre-defined.
122    Version 7.8 05-Sep-08
123    ---------------------
125    1.  Replaced UCP searching code with optimized version as implemented for Ad
126        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
127        stage table and inline lookup instead of a function, giving speed ups of 2
128        to 5 times on some simple patterns that I tested. Permission was given to
129        distribute the MultiStage2.py script that generates the tables (it's not in
130        the tarball, but is in the Subversion repository).
132    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
133        scripts.
135    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
136        a group with a zero qualifier. The result of the study could be incorrect,
137        or the function might crash, depending on the pattern.
139    4.  Caseless matching was not working for non-ASCII characters in back
140        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
141        It now works when Unicode Property Support is available.
143    5.  In pcretest, an escape such as \x{de} in the data was always generating
144        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
145        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
146        truncation.
148    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
150    7.  Added two (int) casts to pcregrep when printing the difference of two
151        pointers, in case they are 64-bit values.
153    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
154        test 2 if it fails.
156    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
157        and a #define of that name to empty if it is not externally set. This is to
158        allow users of MSVC to set it if necessary.
160    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
161        the convenience functions in the pcre_get.c source file.
163    11. An option change at the start of a pattern that had top-level alternatives
164        could cause overwriting and/or a crash. This command provoked a crash in
165        some environments:
167          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
169        This potential security problem was recorded as CVE-2008-2371.
171    12. For a pattern where the match had to start at the beginning or immediately
172        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
173        pcre_dfa_exec() could read past the end of the passed subject if there was
174        no match. To help with detecting such bugs (e.g. with valgrind), I modified
175        pcretest so that it places the subject at the end of its malloc-ed buffer.
177    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
178        exec() might read past the end of the data buffer in UTF-8 mode.
180    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
181        the data contained the byte 0x85 as part of a UTF-8 character within its
182        first line. This applied both to normal and DFA matching.
184    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
185        /^[^d]*?$/8 failed to match "abc".
187    16. Added a missing copyright notice to pcrecpp_internal.h.
189    17. Make it more clear in the documentation that values returned from
190        pcre_exec() in ovector are byte offsets, not character counts.
192    18. Tidied a few places to stop certain compilers from issuing warnings.
194    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
195        supplied by Stefan Weber. I made a further small update for 7.8 because
196        there is a change of source arrangements: the pcre_searchfuncs.c module is
197        replaced by pcre_ucd.c.
200    Version 7.7 07-May-08
201    ---------------------
203    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
204        a string to a long long, pretend we don't even have a long long." This is
205        done by checking for the strtoq, strtoll, and _strtoi64 functions.
207    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
208        pre-7.6 versions, which defined a global no_arg variable instead of putting
209        it in the RE class. (See also #8 below.)
211    3.  Remove a line of dead code, identified by coverity and reported by Nuno
212        Lopes.
214    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
216        (1) The include/exclude patterns were being applied to the whole pathnames
217            of files, instead of just to the final components.
219        (2) If there was more than one level of directory, the subdirectories were
220            skipped unless they satisfied the include/exclude conditions. This is
221            inconsistent with GNU grep (and could even be seen as contrary to the
222            pcregrep specification - which I improved to make it absolutely clear).
223            The action now is always to scan all levels of directory, and just
224            apply the include/exclude patterns to regular files.
226    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
227        --exclude_dir in the tests to avoid scanning .svn directories.
229    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
230        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
231        doesn't support NULs in patterns.
233    7.  Added some missing "const"s to declarations of static tables in
234        pcre_compile.c and pcre_dfa_exec.c.
236    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
237        caused by fix #2  above. (Subsequently also a second patch to fix the
238        first patch. And a third patch - this was a messy problem.)
240    9.  Applied Craig's patch to remove the use of push_back().
242    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
243        matching function regexec().
245    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
246        which, however, unlike Perl's \g{...}, are subroutine calls, not back
247        references. PCRE supports relative numbers with this syntax (I don't think
248        Oniguruma does).
250    12. Previously, a group with a zero repeat such as (...){0} was completely
251        omitted from the compiled regex. However, this means that if the group
252        was called as a subroutine from elsewhere in the pattern, things went wrong
253        (an internal error was given). Such groups are now left in the compiled
254        pattern, with a new opcode that causes them to be skipped at execution
255        time.
257    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
258        to the way PCRE behaves:
260        (a) A lone ] character is dis-allowed (Perl treats it as data).
262        (b) A back reference to an unmatched subpattern matches an empty string
263            (Perl fails the current match path).
265        (c) A data ] in a character class must be notated as \] because if the
266            first data character in a class is ], it defines an empty class. (In
267            Perl it is not possible to have an empty class.) The empty class []
268            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
269            The negative empty class [^] matches any one character, independently
270            of the DOTALL setting.
272    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
273        non-existent subpattern following a character class starting with ']' and
274        containing () gave an internal compiling error instead of "reference to
275        non-existent subpattern". Fortunately, when the pattern did exist, the
276        compiled code was correct. (When scanning forwards to check for the
277        existencd of the subpattern, it was treating the data ']' as terminating
278        the class, so got the count wrong. When actually compiling, the reference
279        was subsequently set up correctly.)
281    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
282        it was being rejected as not supported by pcre_dfa_exec(), even though
283        other assertions are supported. I have made pcre_dfa_exec() support
284        (*FAIL).
286    16. The implementation of 13c above involved the invention of a new opcode,
287        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
288        cannot be changed at match time, I realized I could make a small
289        improvement to matching performance by compiling OP_ALLANY instead of
290        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
291        on the OP_ANY path.
293    17. Compiling pcretest on Windows with readline support failed without the
294        following two fixes: (1) Make the unistd.h include conditional on
295        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
297    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
298        ncurses library to be included for pcretest when ReadLine support is
299        requested, but also to allow for it to be overridden. This patch came from
300        Daniel Bergström.
302    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
303        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
304        any errors with the current Unicode tables. Thanks to Peter Kankowski for
305        spotting this.
308    Version 7.6 28-Jan-08
309  ---------------------  ---------------------
311  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 37  Version 7.6 21-Jan-08 Line 341  Version 7.6 21-Jan-08
341      solves the problem, but it does no harm.      solves the problem, but it does no harm.
343  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
344      NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured      NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
345      with CMake, and also correct the comment about stack recursion.      with CMake, and also correct the comment about stack recursion.
347  7.  Remove the automatic building of pcredemo from the ./configure system and  7.  Remove the automatic building of pcredemo from the ./configure system and
# Line 46  Version 7.6 21-Jan-08 Line 350  Version 7.6 21-Jan-08
350      building it automatically is not really right. What is more, it gave      building it automatically is not really right. What is more, it gave
351      trouble in some build environments.      trouble in some build environments.
353    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
356  Version 7.5 10-Jan-08  Version 7.5 10-Jan-08
357  ---------------------  ---------------------

Removed from v.314  
changed lines
  Added in v.411

  ViewVC Help
Powered by ViewVC 1.1.5