| 136 |
the same checks as \x{...} characters in non-JavaScript mode. Specifically, |
the same checks as \x{...} characters in non-JavaScript mode. Specifically, |
| 137 |
codepoints that are too big for the mode are faulted, and in a UTF mode, |
codepoints that are too big for the mode are faulted, and in a UTF mode, |
| 138 |
disallowed codepoints are also faulted. |
disallowed codepoints are also faulted. |
| 139 |
|
|
| 140 |
|
39. If PCRE was compiled with UTF support, in three places in the DFA |
| 141 |
|
matcher there was code that should only have been obeyed in UTF mode, but |
| 142 |
|
was being obeyed unconditionally. In 8-bit mode this could cause incorrect |
| 143 |
|
processing when bytes with values greater than 127 were present. In 16-bit |
| 144 |
|
mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In |
| 145 |
|
both cases the values are those that cannot be the first data item in a UTF |
| 146 |
|
character. The three items that might have provoked this were recursions, |
| 147 |
|
possessively repeated groups, and atomic groups. |
| 148 |
|
|
| 149 |
|
|
| 150 |
Version 8.30 04-February-2012 |
Version 8.30 04-February-2012 |
Parent Directory
| 
Revision Log
| 
Patch