public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Joel Schopp <jschopp@austin.ibm.com>
Cc: Stefani Seibold <stefani@seibold.net>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	apw@canonical.com, davej@redhat.com
Subject: Re: [PATCH] checkpatch.pl: remove the 80 charactes punch card limit
Date: Wed, 27 Jan 2010 11:01:12 -0800	[thread overview]
Message-ID: <4B608D78.4040606@caviumnetworks.com> (raw)
In-Reply-To: <4B6080C5.7020306@austin.ibm.com>

Joel Schopp wrote:
> 
>> The time of 80 characters punch card and terminals are over, so i would
>> be a good thing to set the line length limit to 120. Every display today
>> should be able handle this.   
> Nack.
> 
> While the origins of 80 character lines dates back to punchcards there 
> is a reason it has survived the test of time.

Has it though?  If that were the undisputed truth, we wouldn't be having 
this discussion.  Also it is likely that there would be very few devices 
capable of displaying more than 80 columns.

> Lines that go longer are hard to comprehend.

Not universally.

> Either they are long themselves, in which case 
> breaking them up into smaller chunks on multiple lines helps 
> readability,

... Or sometimes it results in gibberish.

> or they are starting from deep indentation, in which case 
> the function should be refactored or broken up so the logic is more 
> digestable. --

The problem with the checkpatch.pl tool is that its use results in 
people trying to eliminate warnings.  In the case of the 80 column 
warning, this can result in going against the goal stated in CodingStyle 
Chapter 2:  "Coding style is all about readability and maintainability..."

Perhaps checkpatch.pl needs a third level of diagnostic.  Perhaps:

NOTICE: line over 80 characters

Indicating that the line in question should be given extra attention, 
but weaker than a WARNING.

In any event, it is always fun to discuss these questions of style.


David Daney


  reply	other threads:[~2010-01-27 19:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-27 13:09 [PATCH] checkpatch.pl: remove the 80 charactes punch card limit Stefani Seibold
2010-01-27 18:07 ` Joel Schopp
2010-01-27 19:01   ` David Daney [this message]
2010-01-27 20:31     ` Joel Schopp
2010-01-27 20:42       ` David Daney
2010-01-27 21:36       ` Stefani Seibold
2010-01-28 15:54 ` Andi Kleen
2010-01-28 16:39   ` Alexander Clouter
2010-01-29  5:19     ` tytso
2010-01-29 18:49       ` Joe Perches
2010-02-01 10:53     ` Simon Farnsworth
2010-01-28 17:58   ` David Daney
2010-01-28 16:01 ` Krzysztof Halasa

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=4B608D78.4040606@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=davej@redhat.com \
    --cc=jschopp@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefani@seibold.net \
    /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