Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: C and Floating Point
Message-ID: <5733@brl-smoke.ARPA>
Date: Wed, 8-Apr-87 21:25:36 EST
Article-I.D.: brl-smok.5733
Posted: Wed Apr  8 21:25:36 1987
Date-Received: Mon, 13-Apr-87 03:45:53 EST
References: <15958@sun.uucp> <5716@brl-smoke.ARPA> <14680@cca.CCA.COM> <790@xanth.UUCP> <788@kodak.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 11
Keywords: C Fortran Floating Point Parenthases

In article <788@kodak.UUCP> grodberg@kodak.UUCP (Jeremy Grodberg) writes:
>One of the reasons I put parenthases in my #defines is so that I can be sure
>that that will be evaluated before anything around it. 

Then you're making a mistake.  Possibly your particular compiler has these
additional semantics for (), but the C language does not and never has.

What () DO accomplish is to force the syntactic parsing to deal with the
insides of the () before the outside; this can be used to override default
operator precedence and associativity, which SOMETIMES looks like forcing
order of evaluation, but really they're two different things.