Unspecified behavior
suggest changeRemarks
If the behavior of a construct is unspecified, then the standard places some constraints on the behavior, but leaves some freedom to the implementation, which is not required to document what happens in a given situation. It contrasts with implementation-defined behavior, in which the implementation is required to document what happens, and undefined behavior, in which anything can happen.
Found a mistake? Have a question or improvement idea?
Let me know.
Table Of Contents