Re:Regex character "$" doesn't mean "end-of-string"
by frame_ranger on Wednesday March 20, 2024 @01:00PM
(#39769250)
You couldn’t write a post like this if you didn’t start with a strawman.
Re:Regex character "$" doesn't mean "end-of-string"
by michaelt on Wednesday March 20, 2024 @01:31PM
(#39769657)
Take a look at, for example, these stackoverflow answers about a regex to validate and e-mail address: https://stackoverflow.com/a/8829363
These people are I think not intending to say a newline character is permitted at the end of an e-mail address.
(Of course people using 'grep' would have different expectations for obvious reasons)
Re:Regex character "$" doesn't mean "end-of-string"
by Izkata on Wednesday March 20, 2024 @01:38PM
(#39769753)
Even disregarding whether or not end-of-string is also an end-of-line or not (see all the other comments below), $ doesn't match the newline, similar to zero-width matches like \b, so the newline wouldn't be included in the matched text either way.
I think this series of comments might be clearest: https://news.ycombinator.com/item?id=39764385
Re:Regex character "$" doesn't mean "end-of-string"
by LK5ZJwMwgBbHuVI on Wednesday March 20, 2024 @01:46PM
(#39769860)
Problem is, plenty of software doesn't actually look at the match but rather just validates that there was a match (and then continues to use the input to that match).
In nearly two decades of using regex I think this might be the first time I've heard of $ being end of string. It's always been end of line for me.