61–70 of 382 posts
I can hear thousands of bad hiring manager's adding 'How do you match the end of a string in a regex?' to their list of 'Ha! You don't know the trick!' questions designed to catch out candidates.
"I will hire you anyway, but I will pay you less" Regex, useful in any job...
if you know where to find something no point in knowing it.
Special misery case: Visual Studio supports regex search, where '$' matches \n. The end of line character is usually the standard Windows \r\n. Yes, that means if you want to really match the end of line you have to match "\r$". So broken.
FWIW, and I know this doesn't really address your complaint: I use Windows and I've set all my text editors to use LF exclusively years ago and Things Are Great. No more weird Git autocrlf warnings, no quirks when copying files over to/from people on Macs or Linuxes, etc. Even Notepad supports LF line endings for quite a long time now - to my practical experience, there's little remaining in Windows that makes CRLF "…
The new line is just empty but not the first line anymore.
Earlier quoted context omitted.
Same, tho it'd be interesting to see if this behavior holds if the file ends without a trailing newline and your match is on the final newline-less line.
Fortunately, it's pretty simple to test. $ printf 'Line with EOL\nLine without EOL' | grep 'EOL$' Line with EOL Line without EOL $ grep --version | head -n1 grep (GNU grep) 3.8
It's not matching the newline character after all.
> Folks who've worked with regular expressions before might know about ^ meaning "start-of-string" and correspondingly see $ as "end-of-string". Huh. I always think of them as "start-of-line" and "end-of-line". I mean, a lot of the time when I'm working with regexes, I'm working with text a line at a time so the effect is the same, but that doesn't change how I think of those operators. Maybe because a fair amount of…
Isn't a string with a newline character automatically multiline? The new line is just empty but not the first line anymore.
3.195 Incomplete Line
A sequence of one or more non- characters at the end of the file.
3.206 Line
A sequence of zero or more non- characters plus a terminating character.
Text File
[...] The definition of "text file" has caused controversy. The only difference between text and binary files is that text files have lines of less than {LINE_MAX} bytes, with no NUL characters, each terminated by a . The definition allows a file with a single , or a totally empty file, to be called a text file. If a file ends with an incomplete line it is not strictly a text file by this definition. [...]
[1] https://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xbd...
> Note: The table of data was gathered from regex101.com, I didn't test using the actual runtimes. Has anyone confirmed this behaviour directly against the runtimes/languages? Newlines at the end of a string are certainly something that could get lost in transit inside an online service involving multiple runtimes.
> Newlines at the end of a string are certainly something that could get lost in transit inside an online service involving multiple runtimes. In what way could newlines at the end of a string "could get lost in transit"?
There are plenty of other ways, too; bugs happen.
That's one of the benefits of a complete rethink/rewrite, you can learn from the fact that the old behavior surprised people.
Does anyone consider RegEx to be standardised? Moving to a new context is always a relearning exercise in my experience.
So, yes, at least someone (me) considers regex to be standardized in several published de jure standards.
[0] https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3690.pdf#chapter.28
[1] https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html
[2] https://262.ecma-international.org/14.0/#sec-regexp-regular-expression-objects