| 21 |
the class, even if it had been included by some previous item, for example |
the class, even if it had been included by some previous item, for example |
| 22 |
in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part |
in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part |
| 23 |
of \s, but is part of the POSIX "space" class.) |
of \s, but is part of the POSIX "space" class.) |
| 24 |
|
|
| 25 |
|
4. A partial match never returns an empty string (because you can always |
| 26 |
|
match an empty string at the end of the subject); however the checking for |
| 27 |
|
an empty string was starting at the "start of match" point. This has been |
| 28 |
|
changed to the "earliest inspected character" point, because the returned |
| 29 |
|
data for a partial match starts at this character. This means that, for |
| 30 |
|
example, /(?<=abc)def/ gives a partial match for the subject "abc" |
| 31 |
|
(previously it gave "no match"). |
| 32 |
|
|
| 33 |
|
5. Changes have been made to the way PCRE_PARTIAL_HARD affects the matching |
| 34 |
|
of $, \z, \Z, \b, and \B. If the match point is at the end of the string, |
| 35 |
|
previously a full match would be given. However, setting PCRE_PARTIAL_HARD |
| 36 |
|
has an implication that the given string is incomplete (because a partial |
| 37 |
|
match is preferred over a full match). For this reason, these items now |
| 38 |
|
give a partial match in this situation. [Aside: previously, the one case |
| 39 |
|
/t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial |
| 40 |
|
match rather than a full match, which was wrong by the old rules, but is |
| 41 |
|
now correct.] |
| 42 |
|
|
| 43 |
|
|
| 44 |
Version 8.10 25-Jun-2010 |
Version 8.10 25-Jun-2010 |
Parent Directory
| 
Revision Log
| 
Patch