| 20 |
code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a |
code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a |
| 21 |
2-byte code at the end of the subject (it thought there wasn't enough data |
2-byte code at the end of the subject (it thought there wasn't enough data |
| 22 |
left). |
left). |
| 23 |
|
|
| 24 |
|
5. Comprehensive information about what went wrong is now returned by |
| 25 |
|
pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long |
| 26 |
|
as the output vector has at least 2 elements. The offset of the start of |
| 27 |
|
the failing character and a reason code are placed in the vector. |
| 28 |
|
|
| 29 |
|
6. When the UTF-8 string check fails for pcre_compile(), the offset that is |
| 30 |
|
now returned is for the first byte of the failing character, instead of the |
| 31 |
|
last byte inspected. This is an incompatible change, but I hope it is small |
| 32 |
|
enough not to be a problem. It makes the returned offset consistent with |
| 33 |
|
pcre_exec() and pcre_dfa_exec(). |
| 34 |
|
|
| 35 |
|
7. pcretest now gives a text phrase as well as the error number when |
| 36 |
|
pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check |
| 37 |
|
failure, the offset and reason code are output. |
| 38 |
|
|
| 39 |
|
|
| 40 |
|
|
| 41 |
Version 8.12 15-Jan-2011 |
Version 8.12 15-Jan-2011 |
Parent Directory
| 
Revision Log
| 
Patch