| 135 |
pattern matches a fixed length string. PCRE did not allow this; now it |
pattern matches a fixed length string. PCRE did not allow this; now it |
| 136 |
does. Neither allows recursion. |
does. Neither allows recursion. |
| 137 |
|
|
| 138 |
|
25. I finally figured out how to implement a request to provide the minimum |
| 139 |
|
length of subject string that was needed in order to match a given pattern. |
| 140 |
|
(It was back references and recursion that I had previously got hung up |
| 141 |
|
on.) This code has now been added to pcre_study(); it finds a lower bound |
| 142 |
|
to the length of subject needed. It is not necessarily the greatest lower |
| 143 |
|
bound, but using it to avoid searching strings that are too short does give |
| 144 |
|
some useful speed-ups. The value is available to calling programs via |
| 145 |
|
pcre_fullinfo(). |
| 146 |
|
|
| 147 |
|
26. While implementing 25, I discovered to my embarrassment that pcretest had |
| 148 |
|
not been passing the result of pcre_study() to pcre_dfa_exec(), so the |
| 149 |
|
study optimizations had never been tested with that matching function. |
| 150 |
|
Oops. What is worse, even when it was passed study data, there was a bug in |
| 151 |
|
pcre_dfa_exec() that meant it never actually used it. Double oops. There |
| 152 |
|
were also very few tests of studied patterns with pcre_dfa_exec(). |
| 153 |
|
|
| 154 |
|
|
| 155 |
Version 7.9 11-Apr-09 |
Version 7.9 11-Apr-09 |
| 156 |
--------------------- |
--------------------- |