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 391 by ph10, Tue Mar 17 21:16:01 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.6 21-Jan-08  Version 7.9 xx-xxx-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_RETURSION 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, PCRE
46        could crash during matching.
48    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
49        used for matching.
51    11. Unicode property support in character classes was not working for
52        characters (bytes) greater than 127 when not in UTF-8 mode.
54    12. Added the -M command line option to pcretest.
56    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
58    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
60    16. Added comments and documentation about mis-use of no_arg in the C++
61        wrapper.
63    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
64        from Martin Jerabek that uses macro names for all relevant character and
65        string constants.
68    Version 7.8 05-Sep-08
69    ---------------------
71    1.  Replaced UCP searching code with optimized version as implemented for Ad
72        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
73        stage table and inline lookup instead of a function, giving speed ups of 2
74        to 5 times on some simple patterns that I tested. Permission was given to
75        distribute the MultiStage2.py script that generates the tables (it's not in
76        the tarball, but is in the Subversion repository).
78    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
79        scripts.
81    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
82        a group with a zero qualifier. The result of the study could be incorrect,
83        or the function might crash, depending on the pattern.
85    4.  Caseless matching was not working for non-ASCII characters in back
86        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
87        It now works when Unicode Property Support is available.
89    5.  In pcretest, an escape such as \x{de} in the data was always generating
90        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
91        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
92        truncation.
94    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
96    7.  Added two (int) casts to pcregrep when printing the difference of two
97        pointers, in case they are 64-bit values.
99    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
100        test 2 if it fails.
102    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
103        and a #define of that name to empty if it is not externally set. This is to
104        allow users of MSVC to set it if necessary.
106    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
107        the convenience functions in the pcre_get.c source file.
109    11. An option change at the start of a pattern that had top-level alternatives
110        could cause overwriting and/or a crash. This command provoked a crash in
111        some environments:
113          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
115        This potential security problem was recorded as CVE-2008-2371.
117    12. For a pattern where the match had to start at the beginning or immediately
118        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
119        pcre_dfa_exec() could read past the end of the passed subject if there was
120        no match. To help with detecting such bugs (e.g. with valgrind), I modified
121        pcretest so that it places the subject at the end of its malloc-ed buffer.
123    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
124        exec() might read past the end of the data buffer in UTF-8 mode.
126    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
127        the data contained the byte 0x85 as part of a UTF-8 character within its
128        first line. This applied both to normal and DFA matching.
130    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
131        /^[^d]*?$/8 failed to match "abc".
133    16. Added a missing copyright notice to pcrecpp_internal.h.
135    17. Make it more clear in the documentation that values returned from
136        pcre_exec() in ovector are byte offsets, not character counts.
138    18. Tidied a few places to stop certain compilers from issuing warnings.
140    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
141        supplied by Stefan Weber. I made a further small update for 7.8 because
142        there is a change of source arrangements: the pcre_searchfuncs.c module is
143        replaced by pcre_ucd.c.
146    Version 7.7 07-May-08
147    ---------------------
149    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
150        a string to a long long, pretend we don't even have a long long." This is
151        done by checking for the strtoq, strtoll, and _strtoi64 functions.
153    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
154        pre-7.6 versions, which defined a global no_arg variable instead of putting
155        it in the RE class. (See also #8 below.)
157    3.  Remove a line of dead code, identified by coverity and reported by Nuno
158        Lopes.
160    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
162        (1) The include/exclude patterns were being applied to the whole pathnames
163            of files, instead of just to the final components.
165        (2) If there was more than one level of directory, the subdirectories were
166            skipped unless they satisfied the include/exclude conditions. This is
167            inconsistent with GNU grep (and could even be seen as contrary to the
168            pcregrep specification - which I improved to make it absolutely clear).
169            The action now is always to scan all levels of directory, and just
170            apply the include/exclude patterns to regular files.
172    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
173        --exclude_dir in the tests to avoid scanning .svn directories.
175    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
176        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
177        doesn't support NULs in patterns.
179    7.  Added some missing "const"s to declarations of static tables in
180        pcre_compile.c and pcre_dfa_exec.c.
182    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
183        caused by fix #2  above. (Subsequently also a second patch to fix the
184        first patch. And a third patch - this was a messy problem.)
186    9.  Applied Craig's patch to remove the use of push_back().
188    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
189        matching function regexec().
191    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
192        which, however, unlike Perl's \g{...}, are subroutine calls, not back
193        references. PCRE supports relative numbers with this syntax (I don't think
194        Oniguruma does).
196    12. Previously, a group with a zero repeat such as (...){0} was completely
197        omitted from the compiled regex. However, this means that if the group
198        was called as a subroutine from elsewhere in the pattern, things went wrong
199        (an internal error was given). Such groups are now left in the compiled
200        pattern, with a new opcode that causes them to be skipped at execution
201        time.
203    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
204        to the way PCRE behaves:
206        (a) A lone ] character is dis-allowed (Perl treats it as data).
208        (b) A back reference to an unmatched subpattern matches an empty string
209            (Perl fails the current match path).
211        (c) A data ] in a character class must be notated as \] because if the
212            first data character in a class is ], it defines an empty class. (In
213            Perl it is not possible to have an empty class.) The empty class []
214            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
215            The negative empty class [^] matches any one character, independently
216            of the DOTALL setting.
218    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
219        non-existent subpattern following a character class starting with ']' and
220        containing () gave an internal compiling error instead of "reference to
221        non-existent subpattern". Fortunately, when the pattern did exist, the
222        compiled code was correct. (When scanning forwards to check for the
223        existencd of the subpattern, it was treating the data ']' as terminating
224        the class, so got the count wrong. When actually compiling, the reference
225        was subsequently set up correctly.)
227    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
228        it was being rejected as not supported by pcre_dfa_exec(), even though
229        other assertions are supported. I have made pcre_dfa_exec() support
230        (*FAIL).
232    16. The implementation of 13c above involved the invention of a new opcode,
233        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
234        cannot be changed at match time, I realized I could make a small
235        improvement to matching performance by compiling OP_ALLANY instead of
236        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
237        on the OP_ANY path.
239    17. Compiling pcretest on Windows with readline support failed without the
240        following two fixes: (1) Make the unistd.h include conditional on
241        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
243    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
244        ncurses library to be included for pcretest when ReadLine support is
245        requested, but also to allow for it to be overridden. This patch came from
246        Daniel Bergström.
248    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
249        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
250        any errors with the current Unicode tables. Thanks to Peter Kankowski for
251        spotting this.
254    Version 7.6 28-Jan-08
255  ---------------------  ---------------------
257  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 287  Version 7.6 21-Jan-08
287      solves the problem, but it does no harm.      solves the problem, but it does no harm.
289  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
290      NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured      NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
291      with CMake, and also correct the comment about stack recursion.      with CMake, and also correct the comment about stack recursion.
293  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 296  Version 7.6 21-Jan-08
296      building it automatically is not really right. What is more, it gave      building it automatically is not really right. What is more, it gave
297      trouble in some build environments.      trouble in some build environments.
299    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
302  Version 7.5 10-Jan-08  Version 7.5 10-Jan-08
303  ---------------------  ---------------------

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

  ViewVC Help
Powered by ViewVC 1.1.5