| 5 |
------------ |
------------ |
| 6 |
|
|
| 7 |
Release 8.30 introduces a major new feature: support for 16-bit character |
Release 8.30 introduces a major new feature: support for 16-bit character |
| 8 |
strings, compiled as a separate library. There are no new features in the 8-bit |
strings, compiled as a separate library. There are a few changes to the |
| 9 |
library, but some bugs have been mended. However, note that the pcre_info() |
8-bit library, in addition to some bug fixes. |
| 10 |
function, which has been obsolete for over 10 years, has been removed. |
|
| 11 |
|
. The pcre_info() function, which has been obsolete for over 10 years, has |
| 12 |
|
been removed. |
| 13 |
|
|
| 14 |
|
. When a compiled pattern was saved to a file and later reloaded on a host |
| 15 |
|
with different endianness, PCRE used automatically to swap the bytes in some |
| 16 |
|
of the data fields. With the advent of the 16-bit library, where more of this |
| 17 |
|
swapping is needed, it is no longer done automatically. Instead, the bad |
| 18 |
|
endianness is detected and a specific error is given. The user can then call |
| 19 |
|
a new function called pcre_pattern_to_host_byte_order() (or an equivalent |
| 20 |
|
16-bit function) to do the swap. |
| 21 |
|
|
| 22 |
|
. In UTF-8 mode, the values 0xd800 to 0xdfff are not legal Unicode |
| 23 |
|
code points and are now faulted. (They are the so-called "surrogates" |
| 24 |
|
that are reserved for coding high values in UTF-16.) |
| 25 |
|
|
| 26 |
|
|
| 27 |
Release 8.21 12-Dec-2011 |
Release 8.21 12-Dec-2011 |
Parent Directory
| 
Revision Log
| 
Patch