Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!sco!seanf
From: seanf@sco.COM (Sean Fagan)
Newsgroups: comp.sys.mips
Subject: Re: compiler bug
Message-ID: <5191@scolex.sco.COM>
Date: 14 Mar 90 10:42:32 GMT
References: <36721@mips.mips.COM> <18302@shamash.cdc.com> <36884@mips.mips.COM>
Sender: news@sco.COM
Reply-To: seanf@sco.COM (Sean Fagan)
Organization: The Santa Cruz Operation, Inc.
Lines: 23


In article <36884@mips.mips.COM> rogerk@servitude.mips.com (Roger B.A. Klorese) writes:
>>#define  PushArg(n)              argStack[argStackP++] = n
>>#define  PopArg()                argStack[--argStackP]
>>  temp = PopArg() + PopArg();
>    When evaluating the actual arguments in a function call, the order in
>    which the arguments are evaluated is not specified; but the program
>    must behave as if it chose one argument, evaluated it fully, then chose
>    another argument, evaluated it fully, and so on. . . .

Uhm, I don't see a function call there.  I see to macros which are expanded.

If you are going to continue this, please move it to comp.lang.c, where it
belongs.  Please note that Chris Torek has already replied to this, and he
is considered a comp.lang.c.deity (right up there with Doug Gwyn and Henry
Spencer, right below Dennis Ritchie 8-)).

-- 

-----------------+
Sean Eric Fagan  | "Time has little to do with infinity and jelly donuts."
seanf@sco.COM    |    -- Thomas Magnum (Tom Selleck), _Magnum, P.I._
(408) 458-1422   | Any opinions expressed are my own, not my employers'.