From: Arjan van de Ven <arjan@infradead.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH 0/9] -Wshadow: Making the kernel build clean with -Wshadow
Date: Mon, 10 Jul 2006 15:06:31 +0200 [thread overview]
Message-ID: <1152536791.4874.43.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <d120d5000607100603r7ac59457tc1b080a15ed84db3@mail.gmail.com>
On Mon, 2006-07-10 at 09:03 -0400, Dmitry Torokhov wrote:
> On 7/10/06, Arjan van de Ven <arjan@infradead.org> wrote:
> >
> > > So, what do people say?
> >
> >
> > Hi,
> >
> > I'm just about always in favor of having automated tools help us find
> > bugs. However... can you give an indication of how many real bugs you
> > have encountered? If it's "mostly noise" all the time.. then it's maybe
> > not worth the effort... while if you find real bugs then it's obviously
> > worthwhile to go through this.
> >
>
> While we may not have any issues with the present code it can help
> avoiding problems in new code if we have -Wshadow by default.
I agree with that; however that still depends on the ratio of real bugs
vs "noise". While it's hard to estimate for future code, the existing
code base can be an indication...
next prev parent reply other threads:[~2006-07-10 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 12:48 Jesper Juhl
2006-07-10 12:53 ` Arjan van de Ven
2006-07-10 13:00 ` Jesper Juhl
2006-07-10 13:03 ` Dmitry Torokhov
2006-07-10 13:06 ` Arjan van de Ven [this message]
2006-07-10 13:13 ` Jesper Juhl
2006-07-10 13:23 ` Valdis.Kletnieks
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=1152536791.4874.43.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®