From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: armbru@redhat.com, famz@redhat.com, cornelia.huck@de.ibm.com
Subject: Re: [Qemu-devel] [PATCH 3/5] CODING_STYLE, checkpatch: update line length rules
Date: Wed, 10 Aug 2016 11:48:14 +0200 [thread overview]
Message-ID: <30c0f83d-e9a2-91a3-6c7e-e46a4290aa55@redhat.com> (raw)
In-Reply-To: <1470817370-145190-4-git-send-email-pbonzini@redhat.com>
On 10.08.2016 10:22, Paolo Bonzini wrote:
> Line lengths above 80 characters do exist. They are rare, but
> they happen from time to time. An ignored rule is worse than an
> exception to the rule, so do the latter.
>
> Some on the list expressed their preference for a soft limit that
> is slightly lower than 80 characters, to account for extra characters
> in unified diffs (including three-way diffs) and for email quoting.
> However, there was no consensus on this so keep the 80-character
> soft limit and add a hard limit at 90.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> CODING_STYLE | 13 ++++++++++---
> scripts/checkpatch.pl | 8 ++++++--
> 2 files changed, 16 insertions(+), 5 deletions(-)
>
> diff --git a/CODING_STYLE b/CODING_STYLE
> index 3c6978f..4e48a96 100644
> --- a/CODING_STYLE
> +++ b/CODING_STYLE
> @@ -31,14 +31,20 @@ Do not leave whitespace dangling off the ends of lines.
>
> 2. Line width
>
> -Lines are 80 characters; not longer.
> +Lines should be 80 characters; try not to make them longer.
> +
> +Sometimes it is hard to do, especially when dealing with QEMU subsystems
> +that use long function or symbol names. Even in that case, do not make
> +lines much longer than 80 characters.
>
> Rationale:
> - Some people like to tile their 24" screens with a 6x4 matrix of 80x24
> xterms and use vi in all of them. The best way to punish them is to
> let them keep doing it.
> - Code and especially patches is much more readable if limited to a sane
> line length. Eighty is traditional.
> + - The four-space indentation makes the most common excuse ("But look
> + at all that white space on the left!") moot.
> - It is the QEMU coding style.
>
> 3. Naming
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index f6928db..714a000 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -1336,12 +1336,16 @@ sub process {
> # check we are in a valid source file if not then ignore this hunk
> next if ($realfile !~ /\.(h|c|cpp|s|S|pl|py|sh)$/);
>
> -#80 column limit
> +#90 column limit
> if ($line =~ /^\+/ &&
> !($line =~ /^\+\s*"[^"]*"\s*(?:\s*|,|\)\s*;)\s*$/) &&
> $length > 80)
> {
> - WARN("line over 80 characters\n" . $herecurr);
> + if ($length > 90) {
> + ERROR("line over 90 characters\n" . $herecurr);
> + } else {
> + WARN("line over 80 characters\n" . $herecurr);
> + }
> }
>
> # check for spaces before a quoted newline
>
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2016-08-10 9:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 8:22 [Qemu-devel] [PATCH v2 0/5] checkpatch tweaks Paolo Bonzini
2016-08-10 8:22 ` [Qemu-devel] [PATCH 1/5] checkpatch: tweak the files in which TABs are checked Paolo Bonzini
2016-08-10 8:57 ` Cornelia Huck
2016-08-10 9:02 ` Paolo Bonzini
2016-08-10 9:05 ` Cornelia Huck
2016-08-10 8:22 ` [Qemu-devel] [PATCH 2/5] checkpatch: check for CVS keywords on all sources Paolo Bonzini
2016-08-10 8:22 ` [Qemu-devel] [PATCH 3/5] CODING_STYLE, checkpatch: update line length rules Paolo Bonzini
2016-08-10 9:01 ` Cornelia Huck
2016-08-10 9:48 ` Thomas Huth [this message]
2016-08-10 8:22 ` [Qemu-devel] [PATCH 4/5] checkpatch: bump most warnings to errors Paolo Bonzini
2016-08-10 9:54 ` Thomas Huth
2016-08-10 10:25 ` Paolo Bonzini
2016-08-10 10:29 ` Thomas Huth
2016-08-10 10:44 ` Paolo Bonzini
2016-08-10 10:48 ` Thomas Huth
2016-08-10 8:22 ` [Qemu-devel] [PATCH 5/5] checkpatch: default to success if only warnings Paolo Bonzini
2016-08-10 9:03 ` [Qemu-devel] [PATCH v2 0/5] checkpatch tweaks Markus Armbruster
2016-08-10 23:56 ` no-reply
2016-08-10 23:55 ` Fam Zheng
2016-08-11 0:02 ` no-reply
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=30c0f83d-e9a2-91a3-6c7e-e46a4290aa55@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=famz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).