Robert Dewar <[EMAIL PROTECTED]> writes:

[...]

| By the way, does traditional C really assume this? Is
| it the case that the original K&R document guarantees
| wrapping, or is what you meant here "traditional C
| compilers". There is quite a difference!

K&R C leaves arithmetic overflow undefined (except for unsigned
types), in the sense that you get whatever the underlying hardware
gives you.  If it traps, you get trapped.  If it wraps, you get wrapped.

-- Gaby


Reply via email to