Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!wuarchive!udel!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: Function Argument Evaluation
Message-ID: <15552@smoke.brl.mil>
Date: 22 Mar 91 21:58:56 GMT
References: <17750@crdgw1.crd.ge.com> <15538@smoke.brl.mil> <17809@crdgw1.crd.ge.com>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 8

In article <17809@crdgw1.crd.ge.com> volpe@camelback.crd.ge.com (Christopher R Volpe) writes:
>Ok, but I believe that is true only because the behavior is undefined

No; the order of evaluation in this example is explicitly UNSPECIFIED,
which is not at all the same as UNDEFINED BEHAVIOR.  There are several
possible ways to mix up the order of evaluation, but one of them MUST
be selected by a conforming implementation for each such situation.
(The selection need not be made on a consistent basis, however.)