On Undefined Behavior

Question

Generally, UB is regarded as being something that has to be avoided, and the current C standard itself lists quite a few examples in appendix J.

However, there are c

Answer 1

If the standard says that doing something is undefined, then it is undefined. You may like to think you can predict what the outcome will be, but you can't. For a specific compiler you may always get the same result, but for the next iteration of the compiler, you may not.

And undefined behaviour is so EASY to avoid - don't write code like that! So why do people like you want to mess with it?