From: Derek M Jones <derek@knosof.co.uk>
To: Christopher Li <sparse@chrisli.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
"Robert P. J. Day" <rpjday@crashcourse.ca>,
sparse <linux-sparse@vger.kernel.org>
Subject: Re: Detect unused header files?
Date: Thu, 30 Jul 2009 12:12:31 +0100 [thread overview]
Message-ID: <4A71801F.9060001@knosof.co.uk> (raw)
In-Reply-To: <70318cbf0907300355h5cb34671ha452433c4e0b5324@mail.gmail.com>
Christopher,
> I create a branch "unused-include-files" for some experiment patch.
> Some thing quick and dirty to find out what works and what doesn't.
> No where near submitting quality.
Sorry I meant to post earlier. Projects typically contain around 30%
of unused headers. References to various research articles available
in: c0x.coding-guidelines.com/6.10.2.pdf
--
Derek M. Jones tel: +44 (0) 1252 520 667
Knowledge Software Ltd mailto:derek@knosof.co.uk
Source code analysis http://www.knosof.co.uk
next prev parent reply other threads:[~2009-07-30 11:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 18:18 Detect unused header files? Sam Ravnborg
2009-07-28 20:36 ` Christopher Li
2009-07-28 20:36 ` Robert P. J. Day
2009-07-28 20:49 ` Christopher Li
2009-07-28 21:04 ` Sam Ravnborg
2009-07-28 21:38 ` Christopher Li
2009-07-30 10:55 ` Christopher Li
2009-07-30 11:12 ` Derek M Jones [this message]
2009-07-30 20:36 ` Sam Ravnborg
2009-08-04 21:49 ` Christopher Li
2009-08-05 6:12 ` Sam Ravnborg
2009-08-06 11:14 ` Marko Kreen
2009-08-06 11:17 ` Robert P. J. Day
2009-08-06 12:16 ` Kamil Dudka
2009-08-06 12:15 ` Robert P. J. Day
2009-08-06 13:01 ` Kamil Dudka
2009-08-06 13:26 ` Michael Stefaniuc
2009-08-06 14:09 ` Robert P. J. Day
2009-08-06 17:39 ` Christopher Li
2009-07-28 20:58 ` Sam Ravnborg
2009-07-28 21:21 ` Christopher Li
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=4A71801F.9060001@knosof.co.uk \
--to=derek@knosof.co.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
--cc=sam@ravnborg.org \
--cc=sparse@chrisli.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.