a function is sort of a container for bugs. hope this helps!!https://twitter.com/pressron/status/1019247570231746560 …
-
Show this thread
-
in reply to
@theowl84, I definitely did not mean to imply that all bugs can be contained in functions. our field was forced to invent files, file systems, and networks to contain all the kinds of bugs that we wanted to write.3 replies 5 retweets 30 likesShow this thread -
Replying to @johnregehr @theowl84
We got plenty of undefined behavior that requires zero functions ;-)
2 replies 0 retweets 2 likes -
All you need is an empty file. No newline is UB!
1 reply 0 retweets 3 likes -
-
Replying to @volatile_void @jfbastien and
a shocking breach of backwards compatibility
1 reply 0 retweets 3 likes -
Replying to @johnregehr @volatile_void and
I think it's just a matter of matching the definition of a text file. Single newline is a one-line file containing an empty line. No chars is a zero-line file. Violation only arises when you have >=1 chars with no newline at end, thus not a line and not a text file.
1 reply 0 retweets 0 likes -
Replying to @RichFelker @johnregehr and
How a file is read in is impl-def though. e.g. a BOM won't count as a character, \n and/or \r is moot, and trigraph is still valid even if C++17 removed them. So all of this is silly!
1 reply 0 retweets 1 like
You can think of it as alignment with POSIX, where none of that applies and the definition of text file is as I wrote.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.