From: Willy Tarreau <willy@w.ods.org>
To: Christian Neumair <christian-neumair@web.de>
Cc: Hell.Surfers@cwctv.net, kaos@ocs.com.au, linux-kernel@vger.kernel.org
Subject: Re: RE:2.4.19 warnings with allnoconfig
Date: Sun, 4 Aug 2002 10:16:20 +0200 [thread overview]
Message-ID: <20020804081620.GA13316@alpha.home.local> (raw)
In-Reply-To: <1028447908.4339.3.camel@kellerbar.lan.net>
On Sun, Aug 04, 2002 at 09:58:25AM +0200, Christian Neumair wrote:
> > 2.4.19 with make allnoconfig produces these warnings.
>
> Just a hint:
> There is almost no software with completely clean code.
> Whenever you see one compiling and it produces no warnings it's most
> likely that the build script just suppresses warnings.
I completely disagree with you. I try hard to make my programs
compile without a warning with -Wall, even if it sometimes makes
the code a bit more difficult to read (mainly because of
parenthesis and casts). This way, I have fairly reduced portability
issues with 32/64 bits, LE/BE machines.
Just a hint :-)
It is always bad to ignore the compiler's complaints, because it tells
you that it may do things wrong when it's not sure about what you want.
Spending hours fixing a few warnings in the kernel has already led me
to fix some bugs that only a compiler or an attentive human would have
detected, specially when indentation fools you. Eg, this common mistake :
if (something1)
if (something 2)
do_2();
else
do_not_1();
Cheers,
Willy
next prev parent reply other threads:[~2002-08-04 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 3:38 Hell.Surfers
2002-08-04 7:58 ` Christian Neumair
2002-08-04 7:59 ` Aschwin Marsman - aYniK Software Solutions
2002-08-04 8:16 ` Willy Tarreau [this message]
2002-08-04 10:00 ` Ged Haywood
2002-08-04 10:05 ` Tomas Szepe
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=20020804081620.GA13316@alpha.home.local \
--to=willy@w.ods.org \
--cc=Hell.Surfers@cwctv.net \
--cc=christian-neumair@web.de \
--cc=kaos@ocs.com.au \
--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®