Date: Thu, 28 Jan 1999 21:43:41 -0800 (PST) From: Julian Elischer <julian@whistle.com> To: Greg Lehey <grog@lemis.com> Cc: current@FreeBSD.ORG Subject: Re: btokup().. patch to STYLE(9) (fwd) Message-ID: <Pine.BSF.3.95.990128213330.11856X-100000@current1.whistle.com> In-Reply-To: <19990129155911.Q8473@freebie.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 29 Jan 1999, Greg Lehey wrote: > On Friday, 29 January 1999 at 16:26:53 +1100, John Birrell wrote: > > I'm sure they might. But they'd be wrong. I do believe that > maintaining a coherent style is a Good Thing. I just dislike the > particular style, but since it doesn't significantly lower my standard > of living, I put up with it :-) I know that there are times when I've been working on code, and that I've added parens to help me (who now understands the code) feel comfortable that I will understand it next time I'm visiting it, and when I've committed it someone rips out the parens with the comment.. "make it KNF". 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. KNF is propogating what I consider to be bad practice, and that annoys me. I'm happy to say that often they should be dropped, but to FORCE the dropping of braces etc. with no regard to readbility is too much. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.990128213330.11856X-100000>