New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(*COMMIT) fires inconsistently when another backtracking control verb occurs to its right #14980
Comments
From 0perlbugs@rexegg.comWhen another backtracking control verb is passed after a (*COMMIT), if that verb is backtracked into, the logical behavior (also adopted by PCRE) is that that verb fires, and (*COMMIT) doesn't. This seems to be the case with (*SKIP) but not (*PRUNE), === Case 1: just (*COMMIT) === === Case 2: (*COMMIT) followed by (*SKIP) === === Case 3: (*COMMIT) followed by (*PRUNE) === |
From @demerphqThanks for the report. I will investigate a bit before I say anything. Yves On 12 October 2015 at 06:50, Rex <perlbug-followup@perl.org> wrote:
-- |
The RT System itself - Status changed from 'new' to 'open' |
From 0perlbugs@rexegg.comThank you. Please let me know if there are tests you'd like me to run in case it's system-related. |
Migrated from rt.perl.org#126328 (status was 'open')
Searchable as RT126328$
The text was updated successfully, but these errors were encountered: