From owner-freebsd-chat Thu Feb 29 10:47:30 1996 Return-Path: owner-chat Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA29228 for chat-outgoing; Thu, 29 Feb 1996 10:47:30 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA29223 for ; Thu, 29 Feb 1996 10:47:29 -0800 (PST) Received: from seagull.rtd.com (root@seagull.rtd.com [198.102.68.2]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id KAA01752 for ; Fri, 1 Mar 1996 10:47:25 -0800 Received: (from tony@localhost) by seagull.rtd.com (8.6.12/1.2) id LAA08510 for chat@freebsd.org; Thu, 29 Feb 1996 11:46:02 -0700 Date: Thu, 29 Feb 1996 11:46:02 -0700 From: Tony Jones Message-Id: <199602291846.LAA08510@seagull.rtd.com> To: chat@freebsd.org Subject: Re: your mail Newsgroups: rtd.freebsd.chat Organization: RTD Internet Access X-Newsreader: TIN [version 1.2 PL2] Sender: owner-chat@freebsd.org Precedence: bulk In article <9602290840.AA26034@nob> you wrote: : > This is from /usr/src/linux/Documentation/CodingStyle, it's Linus' own : > personal coding style. Am I the only one here who finds this, ultimate : > : > -- CUT HERE ----------------------------------------------------------------- : > : > Linux kernel coding style : > : > First off, I'd suggest printing out a copy of the GNU coding standards, : > and NOT read it. Burn them, it's a great symbolic gesture. : > : Then I'd suggest to all -- print out a copy of the : _Linux_kernel_coding_style_, and NOT readit. Burn them, it's a great : symbolic gesture. Well ... 1) it's only advisory (or at least purports to be :-) 2) as C coding standards go, it's about the tamest/least offensive I've seen. Having worked on several team development projects where C coding standards have come up, or seen others groups debating them, I've grown used to seeing whole chunks of the language declared 'out of bounds'. IMHO code not conforming to the K&R standards for brace ({}) placement should be rejected by the compiler :-) tony