Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Tim Rentsch Newsgroups: comp.lang.c Subject: Re: Remembering C's operator precedence rules Date: Wed, 13 Mar 2019 09:26:27 -0700 Organization: A noiseless patient Spider Lines: 10 Message-ID: <86wol2rb9o.fsf@mailhub.linuxsc.com> References: <87lg1o9efx.fsf@bsb.me.uk> <1bh8cb93bi.fsf@pfeifferfamily.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader02.eternal-september.org; posting-host="649889cd88840859fa7eb936884ada21"; logging-data="23052"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+audadmsRSCP2ZICT0o8JZ2lVB9RAES7M=" User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux) Cancel-Lock: sha1:Jki0PUvLf/LwQVVTKPbEB7RC2S4= sha1:L2jHuUMQwrwZpNhSVie2D5Mwb/M= Xref: csiph.com comp.lang.c:141937 Richard Damon writes: > C probably could have put & and * at the same level and | and + on > the same level (with ^ in between) to meat this need, but there > may have been some common usage that made it better to put them > where they are as a distinct set of levels. I thought it was well known that early C didn't have && and ||, so the bitwise operators &, ^, and | were put below the comparison operators so they could be used as logical connectives.