Re: checkpatch guide for newbies

From: Alexander Holler
Date: Tue Sep 24 2013 - 14:51:20 EST

Am 24.09.2013 19:43, schrieb Alexander Holler:
Am 24.09.2013 19:26, schrieb Alexander Holler:
Am 24.09.2013 18:36, schrieb Bjorn Helgaas:
On Mon, Sep 23, 2013 at 3:01 AM, Dan Carpenter
<dan.carpenter@xxxxxxxxxx> wrote:
Long Lines

Historically screens were 80 characters wide and it was annoying when
code went
over the edge. These days we have larger screens, but we keep the 80
limit because it forces us to write simpler code.

Sorry, but that just isn't true and never was. Having a line wide limit
of 80 characters while forcing tabs to be 8 characters long limits most
code to just 72 characters. And even less (max 64) inside constructs
like if, for or while.

The only outcome of that totally silly rule is that variable names will
become shorted to silly acronyms almost nobody does understand make code

I forgot to mention function names, which are often even worse shortened
than variable names.

I always feel like beeing in the IT stone age when programmers thought
they have to use variable names like a, b and c to save storage, memory
or to type less when reading linux kernel code.

Just in case of ...

It isn't my intention to start a discussion about that 80 character limit, but justifying it with wrong arguments shouldn't be done.

You could write "'It's there and you have to live with it.", but trying to justify it with obviously wrong arguments should not be done.

Code doesn't get more simple by forcing people to use akronymous, abrevations or to split lines.


Alexander Holler

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at