From: "Mike Goodwin" <mike.goodwin@cantab.net>
To: linux-sparse@vger.kernel.org
Subject: Style checking
Date: Mon, 30 Apr 2007 00:30:45 -0700 [thread overview]
Message-ID: <c38fc0de0704300030x6ab610acge10482904056d1db@mail.gmail.com> (raw)
Hi,
I have begun modifying sparse (read: adding in various hooks to the
preprocessing and parsing stages) in order to be able to use it as a
style checker. Checking rules such as order of includes, function and
variable naming ... etc.
The style checking is intended to be for linux/driver modules and as
far as I am aware the only two freely available c parsers which can
parse all the headers in the linux kernel are those that are part of
sparse and gcc. As sparse is a lot simpler to modify it seems the
logical choice
So I was wondering:-
1) if anyone had used sparse similarly?
2) would it ever be desirable to have this kind of feature as a part of sparse?
3) is there anything wrong with this approach?!
- Mike
next reply other threads:[~2007-04-30 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 7:30 Mike Goodwin [this message]
2007-05-01 18:09 ` Style checking Josh Triplett
2007-05-03 16:34 ` Uwe Kleine-König
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=c38fc0de0704300030x6ab610acge10482904056d1db@mail.gmail.com \
--to=mike.goodwin@cantab.net \
--cc=linux-sparse@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;
as well as URLs for NNTP newsgroup(s).