Re: [pcre-dev] Bactracking controls in subroutines

2018-07-12 Thread ND via Pcre-dev
On 2018-07-12 16:55, ph10 wrote: There are no subroutine calls in the second, so it looks like a Perl bug. You are right. It's a bug. I will report it. Can you please also report about Perl inconsistence that we discuss in "No capture in nested negative assertions"? -- ## List

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

2018-07-12 Thread ND via Pcre-dev
On 2018-07-12 07:25, ph10 wrote: The (*MARK) is inside the assertion. That is what matters. I haveupdated the documentation to say this: The search for a (*MARK) name uses the normal backtracking mechanism, which means that it does not see (*MARK) settings that are inside atomic groups or

Re: [pcre-dev] Bactracking controls in subroutines

2018-07-12 Thread ph10
On Tue, 3 Jul 2018, ND via Pcre-dev wrote: > PCRE2 version 10.31 2018-02-12 > /(?1)(*F)|(a(*COMMIT))/ > a > 0: a > 1: a > > > In Perl this pattern not matched. > Is there weighty reason to stay backtracking controls not "cross-subroutine" > when backtracking is cross-subroutine? And stay

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

2018-07-12 Thread ph10
On Wed, 11 Jul 2018, ND via Pcre-dev wrote: > I seen this docs before. > But in example verb not appears inside assertion. It appears after it. The (*MARK) is inside the assertion. That is what matters. I have updated the documentation to say this: The search for a (*MARK) name uses the