Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!decwrl!amdcad!nucleus!tim
From: tim@nucleus.amd.com (Tim Olson)
Newsgroups: comp.lang.c
Subject: Re: Is this a bug in Turbo C 2.0?
Message-ID: <29477@amdcad.AMD.COM>
Date: 13 Mar 90 01:42:10 GMT
References: <3210@pur-phy> <60@datcon.UUCP> <E24hr$1@cs.psu.edu> <29446@amdcad.AMD.COM> <2374@dataio.Data-IO.COM>
Sender: news@amdcad.AMD.COM
Reply-To: tim@amd.com (Tim Olson)
Organization: Advanced Micro Devices, Inc., Austin, Texas
Lines: 14
Summary:
Expires:
Sender:
Followup-To:

In article <2374@dataio.Data-IO.COM> bright@Data-IO.COM (Walter Bright) writes:
| In article <29446@amdcad.AMD.COM> tim@amd.com (Tim Olson) writes:

      [ some incorrect drivel about order of evaluation and casting]

| Not true. The order of evaluation is undefined, but the *binding* is
| defined.

Walter is right.  I had just been looking at some code that relied
upon order-of-evaluation, and had that on the brain... ;-)

	-- Tim Olson
	Advanced Micro Devices
	(tim@amd.com)