Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!camelback!volpe
From: volpe@camelback.crd.ge.com (Christopher R Volpe)
Newsgroups: comp.lang.c
Subject: Re: When do you use "if ( a = b )"? (was Re: Funny mistake)
Message-ID: <18107@crdgw1.crd.ge.com>
Date: 1 Apr 91 16:05:29 GMT
References: <1991Mar18.195351.11985@unlv.edu> <11109@dog.ee.lbl.gov> <15053@ganymede.inmos.co.uk> <3482@inews.intel.com> <20137@alice.att.com> <18099@crdgw1.crd.ge.com>
Sender: news@crdgw1.crd.ge.com
Reply-To: volpe@camelback.crd.ge.com (Christopher R Volpe)
Lines: 19

In article <18099@crdgw1.crd.ge.com>, I wrote
|>In article <20137@alice.att.com>, ark@alice.att.com (Andrew Koenig) writes:
|>|>I believe that this behavior on the part of the compiler
|>|>is entirely reasonable.
|>
|>Even if it's completely non-conforming?
|>

Nevermind. I checked and noticed that the behavior is undefined in case
of an overflow. (I thought it was just an implementation defined result, 
and therefore the value of the expression is all that matters, and that would
be the same in each case.)

Now, if a,b, and c were unsigned...
                            
==================
Chris Volpe
G.E. Corporate R&D
volpecr@crd.ge.com