public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Ken Werner <ken@linux.vnet.ibm.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
	       Joel Brobecker <brobecker@adacore.com>,
	Tom Tromey <tromey@redhat.com>,
	       gdb-patches@sourceware.org
Subject: Re: [patch] initial OpenCL C language support
Date: Wed, 27 Oct 2010 21:01:00 -0000	[thread overview]
Message-ID: <201010272301.05902.ken@linux.vnet.ibm.com> (raw)
In-Reply-To: <201010272020.51386.pedro@codesourcery.com>

On Wednesday, October 27, 2010 9:20:50 pm Pedro Alves wrote:
> On Wednesday 27 October 2010 20:04:17, Jan Kratochvil wrote:
> > On Tue, 26 Oct 2010 15:57:47 -0400, Joel Brobecker wrote:
> > > > +      ret = ! value_equal (val1, val2);
> > > > 
> > >               ^^^^^ extra space
> > 
> > GNU Coding Standards contains only this reference to the ! operator:
> >        if (! fp)
> > 
> > (GDB code contains enough of both cases.)
> 
> GCC makes that rule explicit:
> 
> http://gcc.gnu.org/codingconventions.html
> 
> <quote>
> Code in GCC should use the following formatting conventions:
> Use...                     ...instead of
> !x                         ! x
> ~x                         ~ x
> -x (unary minus)           - x
> (foo) x (cast)             (foo)x
> *x (pointer dereference)   * x
> </quote>
> 
> We tend to follow these already, so I'm of the opinion we should
> make them explictily official in gdb too.

Ok, thanks for clarifying. I have changed the code to look like this:
    case BINOP_NOTEQUAL:
      ret = !value_equal (val1, val2);

Regards
Ken

  reply	other threads:[~2010-10-27 21:01 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22 17:21 Ken Werner
2010-10-25 22:41 ` Tom Tromey
2010-10-26 13:05   ` Ken Werner
2010-10-26 13:44     ` Tom Tromey
2010-10-26 16:02       ` Ken Werner
2010-10-26 17:49         ` Eli Zaretskii
2010-10-26 19:58         ` Joel Brobecker
2010-10-26 20:03           ` Joel Brobecker
2010-10-27 13:36             ` Ken Werner
2010-11-02 19:23               ` Joel Brobecker
2010-11-03 13:03                 ` Ken Werner
2010-11-03 15:27                   ` Joel Brobecker
2010-11-04 15:39                     ` Ken Werner
2010-11-04 17:48                       ` Eli Zaretskii
2010-11-05 14:21                         ` Ken Werner
2010-11-05 14:39                     ` Ken Werner
2010-10-27 19:04           ` Jan Kratochvil
2010-10-27 19:21             ` Pedro Alves
2010-10-27 21:01               ` Ken Werner [this message]
2010-11-02 16:52               ` [doc RFA] Switch to GCC coding style [Re: [patch] initial OpenCL C language support] Jan Kratochvil
2010-11-02 17:04                 ` Doug Evans
2010-11-02 17:23                   ` Jan Kratochvil
2010-11-02 17:29                     ` Doug Evans
2010-11-02 19:21                     ` Eli Zaretskii
2010-11-02 19:29                       ` Joel Brobecker
2010-11-08 12:50                       ` Jan Kratochvil
2010-11-08 16:11                         ` Joel Brobecker
2010-11-08 16:38                           ` Mark Kettenis
2010-11-08 16:43                             ` Joel Brobecker
2010-11-08 16:54                             ` Pedro Alves
2010-11-08 18:36                               ` Joel Brobecker
2010-11-02 18:01                   ` Joel Brobecker
2010-11-02 18:10                     ` [doc RFA] Switch to GCC coding style Jan Kratochvil
2010-11-02 18:20                       ` Doug Evans
2010-11-02 18:58                         ` Joel Brobecker
2010-11-02 19:19                           ` Doug Evans

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=201010272301.05902.ken@linux.vnet.ibm.com \
    --to=ken@linux.vnet.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=pedro@codesourcery.com \
    --cc=tromey@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).