| 43 |
|
|
| 44 |
8. A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger |
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 |
was a minimum greater than 1 for a wide character in a possessive |
| 46 |
repetition. Chaos could result. |
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 |
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 |
requested for pcre_exec() have been removed. All patterns can now be |
| 54 |
slots in the offset vector, the offsets of the first-encountered partial |
slots in the offset vector, the offsets of the first-encountered partial |
| 55 |
match are set in them when PCRE_ERROR_PARTIAL is returned. |
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 |
Version 7.9 11-Apr-09 |
| 97 |
--------------------- |
--------------------- |
Parent Directory
| 
Revision Log
| 
Patch