21 |
more useful - otherwise, why use --count?) Also ensured that the |
more useful - otherwise, why use --count?) Also ensured that the |
22 |
combination -clh just lists non-zero counts, with no names. |
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. Chaos could result. |
47 |
|
|
48 |
|
9. The restrictions on what a pattern can contain when partial matching is |
49 |
|
requested for pcre_exec() have been removed. All patterns can now be |
50 |
|
partially matched by this function. In addition, if there are at least two |
51 |
|
slots in the offset vector, the offsets of the first-encountered partial |
52 |
|
match are set in them when PCRE_ERROR_PARTIAL is returned. |
53 |
|
|
54 |
|
10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is |
55 |
|
synonymous with PCRE_PARTIAL, for backwards compatibility, and |
56 |
|
PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match, |
57 |
|
and may be more useful for multi-segment matching, especially with |
58 |
|
pcre_exec(). |
59 |
|
|
60 |
|
11. Partial matching with pcre_exec() is now more intuitive. A partial match |
61 |
|
used to be given if ever the end of the subject was reached; now it is |
62 |
|
given only if matching could not proceed because another character was |
63 |
|
needed. This makes a difference in some odd cases such as Z(*FAIL) with the |
64 |
|
string "Z", which now yields "no match" instead of "partial match". In the |
65 |
|
case of pcre_dfa_exec(), "no match" is given if every matching path for the |
66 |
|
final character ended with (*FAIL). |
67 |
|
|
68 |
|
12. Restarting a match using pcre_dfa_exec() after a partial match did not work |
69 |
|
if the pattern had a "must contain" character that was already found in the |
70 |
|
earlier partial match, unless partial matching was again requested. For |
71 |
|
example, with the pattern /dog.(body)?/, the "must contain" character is |
72 |
|
"g". If the first part-match was for the string "dog", restarting with |
73 |
|
"sbody" failed. |
74 |
|
|
75 |
|
13. Added a pcredemo man page, created automatically from the pcredemo.c file, |
76 |
|
so that the demonstration program is easily available in environments where |
77 |
|
PCRE has not been installed from source. |
78 |
|
|
79 |
|
14. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp, |
80 |
|
libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared |
81 |
|
library. |
82 |
|
|
83 |
|
|
84 |
Version 7.9 11-Apr-09 |
Version 7.9 11-Apr-09 |
85 |
--------------------- |
--------------------- |