| 1 |
ChangeLog for PCRE |
ChangeLog for PCRE |
| 2 |
------------------ |
------------------ |
| 3 |
|
|
| 4 |
|
Version 7.4 10-Sep-07 |
| 5 |
|
--------------------- |
| 6 |
|
|
| 7 |
|
1. Change 7.3/28 was implemented for classes by looking at the bitmap. This |
| 8 |
|
means that a class such as [\s] counted as "explicit reference to CR or |
| 9 |
|
LF". That isn't really right - the whole point of the change was to try to |
| 10 |
|
help when there was an actual mention of one of the two characters. So now |
| 11 |
|
the change happens only if \r or \n (or a literal CR or LF) character is |
| 12 |
|
encountered. |
| 13 |
|
|
| 14 |
|
2. The 32-bit options word was also used for 6 internal flags, but the numbers |
| 15 |
|
of both had grown to the point where there were only 3 bits left. |
| 16 |
|
Fortunately, there was spare space in the data structure, and so I have |
| 17 |
|
moved the internal flags into a new 16-bit field to free up more option |
| 18 |
|
bits. |
| 19 |
|
|
| 20 |
|
3. The appearance of (?J) at the start of a pattern set the DUPNAMES option, |
| 21 |
|
but did not set the internal JCHANGED flag - either of these is enough to |
| 22 |
|
control the way the "get" function works - but the PCRE_INFO_JCHANGED |
| 23 |
|
facility is supposed to tell if (?J) was ever used, so now (?J) at the |
| 24 |
|
start sets both bits. |
| 25 |
|
|
| 26 |
|
|
| 27 |
Version 7.3 28-Aug-07 |
Version 7.3 28-Aug-07 |
| 28 |
--------------------- |
--------------------- |
| 29 |
|
|
Parent Directory
| 
Revision Log
| 
Patch