public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Frank <mhf@linuxmail.org>
To: Andrew Morton <akpm@osdl.org>, Giuliano Pochini <pochini@shiny.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH, RFC: 2.6 Documentation/Codingstyle
Date: Fri, 13 Feb 2004 17:49:19 +0800	[thread overview]
Message-ID: <200402131749.19758.mhf@linuxmail.org> (raw)
In-Reply-To: <20040213011012.12645046.akpm@osdl.org>

On Friday 13 February 2004 17:10, Andrew Morton wrote:
> Giuliano Pochini <pochini@shiny.it> wrote:
> >
> > 
> > On 12-Feb-2004 Michael Frank wrote:
> > > Here is Codingstyle updated.
> > 
> > > +The limit on the length of lines is 80 columns and this is a hard limit.

Sorry, I "shortened" that line away and will add it again.

> > 
> > Well, I think this requirement is a bit silly IMHO. How many of us
> > do usually code in a 80x25 terminal screen nowadays ?

I still use 80 wide but with many more lines. I tend to be sloppy about 
code extending beyond 80, which I shall change ;)

Also bear in mind that the fundamental arguments for 80 columns are not 
related to (display) hardware capabilities, but related to clarity of code.

> > 
> 
> "I think the 90x25 requirement is silly"
> 
> "I think the 100x25 requirement is silly"
> 

> And so it goes.  You get into an xterm arms race wherein everyone has to
> make their terminal as wide as the widest guy so anyone can get any work
> done.
> 
> Yes, 80 cols sucks and the world would be a better place had CodingStyle
> mandated 96 columns five years ago.  But it didn't happen.
> 

As to "five years ago", what about review the coding style situation before 
starting 2.7:

In view of better hardware, increasing linelength a little to 96 could be 
considered without increasing the number of indentation levels.

Perhaps consider deprecating function-like macros as inline technology
is much improved.

...


  reply	other threads:[~2004-02-13  9:39 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 [this message]
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
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=200402131749.19758.mhf@linuxmail.org \
    --to=mhf@linuxmail.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pochini@shiny.it \
    /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