From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Chris Wedgwood <cw@f00f.org>
Cc: Jeff Garzik <jeff@garzik.org>, Morten Welinder <terra@gnome.org>,
linux-sparse@vger.kernel.org
Subject: Re: [PATCH] sparse: gcc 4.1 warnings
Date: Tue, 11 Apr 2006 11:19:09 +0200 [thread overview]
Message-ID: <20060411091908.GC11643@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20060411091044.GA4359@taniwha.stupidest.org>
On Tue, 11 April 2006 02:10:44 -0700, Chris Wedgwood wrote:
> On Tue, Apr 11, 2006 at 10:56:02AM +0200, J?rn Engel wrote:
>
> > And yes, this is really obnoxious. I have read code before that
> > constantly does
> > (void) this(...);
> > (void) that(...);
> > and didn't like it much. Ignoring the issue and fixing the code
> > checker instead might be a better idea.
>
> why not leave it just as it is?
>
> making code ugly and unreadable because some random very of gcc is
> being stilly doesn't seem ideal
Absolutely!
Jörn
--
You can't tell where a program is going to spend its time. Bottlenecks
occur in surprising places, so don't try to second guess and put in a
speed hack until you've proven that's where the bottleneck is.
-- Rob Pike
prev parent reply other threads:[~2006-04-11 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 4:14 [PATCH] sparse: gcc 4.1 warnings Jeff Garzik
2006-04-10 13:21 ` Morten Welinder
2006-04-11 0:30 ` Jeff Garzik
2006-04-11 8:56 ` Jörn Engel
2006-04-11 9:10 ` Chris Wedgwood
2006-04-11 9:19 ` Jörn Engel [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=20060411091908.GC11643@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=cw@f00f.org \
--cc=jeff@garzik.org \
--cc=linux-sparse@vger.kernel.org \
--cc=terra@gnome.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