From: Stefani Seibold <stefani@seibold.net>
To: Joel Schopp <jschopp@austin.ibm.com>
Cc: David Daney <ddaney@caviumnetworks.com>,
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 22:36:24 +0100 [thread overview]
Message-ID: <1264628184.11228.7.camel@wall-e> (raw)
In-Reply-To: <4B60A288.2010909@austin.ibm.com>
Am Mittwoch, den 27.01.2010, 14:31 -0600 schrieb Joel Schopp:
> >>
> >>
> >> 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.
Show me the usability study with claims that 80 columns is the wisdom in
software engineering. Why not 73, 90 or 95? The only reason for the 80
columns is a historic one.
And the programming rules for linux doesn't manifest the 80 character
per line.
Code will get in many cases harder to read, especially together with the
tab size of 8. Multiline C statements makes the code IMHO harder to
read.
Stefani
next prev parent reply other threads:[~2010-01-27 21:36 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
2010-01-27 21:36 ` Stefani Seibold [this message]
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=1264628184.11228.7.camel@wall-e \
--to=stefani@seibold.net \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=davej@redhat.com \
--cc=ddaney@caviumnetworks.com \
--cc=jschopp@austin.ibm.com \
--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