Re:You Can't Always Hash Pointers in C
by lmm on Tuesday May 31, 2016 @05:26PM
(#11810400)
I suppose it's less the phrase itself than the concept. What would be a way to say "integer overflow behaviour may reflect the underlying machine, but must be sensible", rigorously enough for the C standard? We've established that "undefined behaviour" is too broad, and "implementation-defined value" is too narrow.
[ Parent
| on HN ]
Why "must be sensible"? Why not just say "signed integer overflow is implementation-defined" and in a footnote say "for example, it may wrap, trap, saturate, or do anything else documented by your implementation"?
I'm not seeing the big deal here.
> Why "must be sensible"? Why not just say "signed integer overflow is implementation-defined" and in a footnote say "for example, it may wrap, trap, saturate, or do anything else documented by your implementation"?
I don't think that actually defines anything - I don't think GCC would interpret that as anything other than undefined behaviour.