From: Kamil Dudka <kdudka@redhat.com>
To: Hannes Eder <hannes@hanneseder.net>
Cc: sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] linearize.h: sanitize header
Date: Thu, 6 Aug 2009 11:51:11 +0200 [thread overview]
Message-ID: <200908061151.11277.kdudka@redhat.com> (raw)
In-Reply-To: <154e089b0908060239g56261ecp916d7b937014a6fd@mail.gmail.com>
On Thu August 6 2009 11:39:11 Hannes Eder wrote:
> >> I guess it is wise to change this in linearize.c as well. Mind sending
> >> a patch?
> >
> > The question is if we need/want to :-) It's change of the working code
> > for no real benefit. I am talking only about system-wide headers which
> > can be included anywhere.
>
> Well I see at least one benefit, a small one though. Syntax
> highlighting is somewhat confused with "true" and "false", at least
> emacs is. They appear like the constants, where in fact they are
> variables.
I can confirm it's the same case with the vim's syntax highlighter.
> The likelyhood to break the code by renaming this two variables is
> kinda low, no? And IHMO it was not so wise in the first place to pick
> these names. ;)
I would contend that only two variables are affected. They are if we consider
only headers. However the situation is much worse when we concern about .c
files. The patch would be non-trivial. Please try the following command:
$ grep --color '[^_]false[^_]' *.c
Kamil
next prev parent reply other threads:[~2009-08-06 9:49 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 [this message]
2009-08-06 11:09 ` Hannes Eder
2009-08-06 17:10 ` Christopher Li
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=200908061151.11277.kdudka@redhat.com \
--to=kdudka@redhat.com \
--cc=hannes@hanneseder.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).