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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.322  
changed lines
  Added in v.393

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12