linux-kernel - Re: CodingStyle: start flamewar about use of braces

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <84144f020705090159t72ea1bd8qccc60791f3be8db@mail.gmail.com>
Date:	Wed, 9 May 2007 11:59:33 +0300
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Stefan Richter" <stefanr@...6.in-berlin.de>
Cc:	"Satyam Sharma" <satyam.sharma@...il.com>,
	"Jeff Garzik" <jeff@...zik.org>,
	"Randy Dunlap" <randy.dunlap@...cle.com>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: CodingStyle: start flamewar about use of braces

On 5/9/07, Stefan Richter <stefanr@...6.in-berlin.de> wrote:
> I don't know which form is better suited to the goal of well
> maintainable code --- the compact, easy to read, winning guideline, or
> the comprehensive norm.

Bah, it's a slippery slope. Too little guidelines and we end up people
submitting code that is "obviously" violating Linux coding standards
on the basis of that it's not forbidden by Documentation/CodingStyle.
And with too much detail, we end up with something that nobody wants
to read let alone follow. So what CodingStyle should say, really, is
that maintainers have different preference and you're usually better
off following them than fighting against them ;-).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/