| 1 |
ChangeLog for PCRE |
ChangeLog for PCRE |
| 2 |
------------------ |
------------------ |
| 3 |
|
|
| 4 |
|
Version 8.20 |
| 5 |
|
------------ |
| 6 |
|
|
| 7 |
|
1. Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had |
| 8 |
|
a POSIX class. After further experiments with Perl, which convinced me that |
| 9 |
|
Perl has bugs and confusions, a closing square bracket is no longer allowed in |
| 10 |
|
a POSIX name. |
| 11 |
|
|
| 12 |
|
|
| 13 |
Version 8.13 16-Aug-2011 |
Version 8.13 16-Aug-2011 |
| 14 |
------------------------ |
------------------------ |
| 15 |
|
|
| 198 |
For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also, |
For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also, |
| 199 |
unescaped square brackets may also appear as part of class names. For |
unescaped square brackets may also appear as part of class names. For |
| 200 |
example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves |
example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves |
| 201 |
more like Perl. |
more like Perl. (But see 8.20/1 above.) |
| 202 |
|
|
| 203 |
38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this |
38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this |
| 204 |
was because it thought it was \N{name}, which is not supported). |
was because it thought it was \N{name}, which is not supported). |