..the second sentence says: if an object is written to within a full expression, any and all accesses to it within the same expression must be directly involved in the computation of the value to be written. This rule effectively constrains legal expressions to those in which the accesses demonstrably precede the modification. For example, the old standby i = i + 1 is allowed, because the access of i is used to determine i’s final value. The example
06000
is disallowed because one of the accesses of i (the one in a[i]) has nothing to do with the value which ends up being stored in i (which happens over in i++), and so there’s no good way to define–either for our understanding or the compiler’s–whether the access should take place before or after the incremented value is stored. Since there’s no good way to define it, the Standard declares that it is undefined, and that portable programs simply must not use such constructs.
Similar to a[i++]=i (which invokes UB) your expression too invokes UB.
C++表达式中的未定义行为解析
本文探讨了C++编程中一个重要的概念——未定义行为(Undefined Behavior)。当在一个表达式中写入一个对象后,所有对该对象的访问都必须直接参与计算新的值。例如,`i=i+1`是允许的,因为访问`i`用于确定其最终值。然而,如`06000`这样的例子是不允许的,因为`a[i]`的访问与`i`的更新无关,这导致无法确定访问应发生在增量之前还是之后。标准规定这种情况下行为是未定义的,因此,为了保证移植性,程序员应避免使用这类构造。

被折叠的 条评论
为什么被折叠?



