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 12:42:53 -0800 [thread overview]
Message-ID: <4B60A54D.5060006@caviumnetworks.com> (raw)
In-Reply-To: <4B60A288.2010909@austin.ibm.com>
Joel Schopp wrote:
>
>>>
>>>
>>> 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.
>
> If you know of a usability study that quantifies the effect of line
> length on readibility of C code I'm willing to listen, and I'm sure
> others are too.
Good point. As with most things related to kernel development, a
usability study or other market research from a reputable institution is
a vital first step before taking any action.
We don't have any good peer reviewed research on the subject that I am
aware of. I guess even contemplating a change at this early point would
be rash and dangerous.
I withdraw my previous comments with respect to the 80 Column Question.
Instead I would recommend elevating the WARNING to ERROR status.
David Daney
next prev parent reply other threads:[~2010-01-27 20:46 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
2010-01-27 20:31 ` Joel Schopp
2010-01-27 20:42 ` David Daney [this message]
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=4B60A54D.5060006@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