Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Add -Wempty-body to warning set (was: Re: RFC: fix bug in compare_breakpoints)
Date: Fri, 19 Oct 2012 16:41:00 -0000	[thread overview]
Message-ID: <508182BF.1010206@redhat.com> (raw)
In-Reply-To: <87lif2wi6c.fsf@fleche.redhat.com>

[Changing $subject.  As with all warning set addition, this is likely to introduce
new -Werror build failures on other hosts/ports.]

On 10/19/2012 05:16 PM, Tom Tromey wrote:
> Tom> The other problem is caught by -Wempty-body, which we don't enable.  It
> Tom> yields a number of warnings and would require a coding style change
> Tom> from:
> [...]
> 
> FWIW, here's the patch.  Comments appreciated.
> 
> I do think it is a mild improvement.  It is a lot easier to mistype a
> ";" than a correctly formatted brace pair.

I agree it's a mild improvement.  Though I'm surprised at how few cases
in common code this reveals -- I thought we had more of:

while (...)
  ;

FAOD, this is fine with me.

Thanks.

-- 
Pedro Alves


  reply	other threads:[~2012-10-19 16:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17 19:36 RFC: fix bug in compare_breakpoints Tom Tromey
2012-10-17 21:25 ` Joel Brobecker
2012-10-18 20:07   ` Tom Tromey
2012-10-18  8:53 ` Pedro Alves
2012-10-18 20:06   ` Tom Tromey
2012-10-19 16:17     ` Tom Tromey
2012-10-19 16:41       ` Pedro Alves [this message]
2012-10-19 16:44         ` Add -Wempty-body to warning set Tom Tromey
2012-10-19 17:00       ` RFC: fix bug in compare_breakpoints Joel Brobecker
2012-10-19 17:03         ` Tom Tromey
2012-10-19 17:12           ` Joel Brobecker
2012-10-19 17:18             ` Pedro Alves
2012-11-02 18:52       ` Tom Tromey

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=508182BF.1010206@redhat.com \
    --to=palves@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