qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Change variable "name" to avoid shadow warnings
Date: Sun, 10 Jun 2007 20:17:02 +0300	[thread overview]
Message-ID: <f43fc5580706101017r7f6af56t3b9195be7bcbd72a@mail.gmail.com> (raw)
In-Reply-To: <466C16C9.9090803@mail.berlios.de>

On 6/10/07, Stefan Weil <weil@mail.berlios.de> wrote:
> Maybe it would be a good idea to add more warnings to the
> QEMU compiler options. The current option -Wall (in files
> Makefile.target, configure) does not activate all warnings.
>
> I think that especially -Wshadow should be added because code
> with shadowed variables is more difficult to read and maintain
> (and potentially contains more bugs).

I'd vote for -Wcast-align, but I'd be happy with any stricter set of warnings.

      reply	other threads:[~2007-06-10 17:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-10 15:20 [Qemu-devel] [PATCH] Change variable "name" to avoid shadow warnings Stefan Weil
2007-06-10 17:17 ` Blue Swirl [this message]

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=f43fc5580706101017r7f6af56t3b9195be7bcbd72a@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.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 NNTP newsgroup(s).