Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ucla-cs!maui.cs.ucla.edu!jon
From: jon@maui.cs.ucla.edu (Jonathan Gingerich)
Newsgroups: comp.std.c
Subject: Re: Function Argument Evaluation
Message-ID: <1991Mar27.181158.15594@cs.ucla.edu>
Date: 27 Mar 91 18:11:58 GMT
References: <17882@crdgw1.crd.ge.com> <15591@smoke.brl.mil> <17937@crdgw1.crd.ge.com>
Sender: usenet@cs.ucla.edu (Mr. News Himself)
Organization: UCLA Computer Science Department
Lines: 18
Nntp-Posting-Host: maui.cs.ucla.edu

First a sincere thanks to everyone trying to help.  Second, a reminder that
precision and meticulousness can often be mistaken for pedantry and rudeness,
especially if people are not addressing the central issue.  Both Christopher
and I realize the assignment may cause a type conversion, and we both realize
different sequences of operations can have different results.  Thank you.  You
can stop posting such examples now.

I originally wanted to satisfy my own curiosity about this and pointed out
that the answers so far were not in agreement.  I still have a question so
let me rephrase it:

Is there any situation where the value stored at l can change before (l=r)
is evaluated but after the assignment, without causing the program to be
undefined?
If so, is the value of (l=r) nonetheless restricted to the value of l 
_immediately_ after the assignment?

Jon.