-
Notifications
You must be signed in to change notification settings - Fork 11
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
Incorrect processing when lookaheads are enabled #3
Comments
I had a quick look at the code, and cannot see what to patch. I suspect I could spend a great deal of time studying this code before daring to patch anything. |
Np I only came across this because I was just curious if I would get speedups from the lookaheads since the generated regex is like ~800k chars long haha (without lookaheads). Then when I was testing I noticed I was getting different outputs so I looked into it and just figured I would submit a bug report. Thanks for looking into it. Not sure if you want this bug to stay open for future validation or whatever... you can just close it if you want. |
Hi Adam On 15/12/15 07:31, Adam Lesperance wrote:
Ahhh. Good to know it's not a real inconvenience.
I'll keep it open. These are the sorts of things any new code I write And it's a warning to potential - and current - users of the module of Ron Savage - savage.net.au |
There are 2 use cases I've identified so far; hopefully this should be enough info for you to reproduce.
Output:
I'm using
Regexp::Assemble 0.36
& here's my perl build info:The text was updated successfully, but these errors were encountered: