Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!brl-adm!adm!PEPRBV%CFAAMP.BITNET@wiscvm.wisc.EDU
From: PEPRBV%CFAAMP.BITNET@wiscvm.wisc.EDU
Newsgroups: comp.lang.c
Subject: living with unary +
Message-ID: <6995@brl-adm.ARPA>
Date: Tue, 21-Apr-87 09:25:59 EST
Article-I.D.: brl-adm.6995
Posted: Tue Apr 21 09:25:59 1987
Date-Received: Wed, 22-Apr-87 02:45:40 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.