Talk:Unspecified behavior

Whose behavior?
While it may be well-known to programmers, the article (especially the intro) is rather vague and unspecified about the behavior that is the subject of this article. Is it behavior on the part of the compiler itself, on the part of the hardware running the compiled program, or what? This should be understandable to laymen, and I don't know enough to make the change. --Piledhigheranddeeper (talk) 15:43, 1 December 2009 (UTC)
 * I've further altered your edit, as it was not strictly correct. I definitely see your point, though. Will try to come up with a better wording. decltype (talk) 15:56, 1 December 2009 (UTC)

Seldom encountered
I reverted the bit about UsB being seldom encountered. It is true that externally visible UsB is not so frequent, but even the simplest of programs are likely to contain some code whose behavior is not fully defined, and where the compiler is not required to document its behavior. I'm thinking for example about the order of construction / destruction of temporaries in an expression like "a = b + c", or the order of the function calls in code like "f(g, h)". These are specified in Java, but not in most languages. decltype (talk) 21:02, 1 December 2009 (UTC)