Path: utzoo!attcan!uunet!cs.utexas.edu!sun-barr!rutgers!aramis.rutgers.edu!paul.rutgers.edu!emuleomo From: emuleomo@paul.rutgers.edu (Emuleomo) Newsgroups: comp.lang.c Subject: Re: why bother with operator precedence Message-ID: Date: 28 Mar 90 16:35:09 GMT References: <2205@osc.COM> <340018@hplvli.HP.COM> <19356@megaron.cs.arizona.edu> <1379@ux.acs.umn.edu> <2031@l.cc.purdue.edu> <15289@bfmny0.UU.NET> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 14 This is why people say that C code is *hard* to read! Why say a = b >> 4 + 5; when you can say a = b >> (4 + 5); Even DMR may have to dive into his manual once in a while if he sees the former expression, but a C neophyte fully understands what the latter does! Well I guess the former is why we have masochists in society! --Emuleomo O.O. (emuleomo@yes.rutgers.edu) -- *Nothing* is hard. If it looks hard, you are looking at it the hard way!