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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.319  
changed lines
  Added in v.423

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12