Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Accelerate blocks sorting
Date: Mon, 22 Jun 2009 18:35:00 -0000	[thread overview]
Message-ID: <20090622183526.GA31281@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3r5xcnmzx.fsf@fleche.redhat.com>

On Mon, 22 Jun 2009 20:26:26 +0200, Tom Tromey wrote:
> This is also http://sourceware.org/bugzilla/show_bug.cgi?id=9988

Forgot to search for it again, sorry.


> Jan> +  return (BLOCK_START (b) > BLOCK_START (a))
> Jan> +	 - (BLOCK_START (b) < BLOCK_START (a));
> 
> This expression needs parens around it, according to GNU rules.

GNU Coding Standards provides this sample code line:
         return ++x + bar ();

Moreover it has no sample code (and found no rules) with `return' using parens.
GDB uses `return' with parens a lot but I find it a GNU style violation by GDB
fixing it along in the patches.

Sure no problem to change it but is there any backing for such parens?



> I think you don't actually need a cleanup here, as nothing here can
> call error.  However, if you want to leave it, that is also ok with
> me.

I did not notice, still I find the code safer that way.


Thanks,
Jan


  reply	other threads:[~2009-06-22 18:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 17:39 Jan Kratochvil
2009-06-22 18:15 ` Michael Snyder
2009-06-22 18:26   ` Jan Kratochvil
2009-06-22 18:26 ` Tom Tromey
2009-06-22 18:35   ` Jan Kratochvil [this message]
2009-06-22 19:26     ` Tom Tromey
2009-06-22 19:51       ` Jan Kratochvil

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=20090622183526.GA31281@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --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