3 ms·
Yes, that also sucks. Every undefined behavior in a language standard is a failure of the standard making process, and should be a source of shame. Sometimes
by pfdietz 7y ago
Yes, that also sucks.
Every undefined behavior in a language standard is a failure of the standard making process, and should be a source of shame. Sometimes it's politically unavoidable (because there are multiple implementations that do something different), or practically unavoidable (the best behavior is not yet known, or impossible to make precise) but every such imprecision is a landmine through which bugs, often insidious ones, can enter programs.