An ambiguity in c89 which will never be fixed
runningmike
15 points
3 comments
August 10, 2026
Related Discussions
Found 5 related stories in 210.1ms across 13,334 title embeddings via pgvector HNSW
- Reducing undefined behavior in the C language chmaynard · 27 pts · September 28, 2026 · 51% similar
- Reducing undefined behavior in the C language signa11 · 79 pts · October 09, 2026 · 51% similar
- C++26 Disapproved thatxliner · 190 pts · November 04, 2026 · 48% similar
- Getting silly with C, part and((int*)-8)[3] surprisetalk · 26 pts · August 21, 2026 · 48% similar
- Type Punning in C and C++ ingve · 36 pts · September 22, 2026 · 46% similar
Discussion Highlights (2 comments)
guenthert
"because the problematic behavior was removed from the standard over 27 years ago, we'll never have closure on what the intended interpretation is." Obsolete standard turns out to be insufficiently strict, news at 11.
bellowsgulch
All the weird stuff I have read about C or C++ doing over the years could be summed up with “Well… don’t do that.” Like almost without fail. I can’t even think of how you’d end up in a scenario like this because a compiler would complain before letting you use an undefined implicit declaration.