Re: Easily-Read C++?

[ncohen@watson.ibm.com (Norman H. Cohen)]

In article <37emsq$smg@gnat.cs.nyu.edu>, dewar@cs.nyu.edu (Robert Dewar)
writes: 

|> is it permissible for ++c to STORE a different value from what it returns?
...
|> Reading the C standard clearly does not answer my question, so we must
|> presume that the two sequences of code have quite a different effect.

Actually, the C standard clearly indicates that this can happen even in
circumstances that do not involve concurrency.  The second paragraph of
ANSI C section 3.3 (which I think of as the ANSI C answer to Ada RM
section 11.6, at least in its ability to keep language lawyers busy
trying to interpret it) states: 

        Between the previous and next sequence point an object shall have
   its stored value modified at most once by the evaluation of an
   expression.  Furthermore, the prior value shall be accessed only to
   determine the value stored.[34]

   -------

   [Footnote 34] This paragraph renders undefined statement expressions
   such as

      i = ++i + 1;

   while allowing

      i = i + 1;

Sequence points are defined syntactically.  They include, for example,
the points after the evaluation of the left operand of the &&, ||, and
comma operators and the ends of statements.  The definition appears to me
to presume a single-threaded model of execution.

I suspect that a large portion of the C code in the field has technically
undefined semantics because it violates the quoted paragraph.

--
Norman H. Cohen    ncohen@watson.ibm.com