On Wednesday, August 17, 2011 7:30:10 PM UTC+1, Amahdy wrote: > > the compiler behavior is not random, >
Maybe. But that's beside the point. If we are talking about a particular compiler, then you are right: One could dissect what the compiler does. The first step would be to look at the machine code produced (assuming that there is any). And I agree that this is a worthwhile exercise. If we are talking about the language, however, then one should consider *any* possible compiler. In other words, one should only look at the language specification. And according to the language specification, the compiler can do *anything* at all if two side-effects on the same value aren't sequenced. (Where 'sequenced' is a precisely defined term.) -- You received this message because you are subscribed to the Google Groups "google-codejam" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-code/-/Z0J9bqolvFoJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code?hl=en.
