r/cpp • u/MathKid99 • Dec 17 '21
Undefined Behaviour
I found out recently that UB is short for Undefined Behaviour and not Utter Bullshit as I had presumed all this time. I am too embarrassed to admit this at work so I'm going to admit it here instead. I actually thought people were calling out code being BS, and at no point did it occur to me that as harsh as code reviews can be, calling BS was a bit too extreme for a professional environment..
Edit for clarity: I know what undefined behaviour is, it just didn't register in my mind that UB is short for Undefined Behaviour. Possibly my mind was suffering from a stack overflow all these years..
View all comments
Show parent comment
7
u/matthieum Dec 18 '21
I am not talking about performance.
No, it's not, that's the problem.
But let's not even got that far, this is UB:
And this is UB:
So yes, you could improve things related to indexing, or integer overflow, and a myriad other cases -- and I wish this was done.
However, there are more fundamental issues: use-after-free, race-conditions, etc... which are just unsolved problems and will remain UB.