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

Diff of /code/trunk/ChangeLog

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

revision 407 by ph10, Mon Mar 23 15:29:18 2009 UTC revision 432 by ph10, Wed Sep 2 16:02:56 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.9 xx-xxx-09  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    15. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
87        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
88        is not the first non-POSIX option to be added. Clearly some people find
89        these options useful.
90    
91    
92    Version 7.9 11-Apr-09
93  ---------------------  ---------------------
94    
95  1.  When building with support for bzlib/zlib (pcregrep) and/or readline  1.  When building with support for bzlib/zlib (pcregrep) and/or readline
# Line 17  Version 7.9 xx-xxx-09 Line 105  Version 7.9 xx-xxx-09
105      but BOOL is not.      but BOOL is not.
106    
107  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
108      PCRE_MATCH_LIMIT_RETURSION values as ints, when they should be long ints.      PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
109    
110  4.  The pcregrep documentation said spaces were inserted as well as colons (or  4.  The pcregrep documentation said spaces were inserted as well as colons (or
111      hyphens) following file names and line numbers when outputting matching      hyphens) following file names and line numbers when outputting matching
# Line 94  Version 7.9 xx-xxx-09 Line 182  Version 7.9 xx-xxx-09
182  23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name  23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
183      CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is      CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
184      included within another project.      included within another project.
185    
186  24. Steven Van Ingelgem's patches to add more options to the CMake support,  24. Steven Van Ingelgem's patches to add more options to the CMake support,
187      slightly modified by me:      slightly modified by me:
188    
189        (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including        (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
190            not building pcregrep.            not building pcregrep.
191    
192        (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only        (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
193            if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.            if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
194    
195    25. Forward references, both numeric and by name, in patterns that made use of
196        duplicate group numbers, could behave incorrectly or give incorrect errors,
197        because when scanning forward to find the reference group, PCRE was not
198        taking into account the duplicate group numbers. A pattern such as
199        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
200    
201    26. Changed a few more instances of "const unsigned char *" to USPTR, making
202        the feature of a custom pointer more persuasive (as requested by a user).
203    
204    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
205        pcretest.c, inside #ifndefs, because it seems they are sometimes already
206        pre-defined.
207    
208    28. Added support for (*UTF8) at the start of a pattern.
209    
210    29. Arrange for flags added by the "release type" setting in CMake to be shown
211        in the configuration summary.
212    
213    
214  Version 7.8 05-Sep-08  Version 7.8 05-Sep-08

Legend:
Removed from v.407  
changed lines
  Added in v.432

  ViewVC Help
Powered by ViewVC 1.1.5