11 Jul
2007
11 Jul
'07
3:16 p.m.
Bryan O'Sullivan wrote:
Richard Kelsall wrote:
I guess there must be a switch to make it produce a nice error message rather than overflowing without warning.
Actually, there isn't.
I for one sometimes wish there was... Of course, sometimes you purposely write code which you know is going to overflow and wrap round in a specific way. But frequently you *don't* want this behaviour - and I wish there were some pragma or something to make this be checked. AFAIK, most CPU types give you an efficient way to testing for such conditions...