See also Pascal's followup post, "The previous post was written in jest."[1] "The previous post assumes the reader is familiar with the notion of undefined beh

See also Pascal's followup post, "The previous post was written in jest."[1] "The previous post assumes the reader is familiar with the notion of undefined behavior and how C compilers have started to justify their more aggressive optimizations along the lines of “this program has always been undefined”.... This was not a serious suggestion, but should be understood as an argument in the debate about the exploitation of undefined behavior in compiler optimization.... I was not suggesting to replace the respected restrict keyword with an awkward replacement. All the arguments I put forward were in bad faith." [1]: http://blog.frama-c.com/index.php?post/2012/07/25/The-previous-post-was-written-in-jest http://blog.frama-c.com/index.php?post/2012/07/25/The-previo...