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

Diff of /code/trunk/ChangeLog

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

revision 388 by ph10, Wed Mar 11 17:03:17 2009 UTC revision 433 by ph10, Wed Sep 2 16:09:13 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    16. If a caller to the POSIX matching function regexec() passes a non-zero
92        value for \fInmatch\fP with a NULL value for \fIpmatch\fP, the value of
93        \fInmatch\fP is forced to zero.
94    
95    
96    Version 7.9 11-Apr-09
97  ---------------------  ---------------------
98    
99  1.  When building with support for bzlib/zlib (pcregrep) and/or readline  1.  When building with support for bzlib/zlib (pcregrep) and/or readline
100      (pcretest), all targets were linked against these libraries. This included      (pcretest), all targets were linked against these libraries. This included
101      libpcre, libpcreposix, and libpcrecpp, even though they do not use these      libpcre, libpcreposix, and libpcrecpp, even though they do not use these
102      libraries. This caused unwanted dependencies to be created. This problem      libraries. This caused unwanted dependencies to be created. This problem
103      has been fixed, and now only pcregrep is linked with bzlib/zlib and only      has been fixed, and now only pcregrep is linked with bzlib/zlib and only
104      pcretest is linked with readline.      pcretest is linked with readline.
105    
106  2.  The "typedef int BOOL" in pcre_internal.h that was included inside the  2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
107      "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been      "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
108      moved outside it again, because FALSE and TRUE are already defined in AIX,      moved outside it again, because FALSE and TRUE are already defined in AIX,
109      but BOOL is not.      but BOOL is not.
110    
111  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
112      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.
113    
114  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
115      hyphens) following file names and line numbers when outputting matching      hyphens) following file names and line numbers when outputting matching
116      lines. This is not true; no spaces are inserted. I have also clarified the      lines. This is not true; no spaces are inserted. I have also clarified the
117      wording for the --colour (or --color) option.      wording for the --colour (or --color) option.
118    
119  5.  In pcregrep, when --colour was used with -o, the list of matching strings  5.  In pcregrep, when --colour was used with -o, the list of matching strings
120      was not coloured; this is different to GNU grep, so I have changed it to be      was not coloured; this is different to GNU grep, so I have changed it to be
121      the same.      the same.
122    
123  6.  When --colo(u)r was used in pcregrep, only the first matching substring in  6.  When --colo(u)r was used in pcregrep, only the first matching substring in
124      each matching line was coloured. Now it goes on to look for further matches      each matching line was coloured. Now it goes on to look for further matches
125      of any of the test patterns, which is the same behaviour as GNU grep.      of any of the test patterns, which is the same behaviour as GNU grep.
126    
127  7.  A pattern that could match an empty string could cause pcregrep to loop; it  7.  A pattern that could match an empty string could cause pcregrep to loop; it
128      doesn't make sense to accept an empty string match in pcregrep, so I have      doesn't make sense to accept an empty string match in pcregrep, so I have
129      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
130      seems to be how GNU grep behaves.      seems to be how GNU grep behaves.
131    
132  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
133      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being
134      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
135      in the first alternative must satisfy the test.      in the first alternative must satisfy the test.
136    
137  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
138      could crash during matching.      condition was an assertion, PCRE could crash during matching, both with
139        pcre_exec() and pcre_dfa_exec().
140  10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was  
141      used for matching.  10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
142        used for matching.
143  11. Unicode property support in character classes was not working for  
144    11. Unicode property support in character classes was not working for
145      characters (bytes) greater than 127 when not in UTF-8 mode.      characters (bytes) greater than 127 when not in UTF-8 mode.
146    
147  12. Added the -M command line option to pcretest.  12. Added the -M command line option to pcretest.
148    
149  14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.  14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
150    
151    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
152    
153    16. Added comments and documentation about mis-use of no_arg in the C++
154        wrapper.
155    
156    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
157        from Martin Jerabek that uses macro names for all relevant character and
158        string constants.
159    
160    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
161        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
162        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
163        these, but not everybody uses configure.
164    
165    19. A conditional group that had only one branch was not being correctly
166        recognized as an item that could match an empty string. This meant that an
167        enclosing group might also not be so recognized, causing infinite looping
168        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
169        with the subject "ab", where knowledge that the repeated group can match
170        nothing is needed in order to break the loop.
171    
172    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
173        exec(), but without supplying a callout function, matching went wrong.
174    
175    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
176        leak if the size of the offset vector was greater than 30. When the vector
177        is smaller, the saved offsets during recursion go onto a local stack
178        vector, but for larger vectors malloc() is used. It was failing to free
179        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
180        error, in fact).
181    
182    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
183        heapframe that is used only when UTF-8 support is enabled. This caused no
184        problem, but was untidy.
185    
186    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
187        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
188        included within another project.
189    
190    24. Steven Van Ingelgem's patches to add more options to the CMake support,
191        slightly modified by me:
192    
193          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
194              not building pcregrep.
195    
196          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
197              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
198    
199    25. Forward references, both numeric and by name, in patterns that made use of
200        duplicate group numbers, could behave incorrectly or give incorrect errors,
201        because when scanning forward to find the reference group, PCRE was not
202        taking into account the duplicate group numbers. A pattern such as
203        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
204    
205    26. Changed a few more instances of "const unsigned char *" to USPTR, making
206        the feature of a custom pointer more persuasive (as requested by a user).
207    
208    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
209        pcretest.c, inside #ifndefs, because it seems they are sometimes already
210        pre-defined.
211    
212    28. Added support for (*UTF8) at the start of a pattern.
213    
214    29. Arrange for flags added by the "release type" setting in CMake to be shown
215        in the configuration summary.
216    
217    
218  Version 7.8 05-Sep-08  Version 7.8 05-Sep-08
219  ---------------------  ---------------------
Legend:
Removed from v.388  
changed lines
  Added in v.433
webmaster@exim.org
 ViewVC Help
Powered by ViewVC 1.1.12