Re^4: Non-greedy match end of line bug?

I get what's going on now, thank you.

I still think it's a bug, or at the very least a major implementation quirk that is incompatible with other regex implementations. Javascript and Golang treat /s the intuitive way and don't make an exception for \n at the end of a string.

Type this into any browser console:

"foo\nbar".match(/(fo.+?)$/s) && RegExp.$1
"foo\n".match(/(fo.+?)$/s) && RegExp.$1
[download]

Or try it on regex101.com - you get different matching results on PCRE vs non-PCRE based engines.

I think it warrants a big warning in perlre. It was a nasty surprise for me even though I am far from being a perl novice.

Comment on Re^4: Non-greedy match end of line bug? Download Code

Replies are listed 'Best First'.
Re^5: Non-greedy match end of line bug? by LanX (Saint) on Oct 26, 2021 at 21:48 UTC
> I still think it's a bug, or at the very least a major implementation quirk that is incompatible with other regex implementations. Well JS claimed from the very beginning on to re-implement the Perl4 regex features. So if anything, then it's JS which is buggy. Furthermore, since when does JS support the `/s` flag? I can see that it works in FF now, but I can't find it documented in MDN !?! Not long ago JS required a "weird" character class like `[^]` to also match newlines, alike `.` with `/s` flag in Perl. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply] [d/l] [select]
Re^6: Non-greedy match end of line bug? by Fletch (Bishop) on Oct 27, 2021 at 00:33 UTC
It's here in the summary table. Specifically /s / dotAll The cake is a lie. The cake is a lie. The cake is a lie.	[reply]