> if you aim for compiler independence then you don't use [undefined behavior]. I think the point was that UB occurs in a lot of relatively common cases and pr

> if you aim for compiler independence then you don't use [undefined behavior]. I think the point was that UB occurs in a lot of relatively common cases and programmers don't realize that they're depending on it/experiencing it. > If [somehow] you decide [to] target a compiler then you read the compiler's docs. Which is why the post you're responding to made the point about undefined behavior. "Read the compiler's docs" is in counterpoint to that post's parent, which praises C for being a small language, and thus one in which reading the language's docs is seldom required.