Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
The reason why it is undefined behaviour instead of a hard error is that the problem of determining it is, quite literally, equivalent to the halting problem. So any implementation will either warn...
Answer
#1: Initial revision
by
celtschk
·
2024-10-07T21:06:57Z (about 1 month ago)
The reason why it is undefined behaviour instead of a hard error is that the problem of determining it is, quite literally, equivalent to the halting problem. So any implementation will either warn about cases where a return cannot actually happen,or miss cases where it can happen, or both. Different implementations will probably make different tradeoffs when giving that warning, and will differ in the effort they put into deciding whether to warn or not. I wouldn't even rely on different versions of the same compiler giving consistent results.