[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1294124330.6617.15.camel@Joe-Laptop>
Date: Mon, 03 Jan 2011 22:58:50 -0800
From: Joe Perches <joe@...ches.com>
To: Dan Carpenter <error27@...il.com>
Cc: Andy Whitcroft <apw@...onical.com>, linux-kernel@...r.kernel.org,
kernel-janitors@...r.kernel.org
Subject: Re: [patch] checkpatch: putting the && or || on the wrong line
On Tue, 2011-01-04 at 08:59 +0300, Dan Carpenter wrote:
> This patch makes checkpatch.pl complain if you break up conditions in
> the wrong way.
>
> Wrong:
> if ((really_long_condition)
> && (second_condition)) { ...
> Right:
> if ((really_long_condition) &&
> (second_condition)) { ...
>
> If you do it in the wrong way the message is: "put the && or || at the
> end of the previous line"
>
> Signed-off-by: Dan Carpenter <error27@...il.com>
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index e3c7fc0..0a813db 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -1509,6 +1509,11 @@ sub process {
> WARN("please, no space before tabs\n" . $herevet);
> }
>
> +# check for && or || at the start of a line
> + if ($rawline =~ /^\+\W+(&&|\|\|)/) {
This should be /^\+[ \t]*(&&|\|\|)/
> + WARN("put the && or || at the end of the previous line\n" . $herecurr);
I've submitted something like this a couple of times and gotten
various objections but I think it's sensible.
https://lkml.org/lkml/2009/12/5/65
https://lkml.org/lkml/2010/7/11/92
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists