From: Joe Perches <joe@perches.com>
To: Eric Nelson <eric.nelson@boundarydevices.com>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
u-boot@lists.denx.de, rylv50@freescale.com, marex@denx.de,
vapier@gentoo.org
Subject: Re: [PATCH V2] checkpatch: add check for whitespace before semicolon at end-of-line
Date: Fri, 04 May 2012 09:45:24 -0700 [thread overview]
Message-ID: <1336149924.7920.14.camel@joe2Laptop> (raw)
In-Reply-To: <1336147186-27853-1-git-send-email-eric.nelson@boundarydevices.com>
On Fri, 2012-05-04 at 08:59 -0700, Eric Nelson wrote:
> Requires --strict option during invocation:
> ~/linux$ scripts/checkpatch --strict foo.patch
>
> This tests for a bad habits of mine like this:
>
> return 0 ;
>
> Note that it does allow a special case of a bare semicolon
> for empty loops:
>
> while (foo())
> ;
>
> ---
> V2 adds the special case and requirement for --strict based on
> recommendations of Joe Perches.
>
> scripts/checkpatch.pl | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index a3b9782..e711122 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -3227,6 +3227,12 @@ sub process {
> "Statements terminations use 1 semicolon\n" . $herecurr);
> }
>
> +# check for whitespace before semicolon - not allowed at end-of-line
> + if ($line =~ /\S+\s+;$/) {
> + CHK("SPACING",
> + "Whitespace before semicolon\n" . $herecurr);
Hey Eric.
This is still a suboptimal test because it should
allow optional spacing after the semicolon before
the EOL.
if ($line =~ /\S\s+;\s*$/)
I still think it's not really necessary to
check for end of line. It'd also be OK to
report spacing issues on code like:
for (i = 0 ; i < 100 ; i++)
and
case foo: x = 1 ; break;
So maybe the test should be
if ($line =~ /\S\s+;/)
But this test emits a CHK on lines
that add a line with just a ; so that
needs a small update to
if ($line =~ /^\+.*\S\s+;/)
Also the test should probably be adjacent
to all the other "SPACING" tests so maybe:
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index cb08290..aadcfba 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -2461,6 +2461,13 @@ sub process {
"space prohibited between function name and open parenthesis '('\n" . $herecurr);
}
}
+
+# check for whitespace before a non-naked semicolon
+ if ($line =~ /^\+.*\S\s+;/) {
+ CHK("SPACING",
+ "space prohibited before semicolon\n" . $herecurr);
+ }
+
# Check operator spacing.
if (!($line=~/\#\s*include/)) {
my $ops = qr{
prev parent reply other threads:[~2012-05-04 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 15:59 [PATCH V2] checkpatch: add check for whitespace before semicolon at end-of-line Eric Nelson
2012-05-04 16:45 ` Joe Perches [this message]
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=1336149924.7920.14.camel@joe2Laptop \
--to=joe@perches.com \
--cc=eric.nelson@boundarydevices.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=rylv50@freescale.com \
--cc=u-boot@lists.denx.de \
--cc=vapier@gentoo.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