David Brown wrote:

Thanks for giving us the official rules.  That makes it even more important
to avoid "a = b = c" constructs, especially for volatile data.  I knew about
function argument evaluation ordering (or lack thereof), but I was not sure
about such multiple assignments (in fact, I was wrong about them !).

David
Ditto the thanks! Folks like me that rely on K&R might want to mark it up a bit :) My 2nd Ed., which has a big red ANSI C stamp on the cover, uses the construct. (pp20-21).

Garst


Reply via email to