From: Joe Perches <joe@perches.com>
To: Shailendra Verma <shailendra.capricorn@gmail.com>
Cc: Andy Whitcroft <apw@canonical.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts:checkpatch - Do not give error if static bool or global bool variables are assigned to false value.
Date: Tue, 26 May 2015 18:57:00 -0700 [thread overview]
Message-ID: <1432691820.2846.133.camel@perches.com> (raw)
In-Reply-To: <1432688995-2931-1-git-send-email-shailendra.capricorn@gmail.com>
On Wed, 2015-05-27 at 06:39 +0530, Shailendra Verma wrote:
> The bool value false is not always to be 0.
By definition (7.16 Boolean type and values <stdbool.h>),
false is integer 0.
Setting a boolean variable to 0 is equivalent to
setting it to false.
What I think you mean is that a boolean variable can be
set to 0 when false might be more intelligible.
> So this patch will
> prevent for error if static bool or global bool are initialized
> with false value.
[]
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> # check for global initialisers.
> - if ($line =~ /^\+(\s*$Type\sa*$Ident\s*(?:\s+$Modifier))*\s*=\s*(0|NULL|false)\s*;/) {
> + if ($line =~ /^\+(\s*$Type\s*$Ident\s*(?:\s+$Modifier))*\s*=\s*(0|NULL)\s*;/) {
> if (ERROR("GLOBAL_INITIALISERS",
> "do not initialise globals to 0 or NULL\n" .
> $herecurr) &&
I think using false adds some clarity for the reader and
even if something were to be applied, the error message
should probably be "do not initialize globals to $2\n"
(choose the spelling of your choice for initialise/initialize)
The (0|NULL|false) regex could probably be expanded to
(0x0+|0|NULL|false) or that regex could be saved as a
$our zero_value and tested using that new variable.
[]
> # check for static initialisers.
> - if ($line =~ /^\+.*\bstatic\s.*=\s*(0|NULL|false)\s*;/) {
> + if ($line =~ /^\+.*\bstatic\s.*=\s*(0|NULL)\s*;/) {
> if (ERROR("INITIALISED_STATIC",
> "do not initialise statics to 0 or NULL\n" .
> $herecurr) &&
$1 here
next prev parent reply other threads:[~2015-05-27 1:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 1:09 [PATCH] scripts:checkpatch - Do not give error if static bool or global bool variables are assigned to false value Shailendra Verma
2015-05-27 1:57 ` Joe Perches [this message]
[not found] ` <CA+tKcn_1VUQ1cEXYpkPwn3BsSHv3uiY-d2_sfbt_59ZL=jpDfw@mail.gmail.com>
2015-05-27 3:23 ` Joe Perches
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=1432691820.2846.133.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shailendra.capricorn@gmail.com \
/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