Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #165621
| From | Ben <ben.usenet@bsb.me.uk> |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Re: Memorizing C operator precedence |
| Date | 2022-04-12 14:50 +0100 |
| Organization | A noiseless patient Spider |
| Message-ID | <877d7u1kcc.fsf@bsb.me.uk> (permalink) |
| References | <memo-20220412132213@ram.dialup.fu-berlin.de> |
ram@zedat.fu-berlin.de (Stefan Ram) writes: > Sometimes, one might want to write x==0&y==0 without > shortcut evaluation (to avoid a jump-operation), so "&" > has less precedence than "==". A more common reason (at least in my experience) is when you want to do a bunch of things and return if they were all successful: return do_this() & and_that() & the_other(); (though !(do_this() | and_that() | the_other()) is often safer). -- Ben.
Back to comp.lang.c | Previous | Next — Next in thread | Find similar
Re: Memorizing C operator precedence Ben <ben.usenet@bsb.me.uk> - 2022-04-12 14:50 +0100 Re: Memorizing C operator precedence fir <profesor.fir@gmail.com> - 2022-05-08 03:10 -0700
csiph-web