| 44 |
|
|
| 45 |
10. Remove two redundant lines of code that can never be obeyed (their function |
10. Remove two redundant lines of code that can never be obeyed (their function |
| 46 |
was moved elsewhere). |
was moved elsewhere). |
| 47 |
|
|
| 48 |
|
11. The program that makes PCRE's Unicode character property table had a bug |
| 49 |
|
which caused it to generate incorrect table entries for sequences of |
| 50 |
|
characters that have the same character type, but are in different scripts. |
| 51 |
|
It amalgamated them into a single range, with the script of the first of |
| 52 |
|
them. In other words, some characters were in the wrong script. There were |
| 53 |
|
thirteen such cases, affecting characters in the following ranges: |
| 54 |
|
|
| 55 |
|
U+002b0 - U+002c1 |
| 56 |
|
U+0060c - U+0060d |
| 57 |
|
U+0061e - U+00612 |
| 58 |
|
U+0064b - U+0065e |
| 59 |
|
U+0074d - U+0076d |
| 60 |
|
U+01800 - U+01805 |
| 61 |
|
U+01d00 - U+01d77 |
| 62 |
|
U+01d9b - U+01dbf |
| 63 |
|
U+0200b - U+0200f |
| 64 |
|
U+030fc - U+030fe |
| 65 |
|
U+03260 - U+0327f |
| 66 |
|
U+0fb46 - U+0fbb1 |
| 67 |
|
U+10450 - U+1049d |
| 68 |
|
|
| 69 |
|
12. The -o option (show only the matching part of a line) for pcregrep was not |
| 70 |
|
compatible with GNU grep in that, if there was more than one match in a |
| 71 |
|
line, it showed only the first of them. It now behaves in the same way as |
| 72 |
|
GNU grep. |
| 73 |
|
|
| 74 |
|
13. If the -o and -v options were combined for pcregrep, it printed a blank |
| 75 |
|
line for every non-matching line. GNU grep prints nothing, and pcregrep now |
| 76 |
|
does the same. The return code can be used to tell if there were any |
| 77 |
|
non-matching lines. |
| 78 |
|
|
| 79 |
|
14. The pattern (?=something)(?R) was not being diagnosed as a potentially |
| 80 |
|
infinitely looping recursion. The bug was that positive lookaheads were not |
| 81 |
|
being skipped when checking for a possible empty match (negative lookaheads |
| 82 |
|
and both kinds of lookbehind were skipped). |
| 83 |
|
|
| 84 |
|
15. Fixed two typos in the Windows-only code in pcregrep.c, and moved the |
| 85 |
|
inclusion of <windows.h> to before rather than after the definition of |
| 86 |
|
INVALID_FILE_ATTRIBUTES (patch from David Byron). |
| 87 |
|
|
| 88 |
|
16. Specifying a possessive quantifier with a specific limit for a Unicode |
| 89 |
|
character property caused pcre_compile() to compile bad code, which led at |
| 90 |
|
runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this |
| 91 |
|
are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that |
| 92 |
|
caused the error; without that there was no problem. |
| 93 |
|
|
| 94 |
|
|
| 95 |
Version 7.4 21-Sep-07 |
Version 7.4 21-Sep-07 |
Parent Directory
| 
Revision Log
| 
Patch