--- In power-pro@yahoogroups.com, "Sheri" <sheri...@...> wrote:
> So I was correct! when I guessed "Maybe that is connected with the > plugin advancing the start position and retrying a match, in a > multiple match operation." I'm going to go out on a limb and say No, don't > bother with mark for resultPostNoMatchAnchored. Okay. > Noticed another small issue with current test version. When > hRE.pcreReplaceCallback is used, even without the "mark" option, the plugin > is manipulating regex_mark (I can tell because PP complains if it is > undeclared, e.g., existing usage of pcreReplaceCallback function). Okay. As usual don't have source code in front of me but may be fixed in latest: regexPlugin210_100706.zip > You sez: Because regex_mark is retaining the mark set for a previous > pattern/execution even > when a new pattern/execution has the "mark" plugin option set. Okay, now if (but only if) new pattern/execution has "mark" option set, regex_mark is set to null string before pcre_exec called for first time. > You sez: What of the other optimization something you said previously, i.e., > to eliminate sending a PCRE extra block except when called for? done regexCallout.powerpro uses dll plugin to break up pcre_callout block Using sPattern = "(?C1)ec(.)e" Isn't (.) a capture? capture_last always returns -1 never shows a capture. That right?
