Re: making undefined behaviour defined

I agree with Mr Sossman in considering that integer overflow
is a poor example for what you are saying.

In lcc-win32, using a compiler option makes integer
overflow TRAP, what (I think) is quite useful.

Better a trap than INCORRECT RESULTS!

Of course only signed integers trap, unsigned do not.

Making mandatory to accept integer overflow would destroy this
and make the C language a construct with no hope of getting
sensible results and catching programmer errors...

jacob
.