linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@canonical.com>
To: Eric Nelson <eric.nelson@boundarydevices.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-kbuild@vger.kernel.org, joe@perches.com
Subject: Re: [PATCH V3] checkpatch: check for whitespace before semicolon at EOL
Date: Mon, 28 May 2012 15:42:59 +0100	[thread overview]
Message-ID: <20120528144259.GA5878@dm> (raw)
In-Reply-To: <1338163246-6727-1-git-send-email-eric.nelson@boundarydevices.com>

On Sun, May 27, 2012 at 05:00:46PM -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())
> 		;
> 
> Signed-off-by: Eric Nelson <eric.nelson@boundarydevices.com>
> ---
>  scripts/checkpatch.pl |    7 +++++++
>  1 files changed, 7 insertions(+), 0 deletions(-)
> 
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index faea0ec..2262e1f 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -2448,6 +2448,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);
> +		}
> +

Would this not also falsly trigger on 'for (foo = 10; foo; foo--) {' ?

>  # Check operator spacing.
>  		if (!($line=~/\#\s*include/)) {
>  			my $ops = qr{

-apw

  reply	other threads:[~2012-05-28 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-28  0:00 [PATCH V3] checkpatch: check for whitespace before semicolon at EOL Eric Nelson
2012-05-28 14:42 ` Andy Whitcroft [this message]
2012-05-28 15:12   ` Joe Perches
2012-05-28 15:15   ` Eric Nelson

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=20120528144259.GA5878@dm \
    --to=apw@canonical.com \
    --cc=akpm@linux-foundation.org \
    --cc=eric.nelson@boundarydevices.com \
    --cc=joe@perches.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@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).