Skip to content
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

Quantified (*COMMIT) fails to fire #14983

p5pRT opened this issue Oct 13, 2015 · 1 comment


Copy link

@p5pRT p5pRT commented Oct 13, 2015

Migrated from (status was 'new')

Searchable as RT126343$


This comment has been minimized.

Copy link
Collaborator Author

@p5pRT p5pRT commented Oct 13, 2015


Hi Yves,

Here is another (*COMMIT) behavior that feels wrong (it fails to fire).

if ('1213' =~ /(?​:1(*COMMIT)2)+./ ) { print "\$&='$&'\n"; }
# $&='121'

The engine matches '12', then it matches '1' and the (*COMMIT) token.
When the second '2' fails, the engine somehow manages to backtrack across (*COMMIT), which never fires.

@p5pRT p5pRT added the Severity Low label Oct 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.