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

Diff of /code/trunk/ChangeLog

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

revision 393 by ph10, Tue Mar 17 21:47:54 2009 UTC revision 437 by ph10, Sun Sep 6 16:34:42 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 offset of the earliest inspected character
55        for the match and the offset of the end of the subject are set in them when
56        PCRE_ERROR_PARTIAL is returned.
57    
58    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
59        synonymous with PCRE_PARTIAL, for backwards compatibility, and
60        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
61        and may be more useful for multi-segment matching, especially with
62        pcre_exec().
63    
64    11. Partial matching with pcre_exec() is now more intuitive. A partial match
65        used to be given if ever the end of the subject was reached; now it is
66        given only if matching could not proceed because another character was
67        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
68        string "Z", which now yields "no match" instead of "partial match". In the
69        case of pcre_dfa_exec(), "no match" is given if every matching path for the
70        final character ended with (*FAIL).
71    
72    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
73        if the pattern had a "must contain" character that was already found in the
74        earlier partial match, unless partial matching was again requested. For
75        example, with the pattern /dog.(body)?/, the "must contain" character is
76        "g". If the first part-match was for the string "dog", restarting with
77        "sbody" failed. This bug has been fixed.
78    
79    13. The string returned by pcre_dfa_exec() after a partial match has been
80        changed so that it starts at the first inspected character rather than the
81        first character of the match. This makes a difference only if the pattern
82        starts with a lookbehind assertion or \b or \B (\K is not supported by
83        pcre_dfa_exec()). It's an incompatible change, but it makes the two
84        matching functions compatible, and I think it's the right thing to do.
85    
86    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
87        so that the demonstration program is easily available in environments where
88        PCRE has not been installed from source.
89    
90    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
91        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
92        library.
93    
94    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
95        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
96        is not the first non-POSIX option to be added. Clearly some people find
97        these options useful.
98    
99    17. If a caller to the POSIX matching function regexec() passes a non-zero
100        value for \fInmatch\fP with a NULL value for \fIpmatch\fP, the value of
101        \fInmatch\fP is forced to zero.
102    
103    18. RunGrepTest did not have a test for the availability of the -u option of
104        the diff command, as RunTest does. It now checks in the same way as
105        RunTest, and also checks for the -b option.
106    
107    
108    Version 7.9 11-Apr-09
109  ---------------------  ---------------------
110    
111  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 121  Version 7.9 xx-xxx-09
121      but BOOL is not.      but BOOL is not.
122    
123  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
124      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.
125    
126  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
127      hyphens) following file names and line numbers when outputting matching      hyphens) following file names and line numbers when outputting matching
# Line 42  Version 7.9 xx-xxx-09 Line 146  Version 7.9 xx-xxx-09
146      correctly handled. The rule now is that both the assertion and what follows      correctly handled. The rule now is that both the assertion and what follows
147      in the first alternative must satisfy the test.      in the first alternative must satisfy the test.
148    
149  9.  If auto-callout was enabled in a pattern with a conditional group, PCRE  9.  If auto-callout was enabled in a pattern with a conditional group whose
150      could crash during matching.      condition was an assertion, PCRE could crash during matching, both with
151        pcre_exec() and pcre_dfa_exec().
152    
153  10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was  10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
154      used for matching.      used for matching.
# Line 63  Version 7.9 xx-xxx-09 Line 168  Version 7.9 xx-xxx-09
168  17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch  17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
169      from Martin Jerabek that uses macro names for all relevant character and      from Martin Jerabek that uses macro names for all relevant character and
170      string constants.      string constants.
171    
172  18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and  18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
173      SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without      SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
174      SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of      SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
175      these, but not everybody uses configure.      these, but not everybody uses configure.
176    
177    19. A conditional group that had only one branch was not being correctly
178        recognized as an item that could match an empty string. This meant that an
179        enclosing group might also not be so recognized, causing infinite looping
180        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
181        with the subject "ab", where knowledge that the repeated group can match
182        nothing is needed in order to break the loop.
183    
184    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
185        exec(), but without supplying a callout function, matching went wrong.
186    
187    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
188        leak if the size of the offset vector was greater than 30. When the vector
189        is smaller, the saved offsets during recursion go onto a local stack
190        vector, but for larger vectors malloc() is used. It was failing to free
191        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
192        error, in fact).
193    
194    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
195        heapframe that is used only when UTF-8 support is enabled. This caused no
196        problem, but was untidy.
197    
198    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
199        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
200        included within another project.
201    
202    24. Steven Van Ingelgem's patches to add more options to the CMake support,
203        slightly modified by me:
204    
205          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
206              not building pcregrep.
207    
208          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
209              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
210    
211    25. Forward references, both numeric and by name, in patterns that made use of
212        duplicate group numbers, could behave incorrectly or give incorrect errors,
213        because when scanning forward to find the reference group, PCRE was not
214        taking into account the duplicate group numbers. A pattern such as
215        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
216    
217    26. Changed a few more instances of "const unsigned char *" to USPTR, making
218        the feature of a custom pointer more persuasive (as requested by a user).
219    
220    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
221        pcretest.c, inside #ifndefs, because it seems they are sometimes already
222        pre-defined.
223    
224    28. Added support for (*UTF8) at the start of a pattern.
225    
226    29. Arrange for flags added by the "release type" setting in CMake to be shown
227        in the configuration summary.
228    
229    
230  Version 7.8 05-Sep-08  Version 7.8 05-Sep-08

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

  ViewVC Help
Powered by ViewVC 1.1.5