Every time someone says "I know C but others don't, and they make UB mistakes but I don't", I make them take this test. It's just five questions.
hackernoon.com
Undefined Behavior in 2017
Easton Nelson
Camden Jackson
I don't think we're understanding each other. Of course, most C code has undefined behaviour, and of course it's impossible to avoid. I mean, the execution order of statements within function calls is undefined, so pretty much even a Hello World has UB.
What I'm saying, it's UB that doesn't actually matter and that you shouldn't be caring about, because it doesn't alter the program correctness, and if it does, then you have been programming like a retard.
For example, whether foo(a+b, b+c); execute a+b or b+c first shouldn't matter at all, and if the statements you put in your parameters do need to be executed in a specific order (functions with side effects, prefix increments, etc.), you shouldn't be putting them there in the first place.
I remember that one blog who bitched about the undefined behaviour of a = 1;foo(++a, ++a, ++a)
If you ever run into such a situation, either you stop trying to write one liners, or your code is retarded, you yourself are retarded and you should go back to coding HTML5.
Using atoi()? Then you should be sure that the pointer you give it is in fact a null-terminated string that represents an integer. Defining behaviour of atoi() on an input it shouldn't get is stupid anyway.
Integer overflow? Why the fuck would you use it in a production codebase anyway besides, maybe, on some obscure embedded platform?
Division by zero? Check your goddamn variables if you know there's a risk such a division will happen.
Missing a return statement at the end of your non-void function? Hang thyself.
Smartass one-liners that can't be easily understood from looking at them? Jump off a bridge.
Relying on the value of unitialized variables? Seriously, just stop.
UB is very much okay, your program's output shouldn't depend on their existence and rustards should keep writing CoCs instead of giving their opinion on a topic they don't understand, that's just the point I'm trying to make. Apologies if I don't make myself clear enough, in fact I think my statement that your program should never run into UB is simply wrong, what I really meant was, UB should never be relevant to you.
Just take a look at retard
It's 4 one-liners/syntax hells that you shouldn't write in any language ever, and the absolute retardation of mutiplying a character by an integer, which you shouldn't write in any language either.
The use of these besides showing the world you're a retard? Absolutely none.
Christopher Reyes
Also LOL @ your page.
Literally someone whose field of expertise is far, far away from C gives his shit opinion on it based on what he's read on en.wikipedia.org
Adrian Edwards
Read the article. He has 15 years of experience in C and learned about this when he worked on a nuclear power plant project. That website isn't even about a single author, and they mix in this guy with girls talking about Bitcoins.
William Adams
...
Gavin Ortiz
Ok, but the relevant point stands still: it's not code you should EVER write in production, not even in Rust or Java, so using it as a basis for criticism of C is simply retarded.
Does C have a lot of disadvantages? Yes. Is UB on unreadable one-liners one of them? No.
It was obvious from the very beginning that the answers would be UB.
Julian Williams
it was obvious from the very beginning that you are a meme spouting retard
Logan Gomez
Hey {{{prrpx}}}, why don't you go back to writing Fizzbuzzes in some toy language?
Kevin Reed
what makes you think im prrpx?
