| 92 |
15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the |
15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the |
| 93 |
starting offset points to the beginning of a UTF-8 character was |
starting offset points to the beginning of a UTF-8 character was |
| 94 |
unnecessarily clumsy. I tidied it up. |
unnecessarily clumsy. I tidied it up. |
| 95 |
|
|
| 96 |
|
16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a |
| 97 |
|
bad UTF-8 sequence and one that is incomplete. |
| 98 |
|
|
| 99 |
|
17. Nobody had reported that the --include_dir option, which was added in |
| 100 |
|
release 7.7 should have been called --include-dir (hyphen, not underscore) |
| 101 |
|
for compatibility with GNU grep. I have changed it to --include-dir, but |
| 102 |
|
left --include_dir as an undocumented synonym, and the same for |
| 103 |
|
--exclude-dir, though that is not available in GNU grep, at least as of |
| 104 |
|
release 2.5.4. |
| 105 |
|
|
| 106 |
|
18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8 |
| 107 |
|
characters from a string of bytes) have been redefined so as not to use |
| 108 |
|
loops, in order to improve performance in some environments. At the same |
| 109 |
|
time, I abstracted some of the common code into auxiliary macros to save |
| 110 |
|
repetition (this should not affect the compiled code). |
| 111 |
|
|
| 112 |
|
19. If \c was followed by a multibyte UTF-8 character, bad things happened. A |
| 113 |
|
compile-time error is now given if \c is not followed by an ASCII |
| 114 |
|
character, that is, a byte less than 128. (In EBCDIC mode, the code is |
| 115 |
|
different, and any byte value is allowed.) |
| 116 |
|
|
| 117 |
|
|
| 118 |
Version 8.10 25-Jun-2010 |
Version 8.10 25-Jun-2010 |
Parent Directory
| 
Revision Log
| 
Patch