Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754541Ab3IXR0p (ORCPT ); Tue, 24 Sep 2013 13:26:45 -0400 Received: from h1446028.stratoserver.net ([85.214.92.142]:40968 "EHLO mail.ahsoftware.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754494Ab3IXR0n (ORCPT ); Tue, 24 Sep 2013 13:26:43 -0400 Message-ID: <5241CB44.8080004@ahsoftware.de> Date: Tue, 24 Sep 2013 19:26:28 +0200 From: Alexander Holler User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130805 Thunderbird/17.0.8 MIME-Version: 1.0 To: Bjorn Helgaas CC: Dan Carpenter , kernel-janitors@vger.kernel.org, "linux-kernel@vger.kernel.org" Subject: Re: checkpatch guide for newbies References: <20130923090100.GE6192@mwanda> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1248 Lines: 30 Am 24.09.2013 18:36, schrieb Bjorn Helgaas: > On Mon, Sep 23, 2013 at 3:01 AM, Dan Carpenter 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. Regards, Alexander Holler -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/