From: Christopher Li <sparse@chrisli.org>
To: Hannes Eder <hannes@hanneseder.net>
Cc: Kamil Dudka <kdudka@redhat.com>, sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] linearize.h: sanitize header
Date: Thu, 6 Aug 2009 10:10:30 -0700 [thread overview]
Message-ID: <70318cbf0908061010w737ac3d7j1feb1f9744217df7@mail.gmail.com> (raw)
In-Reply-To: <154e089b0908060409v4dff4785x456b5aad2460ed84@mail.gmail.com>
On Thu, Aug 6, 2009 at 4:09 AM, Hannes Eder<hannes@hanneseder.net> wrote:
>> $ grep --color '[^_]false[^_]' *.c
>
> $ grep --color '\bfalse\b\|\btrue\b' *.c | wc -l
> 91
>
> some of them are just in comments, does not look to scary to me. If
> others agree that its a good idea to rename them, I can do it if you
> don't want to.
I would just apply the change to the header file and related variables.
The linearize.h is consider an API header file for other sparse application
to use. So we'd better not assume too much on the sparse caller side.
I agree with Kamil that rename variable in linearize.c offer no real
benefits. I consider it more of a personal preference thing. And it is
internal to linearize.c. At this point renaming variable will mess up with
annotations. It is not good enough reason to do it just to make
the editor happy.
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-08-06 17:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 9:02 [PATCH] linearize.h: sanitize header Kamil Dudka
2009-08-06 9:23 ` Hannes Eder
2009-08-06 9:30 ` Kamil Dudka
2009-08-06 9:39 ` Hannes Eder
2009-08-06 9:51 ` Kamil Dudka
2009-08-06 11:09 ` Hannes Eder
2009-08-06 17:10 ` Christopher Li [this message]
2009-08-06 17:27 ` Kamil Dudka
2009-08-06 17:49 ` Hannes Eder
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=70318cbf0908061010w737ac3d7j1feb1f9744217df7@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=hannes@hanneseder.net \
--cc=kdudka@redhat.com \
--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).