--- In [email protected], "entropyreduction" <alancampbelllists+ya...@...> wrote:
> /If the previous match WAS for an empty string, we can't do that, as it would > lead to an > //infinite loop. Instead, a special call of pcre_exec() is made with > // the PCRE_NOTEMPTY and PCRE_ANCHORED flags set. The first of these tells > PCRE that an empty string is not a valid match; > //other possibilities must be tried. The second flag restricts PCRE to one > match attempt at the > //initial string position. If this match succeeds, an alternative to the > empty string match has been > //found, and we can proceed round the loop; > > > So resultPostNoMatchAnchored is what I send back from here to there when > (match with PCRE_NOTEMPTY and PCRE_ANCHORED set) fails. Return mark name > result or not in that situation? > 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. 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). Regards, Sheri
