sweet sassy molassy... what if the implementation defines that behavior as spawning small gnomes? Then it's OK? That would be defined and implementation-defined, but so what?
We are talking about end-result expectations! Geez. On Jan 9, 2014, at 9:56 AM, Steinar H. Gunderson <sgunder...@bigfoot.com> wrote: > On Thu, Jan 09, 2014 at 09:52:57AM -0500, Jim Jagielski wrote: >> Undefined means that the specification does not define >> what happens, and that people cannot expect anything, >> since what happens is implementation dependent. > > As an example: Undefined means it could crash. Or, as the saying goes, the > compiler could spawn small gnomes poking fun at the programmer. That's > certainly not allowed for unsigned-to-signed conversion overflow :-) > > /* Steinar */ > -- > Homepage: http://www.sesse.net/ >
