Sequence points and side effects in C

by

My question are;
1.What does it mean by, 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.?

With a sub-expression like i++, i is written to. Moreover, assignment is an expression, so in i = 2, i is written to. It may not be immediately obvious that a = b is an expression, but it is. This is why you can do things like a = b = c, which is good, and if (a = b) which is less good.

So what it is saying is that if you write to i, with =, or pre- or post- increment, then any access to i must be as part of the calculation of the new value of i. However, and this is important, the only thing involved in the calculation of pre and post increment is the value of i at the start of the statement.

2.what does it mean by, The example a[i] = i++ 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++)

Precisely what it says. When you access i in a[i] it is not part of the calculation of the new value of i that results from i++.

Could someone explain it in some easy way?

Easy way: Don’t use pre or post increment in an expression. always use them in statements by themselves. If you really really must, do NOT use the same variable anywhere else in the entire statement.

More Related Contents:

  1. Why are these constructs using pre and post-increment undefined behavior?
  2. In C99, is f()+g() undefined or merely unspecified?
  3. Given the state of the stack and registers, can we predict the outcome of printf’s undefined behavior
  4. Undefined behavior and sequence points
  5. (Why) is using an uninitialized variable undefined behavior?
  6. Can we change the value of an object defined with const through pointers?
  7. Is the “struct hack” technically undefined behavior?
  8. sequence points in c
  9. Undefined behavior and sequence points reloaded
  10. Is accessing a global array outside its bound undefined behavior?
  11. How undefined is undefined behavior?
  12. A question about union in C – store as one type and read as another – is it implementation defined?
  13. When is casting between pointer types not undefined behavior in C?
  14. Is the output of printf (“%d %d”, c++, c); also undefined?
  15. What is Undefined Behaviour in C? [duplicate]
  16. Unspecified, undefined and implementation defined behavior WIKI for C
  17. How to implement memmove in standard C without an intermediate copy?
  18. Is this undefined C behaviour?
  19. Is while(1); undefined behavior in C?
  20. Order of evaluation of arguments in function calling?
  21. C code with undefined results, compiler generates invalid code (with -O3)
  22. printf() with no arguments in C compiles fine. how?
  23. When is it valid to access a pointer to a “dead” object?
  24. Is it Undefined Behaviour to cast away the constness of a function parameter?
  25. C – is an indeterminate value indeterminable?
  26. Does ctype.h still require unsigned char?
  27. Why is undefined behaviour allowed in C
  28. Cast T[][] to T*
  29. 2D Array indexing – undefined behavior?
  30. Uninitialized variable in C [duplicate]

Leave a Comment