Re^3: regex gotcha moving from 5.8.8 to 5.30.0?

That's fascinating, thank you! It looks like through blind luck I've been frozen-in-time with a version whose performance happened to complement the way I was trying to tackle the parsing problem...

For my side, I suppose I can stick with 5.8.8, or jump to 5.30+ by possibly changing my regexes as sw1 and SBECK have suggested to avoid "\s* ^ \s*" and compromising a little on the strictness of the parser.

But for the sake of Perl, however, is there a recommended escalation path to alert the developers about this regression / add it to the test suite / etc? Or is it niche enough not to be interesting?

Comment on Re^3: regex gotcha moving from 5.8.8 to 5.30.0?

Replies are listed 'Best First'.
Re^4: regex gotcha moving from 5.8.8 to 5.30.0? by Animator (Hermit) on Feb 12, 2021 at 17:16 UTC
Just a FYI: perl developers are already aware. (but I suppose you could still create an issue for it; less chance for it to be forgotten) It's also been discussed a bit on the #p5p IRC channel.	[reply]
Re^5: regex gotcha moving from 5.8.8 to 5.30.0? by demerphq (Chancellor) on Feb 12, 2021 at 21:47 UTC
https://github.com/Perl/perl5/issues/18566 --- $world=~s/war/peace/g	[reply]
Re^6: regex gotcha moving from 5.8.8 to 5.30.0? by erzuuli (Cannon) on Feb 12, 2021 at 22:36 UTC
OMG! Look who it is! :-D	[reply]
Re^4: regex gotcha moving from 5.8.8 to 5.30.0? by rsFalse (Chaplain) on Feb 11, 2021 at 22:17 UTC
You can try perlbug - 'how to submit bug reports on Perl'. Or ask someone else to create a ticket. Also you can add a link to this perlmonks forum discussion. I think it is a regression of at least of medium severity.	[reply]