Re: [pcre-dev] (*SKIP:NAME) when (*MARK:NAME) is in assertion

2018-07-13 Thread ND via Pcre-dev
On 2018-07-13 16:08, ph10 wrote: When SKIP has a name, it backtracks until it hits a MARK with the same name. Why it need to backtrack? Why not do a "bumpalong" advance to the next starting character strait away? -- ## List details at https://lists.exim.org/mailman/listinfo/pcre-dev

Re: [pcre-dev] (*SKIP:NAME) when (*MARK:NAME) is in assertion

2018-07-13 Thread ph10
On Fri, 13 Jul 2018, ND via Pcre-dev wrote: > The SKIP verb don't need backtracking after it fires: there is bumpalong and > new match. If MARK position is saved then there is no problem for engine to > discard current matching and start new matching at saved position without any > backtracking.

Re: [pcre-dev] (*SKIP:NAME) when (*MARK:NAME) is in assertion

2018-07-13 Thread ND via Pcre-dev
On 2018-07-13 07:23, ph10 wrote: On Thu, 12 Jul 2018, ND via Pcre-dev wrote: And one more thing should also be clarified in docs: > MARK name unlike MARK position is saved outside assertion or atomic group: The MARK position *is* saved; it's just that there is never a backtrack into an

Re: [pcre-dev] (*SKIP:NAME) when (*MARK:NAME) is in assertion

2018-07-13 Thread ph10
On Thu, 12 Jul 2018, ND via Pcre-dev wrote: > And one more thing should also be clarified in docs: > MARK name unlike MARK position is saved outside assertion or atomic group: The MARK position *is* saved; it's just that there is never a backtrack into an atomic group, so that data is never