Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!purdue!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: comma operator
Message-ID: <10668@smoke.BRL.MIL>
Date: 4 Aug 89 16:31:50 GMT
References: <10099@mpx2.mpx.com> <93@microsoft.UUCP> <10100@mpx2.mpx.com> <44c53d5b.f9df@gtephx.UUCP> <1351@cbnewsl.ATT.COM> <3287@ohstpy.mps.ohio-state.edu>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 10

In article <3287@ohstpy.mps.ohio-state.edu> SMITHJ@ohstpy.mps.ohio-state.edu writes:
>Maybe I'm mistaken, but I'm sure that all the documentation I've read warns
>that the *comma* operator ----does not----- guarantee evaluation in any order.
>Specifically, the Microsoft 5.0 manual mentions this.

Are you sure you're not confusing the comma separating two function
arguments with the comma operator?  The comma operator has ALWAYS
been defined to evaluate its LHS before its RHS.  If the MicroSoft
5.0 manual claims otherwise, then either it's wrong or they're
trying to cover up a SEVERE bug in their compiler!