/[pcre]/code/branches/pcre16/ChangeLog
ViewVC logotype

Diff of /code/branches/pcre16/ChangeLog

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

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

Legend:
Removed from v.308  
changed lines
  Added in v.431

  ViewVC Help
Powered by ViewVC 1.1.5