From: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
To: Josh Triplett <josh@freedesktop.org>
Cc: Mike Goodwin <mike.goodwin@cantab.net>, linux-sparse@vger.kernel.org
Subject: Re: Style checking
Date: Thu, 3 May 2007 18:34:53 +0200 [thread overview]
Message-ID: <20070503163452.GA21333@informatik.uni-freiburg.de> (raw)
In-Reply-To: <46378276.8060307@freedesktop.org>
Hello,
Josh Triplett wrote:
> In addition to the warnings you suggest, I'd love to see a warning for "Header
> not self-contained": a header does not #include all the headers it needs, and
> instead relied on the inclusion of another header first.
IIRC X oblige you to use a certain order of #include's, and there might
be some headers in the linux kernel that are not self-contained on
purpose. But this should not stop you (or anyone else) to implement
such checks :-)
The other way round is interesting, too: "Header included but unused."
This could be used to speed up rebuilds if build dependencies are
auto-generated.
Best regards
Uwe
--
Uwe Kleine-König
http://www.google.com/search?q=1+degree+celsius+in+kelvin
next prev parent reply other threads:[~2007-05-03 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 7:30 Style checking Mike Goodwin
2007-05-01 18:09 ` Josh Triplett
2007-05-03 16:34 ` Uwe Kleine-König [this message]
2007-05-11 10:25 ` Mike Goodwin
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=20070503163452.GA21333@informatik.uni-freiburg.de \
--to=ukleinek@informatik.uni-freiburg.de \
--cc=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=mike.goodwin@cantab.net \
/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).