Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sdd.hp.com!ucsd!ucbvax!DECWRL.DEC.COM!mwm
From: mwm@DECWRL.DEC.COM (Mike  Meyer, My Watch Has Windows)
Newsgroups: comp.society.futures
Subject: Re: C's sins of commission (was: (pssst...fortran?))
Message-ID: <9009202236.AA21344@raven.pa.dec.com>
Date: 20 Sep 90 22:36:24 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 24

>> >The intent was to determine the byte ordering of the machine the code was
>> >running on.
>> >
>> >	<mike
>> 
>> How about something as simple as:

I goofed. Should have stated the problem, rather than trying to
demonstrate it.

The problem is with order of evaluation. You generally have to choose
between three options:

1) Don't allow side effects, so that normally it isn't critical.

2) Specify it exactly, so you can predict side effects.

3) Leave it "undefined".

This problem arises in all expressions, not just function arguments.
There are problems with all three solutions. I was curious as to which
was going to be taken in this case.

	<mike