From owner-freebsd-current Thu Jan 28 08:32:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08068 for freebsd-current-outgoing; Thu, 28 Jan 1999 08:32:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08059 for ; Thu, 28 Jan 1999 08:32:43 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA17377; Thu, 28 Jan 1999 11:32:35 -0500 (EST) (envelope-from wollman) Date: Thu, 28 Jan 1999 11:32:35 -0500 (EST) From: Garrett Wollman Message-Id: <199901281632.LAA17377@khavrinen.lcs.mit.edu> To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: btokup() macro in sys/malloc.h In-Reply-To: <36B04265.842788DA@newsguy.com> References: <99Jan28.131753est.40347@border.alcanet.com.au> <36B04265.842788DA@newsguy.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Peter Jeremy wrote: >> >> I'll support that. The example given in style(9): >> >> a = b->c[0] + ~d == (e || f) || g && h ? i : j >> 1; >> >> should rate as an entry in the Obfuscated C competition rather than >> an example of maintainable code. > As a matter of fact, what's the reasoning behind this particular > style(9) recommendation? I believe that it was an attempt on Berkeley's part to ``raise the bar'' for kernel coders -- `if you don't know the C operator precedence table by heart, you shouldn't be writing kernel code'. Obviously, it didn't work, or we wouldn't be here today. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message