| 1 |
ChangeLog for PCRE |
ChangeLog for PCRE |
| 2 |
------------------ |
------------------ |
| 3 |
|
|
| 4 |
Version 8.10 03 May-2010 |
Version 8.10 03-Jun-2010 |
| 5 |
------------------------ |
------------------------ |
| 6 |
|
|
| 7 |
1. Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and |
1. Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and |
| 9 |
|
|
| 10 |
2. (*ACCEPT) was not working when inside an atomic group. |
2. (*ACCEPT) was not working when inside an atomic group. |
| 11 |
|
|
| 12 |
3. Inside a character class, \B is treated as a literal by default, but |
3. Inside a character class, \B is treated as a literal by default, but |
| 13 |
faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option |
faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option |
| 14 |
causes the error). The code is unchanged, but I tidied the documentation. |
causes the error). The code is unchanged, but I tidied the documentation. |
| 15 |
|
|
| 16 |
4. Inside a character class, PCRE always treated \R and \X as literals, |
4. Inside a character class, PCRE always treated \R and \X as literals, |
| 17 |
whereas Perl faults them if its -w option is set. I have changed PCRE so |
whereas Perl faults them if its -w option is set. I have changed PCRE so |
| 18 |
that it faults them when PCRE_EXTRA is set. |
that it faults them when PCRE_EXTRA is set. |
| 19 |
|
|
| 20 |
5. Added support for \N, which always matches any character other than |
5. Added support for \N, which always matches any character other than |
| 21 |
newline. (It is the same as "." when PCRE_DOTALL is not set.) |
newline. (It is the same as "." when PCRE_DOTALL is not set.) |
| 22 |
|
|
| 23 |
6. When compiling pcregrep with newer versions of gcc which may have |
6. When compiling pcregrep with newer versions of gcc which may have |
| 24 |
FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite', |
FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite', |
| 25 |
declared with attribute warn_unused_result" were given. Just casting the |
declared with attribute warn_unused_result" were given. Just casting the |
| 26 |
result to (void) does not stop the warnings; a more elaborate fudge is |
result to (void) does not stop the warnings; a more elaborate fudge is |
| 27 |
needed. I've used a macro to implement this. |
needed. I've used a macro to implement this. |
| 28 |
|
|
| 29 |
7. Minor change to pcretest.c to avoid a compiler warning. |
7. Minor change to pcretest.c to avoid a compiler warning. |
| 30 |
|
|
| 31 |
8. Added four artifical Unicode properties to help with an option to make |
8. Added four artifical Unicode properties to help with an option to make |
| 32 |
\s etc use properties (see next item). The new properties are: Xan |
\s etc use properties (see next item). The new properties are: Xan |
| 33 |
(alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word). |
(alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word). |
| 34 |
|
|
| 35 |
9. Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes |
9. Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes |
| 36 |
use Unicode properties. (*UCP) at the start of a pattern can be used to set |
use Unicode properties. (*UCP) at the start of a pattern can be used to set |
| 37 |
this option. Modified pcretest to add /W to test this facility. Added |
this option. Modified pcretest to add /W to test this facility. Added |
| 38 |
REG_UCP to make it available via the POSIX interface. |
REG_UCP to make it available via the POSIX interface. |
|
|
|
|
10. Added --line-buffered to pcregrep. |
|
| 39 |
|
|
| 40 |
11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was |
10. Added --line-buffered to pcregrep. |
| 41 |
studied, and the match started with a letter with a code point greater than |
|
| 42 |
|
11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was |
| 43 |
|
studied, and the match started with a letter with a code point greater than |
| 44 |
127 whose first byte was different to the first byte of the other case of |
127 whose first byte was different to the first byte of the other case of |
| 45 |
the letter, the other case of this starting letter was not recognized. |
the letter, the other case of this starting letter was not recognized |
| 46 |
|
(#976). |
| 47 |
12. pcreposix.c included pcre.h before including pcre_internal.h. This caused a |
|
| 48 |
conflict in the definition of PCRE_EXP_DECL. I have removed the include of |
12. If a pattern that was studied started with a repeated Unicode property |
|
pcre.h as pcre_internal.h includes pcre.h itself. (This may be a bit of |
|
|
historical tidying that never got done.) |
|
|
|
|
|
13. If a pattern that was studied started with a repeated Unicode property |
|
| 49 |
test, for example, \p{Nd}+, there was the theoretical possibility of |
test, for example, \p{Nd}+, there was the theoretical possibility of |
| 50 |
setting up an incorrect bitmap of starting bytes, but fortunately it could |
setting up an incorrect bitmap of starting bytes, but fortunately it could |
| 51 |
not have actually happened in practice until change 8 above was made (it |
not have actually happened in practice until change 8 above was made (it |
| 52 |
added property types that matched character-matching opcodes). |
added property types that matched character-matching opcodes). |
| 53 |
|
|
| 54 |
|
13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of |
| 55 |
|
possible starting bytes for non-anchored patterns. |
| 56 |
|
|
| 57 |
|
14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes |
| 58 |
|
\R, and also a number of cases that involve Unicode properties, both |
| 59 |
|
explicit and implicit when PCRE_UCP is set. |
| 60 |
|
|
| 61 |
|
15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8 |
| 62 |
|
input, it could crash or give wrong results if characters with values |
| 63 |
|
greater than 0xc0 were present in the subject string. (Detail: it assumed |
| 64 |
|
UTF-8 input when processing these items.) |
| 65 |
|
|
| 66 |
|
16. Added a lot of (int) casts to avoid compiler warnings in systems where |
| 67 |
|
size_t is 64-bit (#991). |
| 68 |
|
|
| 69 |
|
17. Added a check for running out of memory when PCRE is compiled with |
| 70 |
|
--disable-stack-for-recursion (#990). |
| 71 |
|
|
| 72 |
|
18. If the last data line in a file for pcretest does not have a newline on |
| 73 |
|
the end, a newline was missing in the output. |
| 74 |
|
|
| 75 |
14. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of |
19. The default pcre_chartables.c file recognizes only ASCII characters (values |
| 76 |
possible starting bytes for non-anchored patterns. |
less than 128) in its various bitmaps. However, there is a facility for |
| 77 |
|
generating tables according to the current locale when PCRE is compiled. It |
| 78 |
|
turns out that in some environments, 0x85 and 0xa0, which are Unicode space |
| 79 |
|
characters, are recognized by isspace() and therefore were getting set in |
| 80 |
|
these tables. This caused a problem in UTF-8 mode when pcre_study() was |
| 81 |
|
used to create a list of bytes that can start a match. For \s, it was |
| 82 |
|
including 0x85 and 0xa0, which of course cannot start UTF-8 characters. I |
| 83 |
|
have changed the code so that only real ASCII characters (less than 128) |
| 84 |
|
are set in this case because the \s etc escapes are documented as |
| 85 |
|
recognizing only ASCII characters. (When PCRE_UCP is set - see 9 above - |
| 86 |
|
the code is different altogether.) |
| 87 |
|
|
| 88 |
|
|
| 89 |
Version 8.02 19-Mar-2010 |
Version 8.02 19-Mar-2010 |