|
1 | 1 | News about PCRE releases |
2 | 2 | ------------------------ |
3 | 3 |
|
| 4 | +Release 8.36 26-September-2014 |
| 5 | +------------------------------ |
| 6 | + |
| 7 | +This is primarily a bug-fix release. However, in addition, the Unicode data |
| 8 | +tables have been updated to Unicode 7.0.0. |
| 9 | + |
| 10 | + |
| 11 | +Release 8.35 04-April-2014 |
| 12 | +-------------------------- |
| 13 | + |
| 14 | +There have been performance improvements for classes containing non-ASCII |
| 15 | +characters and the "auto-possessification" feature has been extended. Other |
| 16 | +minor improvements have been implemented and bugs fixed. There is a new callout |
| 17 | +feature to enable applications to do detailed stack checks at compile time, to |
| 18 | +avoid running out of stack for deeply nested parentheses. The JIT compiler has |
| 19 | +been extended with experimental support for ARM-64, MIPS-64, and PPC-LE. |
| 20 | + |
| 21 | + |
| 22 | +Release 8.34 15-December-2013 |
| 23 | +----------------------------- |
| 24 | + |
| 25 | +As well as fixing the inevitable bugs, performance has been improved by |
| 26 | +refactoring and extending the amount of "auto-possessification" that PCRE does. |
| 27 | +Other notable changes: |
| 28 | + |
| 29 | +. Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match |
| 30 | + an empty string. If it can, pcretest shows this in its information output. |
| 31 | + |
| 32 | +. A back reference to a named subpattern when there is more than one of the |
| 33 | + same name now checks them in the order in which they appear in the pattern. |
| 34 | + The first one that is set is used for the reference. Previously only the |
| 35 | + first one was inspected. This change makes PCRE more compatible with Perl. |
| 36 | + |
| 37 | +. Unicode character properties were updated from Unicode 6.3.0. |
| 38 | + |
| 39 | +. The character VT has been added to the set of characters that match \s and |
| 40 | + are generally treated as white space, following this same change in Perl |
| 41 | + 5.18. There is now no difference between "Perl space" and "POSIX space". |
| 42 | + |
| 43 | +. Perl has changed its handling of \8 and \9. If there is no previously |
| 44 | + encountered capturing group of those numbers, they are treated as the |
| 45 | + literal characters 8 and 9 instead of a binary zero followed by the |
| 46 | + literals. PCRE now does the same. |
| 47 | + |
| 48 | +. Following Perl, added \o{} to specify codepoints in octal, making it |
| 49 | + possible to specify values greater than 0777 and also making them |
| 50 | + unambiguous. |
| 51 | + |
| 52 | +. In UCP mode, \s was not matching two of the characters that Perl matches, |
| 53 | + namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they |
| 54 | + were matched by \h. |
| 55 | + |
| 56 | +. Add JIT support for the 64 bit TileGX architecture. |
| 57 | + |
| 58 | +. Upgraded the handling of the POSIX classes [:graph:], [:print:], and |
| 59 | + [:punct:] when PCRE_UCP is set so as to include the same characters as Perl |
| 60 | + does in Unicode mode. |
| 61 | + |
| 62 | +. Perl no longer allows group names to start with digits, so I have made this |
| 63 | + change also in PCRE. |
| 64 | + |
| 65 | +. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to |
| 66 | + mean "start of word" and "end of word", respectively, as a transition aid. |
| 67 | + |
| 68 | + |
| 69 | +Release 8.33 28-May-2013 |
| 70 | +-------------------------- |
| 71 | + |
| 72 | +A number of bugs are fixed, and some performance improvements have been made. |
| 73 | +There are also some new features, of which these are the most important: |
| 74 | + |
| 75 | +. The behaviour of the backtracking verbs has been rationalized and |
| 76 | + documented in more detail. |
| 77 | + |
| 78 | +. JIT now supports callouts and all of the backtracking verbs. |
| 79 | + |
| 80 | +. Unicode validation has been updated in the light of Unicode Corrigendum #9, |
| 81 | + which points out that "non characters" are not "characters that may not |
| 82 | + appear in Unicode strings" but rather "characters that are reserved for |
| 83 | + internal use and have only local meaning". |
| 84 | + |
| 85 | +. (*LIMIT_MATCH=d) and (*LIMIT_RECURSION=d) have been added so that the |
| 86 | + creator of a pattern can specify lower (but not higher) limits for the |
| 87 | + matching process. |
| 88 | + |
| 89 | +. The PCRE_NEVER_UTF option is available to prevent pattern-writers from using |
| 90 | + the (*UTF) feature, as this could be a security issue. |
| 91 | + |
| 92 | + |
4 | 93 | Release 8.32 30-November-2012 |
5 | 94 | ----------------------------- |
6 | 95 |
|
|
0 commit comments