public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Tomlinson <edt@aei.ca>
To: linux kernel <linux-kernel@vger.kernel.org>
Cc: Andries Brouwer <aebr@win.tue.nl>
Subject: Re: PATCH, RFC: 2.6 Documentation/Codingstyle
Date: Fri, 13 Feb 2004 07:42:08 -0500	[thread overview]
Message-ID: <200402130742.08853.edt@aei.ca> (raw)
In-Reply-To: <20040213124232.B2871@pclin040.win.tue.nl>

On February 13, 2004 06:42 am, Andries Brouwer wrote:
> On Fri, Feb 13, 2004 at 09:58:02AM +0100, Giuliano Pochini wrote:
> >> +The limit on the length of lines is 80 columns and this is a hard
> >> limit.
> >
> > Well, I think this requirement is a bit silly IMHO. How many of us
> > do usually code in a 80x25 terminal screen nowadays ?
>
> I do. (That is, 80xN with N in 24..60 or so.)
>
> The 80 here has a pedagogical and a practical purpose.
> The practical one is that it makes sure that everybody can read the source.
> The pedagogical is to invite you to arrange the code in a different way
> if you are nesting too deeply or your expressions are too complicated.
>
> There is also ergonomics. There is a reason newspapers do not print
> text across the full width of the page - it would be very difficult
> to read. There is an optimal column width. One might fight over the
> exact value of the optimum, but 80 columns is not a bad choice.

This would be true if not for indenting.  A program is not a newspaper.
I doubt the lenght of text, excluding the indent is longer than 80 chars
very often....   With 80 columns and indenting code looks ugly.

Ed Tomlinson

  parent reply	other threads:[~2004-02-13 12:42 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-12 22:15 PATCH, RFC: 2.6 Documentation/Codingstyle Michael Frank
2004-02-12 23:20 ` Tim Bird
2004-02-12 23:46   ` Måns Rullgård
2004-02-13  0:19   ` Tim Hockin
2004-02-12 23:38 ` Randy.Dunlap
2004-02-13  1:50   ` Alex Goddard
2004-02-13  1:52   ` Maciej Zenczykowski
2004-02-13  0:13 ` viro
2004-02-13  1:12 ` J. Bruce Fields
2004-02-13  8:49 ` PATCH, RFC: Version 2 of 2.6 Codingstyle Michael Frank
2004-02-13  9:44   ` Andries Brouwer
2004-02-13 11:24     ` Nikita Danilov
2004-02-16 17:56     ` Ludootje
2004-02-13 22:38   ` Randy.Dunlap
2004-02-13  8:58 ` PATCH, RFC: 2.6 Documentation/Codingstyle Giuliano Pochini
2004-02-13  9:10   ` Andrew Morton
2004-02-13  9:49     ` Michael Frank
2004-02-13 10:09       ` Nick Piggin
2004-02-13 10:50         ` Michael Frank
2004-02-18  7:39           ` Miles Bader
2004-02-13 12:44     ` viro
2004-02-13  9:19   ` David Weinehall
2004-02-13 11:42   ` Andries Brouwer
2004-02-13 12:13     ` Måns Rullgård
2004-02-13 12:42     ` Ed Tomlinson [this message]
2004-02-13 13:55     ` Giuliano Pochini
2004-02-13 14:35       ` Angelo Dell'Aera
2004-02-13 15:42         ` Giuliano Pochini
2004-02-13 15:48         ` Valdis.Kletnieks
2004-02-13 16:38           ` Angelo Dell'Aera
2004-02-13 17:03             ` Valdis.Kletnieks
2004-02-13 16:18       ` viro
2004-02-14  0:38 ` Kevin O'Connor
2004-02-14  0:56   ` Valdis.Kletnieks
2004-02-14  1:44 ` PATCH, RFC: Version 3 of 2.6 Codingstyle Michael Frank
2004-02-14  3:44   ` Dmitry Torokhov
2004-02-15 10:09     ` Jamie Lokier
2004-02-14 20:44 ` PATCH, RFC: Version 4 " Michael Frank
2004-02-14 21:27   ` viro
2004-02-16  3:47 ` PATCH, RFC: Version 5 " Michael Frank
     [not found] <fa.fbh88ra.kn8094@ifi.uio.no>
2004-02-13  6:41 ` PATCH, RFC: 2.6 Documentation/Codingstyle Junio C Hamano
2004-02-13  7:18   ` vda
2004-02-13 12:37     ` Maciej Zenczykowski
2004-02-13 13:57       ` vda

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=200402130742.08853.edt@aei.ca \
    --to=edt@aei.ca \
    --cc=aebr@win.tue.nl \
    --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