Alistair John Strachan <[email protected]> writes:
> I personally buy the argument that 80 cols helps remind people that they've
> used too many indentation depths and should redesign their code.
> I think it's
> a good thing to stick to where possible, even if just from a design
> perspective.
How many is too many? A function with 2 "if" means 3 tabs = 24 characters
for just indentation. Add a printk(KERN_DEBUG "\n"); and you can print
ca. 30 characters without having to break the string. This is crazy.
> There are some cases such as the one Alan has pointed out here where being
> strictly 80 cols seems more destructive than useful, but those are the
> exception, not the rule (IMO).
Well... I was forced to split functions making the code less readable
and more complicated just to avoid these 80-columns. A short function
with more indent levels may be way more readable than a redesigned one
with this requirement in mind.
I'd just state the code has to be readable and laid out with some sanity
but 80 columns give us nothing WRT this.
We already review new code and spot such problems (and smaller ones)
without using the 80-cols rule.
--
Krzysztof Halasa
-
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/
[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]
