From: Michael Snyder <msnyder@vmware.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [doc/gdbint] Mention some formatting guidelines for casts and unary operators
Date: Tue, 01 Feb 2011 18:48:00 -0000 [thread overview]
Message-ID: <4D485589.7060600@vmware.com> (raw)
In-Reply-To: <201102011628.32860.pedro@codesourcery.com>
Pedro Alves wrote:
> This is a follow up to a discussion from last November
> <http://sourceware.org/ml/gdb-patches/2010-11/msg00121.html>,
> that sort of came up today again.
>
> It imports and casts to stone these recommendations (from GCC):
>
> Use... ...instead of
> !x ! x
> ~x ~ x
> -x (unary minus) - x
> (foo) x (cast) (foo)x
> *x (pointer dereference) * x
>
>
> which we have been largely following already anyway.
>
> Okay?
Good by me.
Suggest also:
(type *) (cast) instead of (type*)
(type *name) (prototype) instead of (type* name)
next prev parent reply other threads:[~2011-02-01 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 16:28 Pedro Alves
2011-02-01 18:48 ` Michael Snyder [this message]
2011-02-01 18:50 ` Eli Zaretskii
2011-02-04 17:01 ` Pedro Alves
2011-02-04 18:29 ` Eli Zaretskii
2011-02-04 19:12 ` Pedro Alves
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=4D485589.7060600@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
/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