| 81 |
and -d etc. It's slightly incompatible, but I'm hoping nobody is still |
and -d etc. It's slightly incompatible, but I'm hoping nobody is still |
| 82 |
using it. It makes it easier to run collection of tests with study enabled, |
using it. It makes it easier to run collection of tests with study enabled, |
| 83 |
and thereby test pcre_study() more easily. |
and thereby test pcre_study() more easily. |
| 84 |
|
|
| 85 |
|
15. When (*ACCEPT) was used in a subpattern that was called recursively, the |
| 86 |
|
restoration of the capturing data to the outer values was not happening |
| 87 |
|
correctly. |
| 88 |
|
|
| 89 |
|
16. If a recursively called subpattern ended with (*ACCEPT) and matched an |
| 90 |
|
empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole |
| 91 |
|
pattern had matched an empty string, and so incorrectly returned a no |
| 92 |
|
match. |
| 93 |
|
|
| 94 |
|
17. There was optimizing code for the last branch of non-capturing parentheses, |
| 95 |
|
and also for the obeyed branch of a conditional subexpression, which used |
| 96 |
|
tail recursion to cut down on stack usage. Unfortunately, not that there is |
| 97 |
|
the possibility of (*THEN) occurring in these branches, tail recursion is |
| 98 |
|
no longer possible because the return has to be checked for (*THEN). These |
| 99 |
|
two optimizations have therefore been removed. |
| 100 |
|
|
| 101 |
|
18. If a pattern containing \R was studied, it was assumed that \R always |
| 102 |
|
matched two bytes, thus causing the minimum subject length to be |
| 103 |
|
incorrectly computed because \R can also match just one byte. |
| 104 |
|
|
| 105 |
|
|
| 106 |
Version 8.12 15-Jan-2011 |
Version 8.12 15-Jan-2011 |
Parent Directory
| 
Revision Log
| 
Patch