Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!brl-adm!adm!PEPRBV@cfaamp.bitnet
From: PEPRBV@cfaamp.bitnet
Newsgroups: comp.lang.c
Subject: living with unary +
Message-ID: <6974@brl-adm.ARPA>
Date: Mon, 20-Apr-87 07:26:35 EST
Article-I.D.: brl-adm.6974
Posted: Mon Apr 20 07:26:35 1987
Date-Received: Tue, 21-Apr-87 00:32:44 EST
Sender: news@brl-adm.ARPA
Lines: 8

-----------
>> Larry Cipriani <lvc@danews.ATT.COM> suggests a new cast operator
>>  x = (eval)(a + b) + c;
to force order of evaluation.  Seems to me you could define a
macro to do essentially this within the ANSI spec:
   #define EVAL(x) (+(x))
Usage of EVAL where order of operation was known to be important
would flag these points and make code maintenance easier.