lkml.org 
[lkml]   [2013]   [Sep]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: checkpatch guide for newbies
From
On Tue, Sep 24, 2013 at 7:26 PM, Alexander Holler <holler@ahsoftware.de> wrote:
> Am 24.09.2013 18:36, schrieb Bjorn Helgaas:
>>
>> On Mon, Sep 23, 2013 at 3:01 AM, Dan Carpenter <dan.carpenter@oracle.com>
>> 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
>>> character
>>> 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
> unreadable.
>
> 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.
I was about to disagree because I've never seen variables named a, b
or c, but I found that there are at least 2238 variables named a, b or
c in linux-next. This is not good.

>
> Regards,
>
> Alexander Holler
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-janitors"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html



--
Peter


\
 
 \ /
  Last update: 2013-09-24 21:41    [W:0.053 / U:5.136 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site