| |||||||||||||
It's different viewpoints...It's different viewpoints...Posted May 29, 2011 10:24 UTC (Sun) by mpr22 (subscriber, #60784)In reply to: It's different viewpoints... by anton Parent article: What Every C Programmer Should Know About Undefined Behavior #3/3
My programs behave as intended when compiled with the GNU Compiler Collection version 4.6 at -O2, and when they don't, it's because I didn't correctly express my intention in the first place. It may help that over the years, I've had to deal with sizeof(int) doing what the standard says it might (i.e. not be the same on all platforms), and I've been caught out by sizeof(long) doing the same (I wrote a game on i686 round about the time amd64 was launched; the RNG blew up when someone tried to use it on amd64, because I'd written "long" in a place where what I actually meant was "32 bits"). So in the case of the example above (where a bounded loop became infinite because of the way the compiler treated a body of code whose behaviour is formally undefined under the C standard), I'm not actually all that sympathetic. <stdint.h> exists; it behooves the responsible C programmer to use it.
(Log in to post comments)
|
|||||||||||||