From: Tim Hollebeek <tim@hollebeek.com>
To: gcc@gcc.gnu.org
Subject: Re: Coding convention: use of `!x' vs. `! x'
Date: Fri, 22 Sep 2000 10:22:00 -0000 [thread overview]
Message-ID: <200009221636.MAA14919@cj44686-b.reston1.va.home.com> (raw)
In-Reply-To: <200009221648.MAA04946@mal-ach.watson.ibm.com>
David Edelsohn writes ...
>
> Richard> What about the other unary operators? Should they have a blank, like the
> Richard> binary operators do, or no blank, like "!" now will?
One practical advantage of using "!x" (and similar for all other unary
operators) is that it is visually consistent with the C precedence
rules.
5 - ~ x + 1 // less clear
5 - ~x + 1 // better
// more realistic example
y + * x + 1
y + *x + 1
-Tim
next prev parent reply other threads:[~2000-09-22 10:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-22 9:32 Richard Kenner
2000-09-22 9:41 ` GNU long long Matt Minnis
2000-09-22 13:33 ` Joseph S. Myers
2000-09-22 9:50 ` Coding convention: use of `!x' vs. `! x' David Edelsohn
2000-09-22 10:22 ` Gabriel Dos Reis
2000-09-22 10:22 ` Tim Hollebeek [this message]
2000-09-30 9:52 ` Mark Mitchell
-- strict thread matches above, loose matches on Subject: below --
2000-09-26 4:36 Jamie Lokier
[not found] <969652582.12981.ezmlm@gcc.gnu.org>
2000-09-22 17:00 ` Tim Josling
2000-09-22 18:21 ` Stan Shebs
2000-09-22 21:44 ` Mark Mitchell
2000-09-25 2:04 ` Akim Demaille
2000-09-25 7:29 ` Mark Mitchell
2000-09-25 11:32 ` Phil Edwards
2000-09-26 1:29 ` Andreas Schwab
2000-09-22 0:29 Mark Mitchell
2000-09-24 22:57 ` Geoff Keating
2000-09-24 23:43 ` Mark Mitchell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200009221636.MAA14919@cj44686-b.reston1.va.home.com \
--to=tim@hollebeek.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).