From owner-freebsd-current Tue Feb 2 11:43:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22812 for freebsd-current-outgoing; Tue, 2 Feb 1999 11:43:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from csla.csl.sri.com (csla.csl.sri.com [192.12.33.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22802 for ; Tue, 2 Feb 1999 11:43:51 -0800 (PST) (envelope-from gilham@csl.sri.com) Received: from csl.sri.com (snapdragon.csl.sri.com [130.107.18.20]) by csla.csl.sri.com (8.9.1/8.9.1) with ESMTP id LAA10324 for ; Tue, 2 Feb 1999 11:43:47 -0800 (PST) Message-Id: <199902021943.LAA10324@csla.csl.sri.com> To: current@FreeBSD.ORG Subject: Re: btokup().. patch to STYLE(9) (fwd) In-reply-to: Your message of "Thu, 28 Jan 1999 21:43:41 PST." Date: Tue, 02 Feb 1999 11:43:47 -0800 From: Fred Gilham Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > > Now if I'm working on some piece of code and feel that it could do with > some parens then surely KNF should be flexible enough to allow them.. > > I don't know how many bugs have ben revealed by adding parens and braces.. > I know that one of the first things I do when looking for a bug is add as > many as I can in parts of the code that are suspect. > > It's amazing how often it shows up the problem. > As someone who has made one (1) contribution to the FreeBSD kernel, I say, go ahead and use parentheses to your heart's content. My one contribution was a patch to the kernel and Linux emulator to allow the Linux version of Allegro Common Lisp 4.3 to run under FreeBSD. :-) :-) -Fred Gilham gilham@csl.sri.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message