Path: utzoo!attcan!uunet!munnari.oz.au!mel.dit.csiro.au!yarra!melba.bby.oz.au!leo!zvs
From: zvs@bby.oz.au (Zev Sero)
Newsgroups: comp.lang.c
Subject: Re: An overview ...
Message-ID: <1990Jul4.020809.7619@melba.bby.oz.au>
Date: 4 Jul 90 02:08:09 GMT
References: <1990Jul1.065531.18620@acc.stolaf.edu>
Sender: news@melba.bby.oz.au
Distribution: comp
Organization: Burdett, Buckeridge and Young Ltd.
Lines: 18
In-Reply-To: hannum@haydn.psu.edu's message of 1 Jul 90 06:55:31 GMT

In article <1990Jul1.065531.18620@acc.stolaf.edu> hannum@haydn.psu.edu (Charles Hannum) writes:

   In a lot of cases, C operator precedence sucks.  (I can quote K&R saying the
   same thing -- different wording, of course.  Lets not argue about this point.)
   How does one deal with it?

   My solution:  Most of the time I know.  When I don't, I try it one way, and if
   it doesn't work right, I put parentheses in to force the issue.  Many times I
   just add them to begin with.

My solution: Photocopy the table on page 49 of K&R1 (Page 53 of K&R2
is not as neat looking), and stick it on the wall next to your screen.
When in doubt (and even when not in doubt), look it up.
--
				Zev Sero  -  zvs@bby.oz.au
...but we've proved it again and again
that if once you have paid him the danegeld,
you never get rid of the Dane.		- Rudyard Kipling