80 column line limit?

Can't we relax the 80 column line rule to something more comfortable?
These days descriptive variable/function names are much more valuable,
I think.

Just by looking at random examples in the tree, seems the 80 column
rule does more harm than good. I always find myself start shortening
names just to fit the line limit and not to need to line-wrap a statement.
We even use #defines sometimes to access simple structure members and
the like, only to fit that rule.

So, are we sure that 80 columns is still valuable, looking at the
side-effects of artificially shortended variable/function names and
line-wrapped statements, caused by this rule?

Thanks,
Kay
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: 80 column line limit?
    • From: Jim Nance <[email protected]>
  • Re: 80 column line limit?
    • From: Alistair John Strachan <[email protected]>
  • Re: 80 column line limit?
    • From: Giuliano Pochini <[email protected]>
  • Re: 80 column line limit?
    • From: Pekka Enberg <[email protected]>
  • Re: 80 column line limit?
    • From: Jesper Juhl <[email protected]>

• Prev by Date: Re: [PATCH 3/3] v9fs: zero copy implementation
• Next by Date: [PATCH] drivers/media: Conversions from kmalloc+memset to k(z|c)alloc.
• Previous by thread: socketpair - too many open files
• Next by thread: Re: 80 column line limit?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]