Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!vsi1!daver!tscs!tct!chip From: chip@tct.uucp (Chip Salzenberg) Newsgroups: comp.lang.c Subject: Re: Coding Standards. Message-ID: <2753F21B.2F6@tct.uucp> Date: 28 Nov 90 17:21:30 GMT References: <1990Nov10.191840.21113@clear.com> <2055.27469abd@iccgcc.decnet.ab.com> <1990Nov21.182209.23578@clear.com> Organization: Teltronics/TCT, Sarasota, FL Lines: 18 According to rmartin@clear.com (Bob Martin): >At Clear we have instituted a style standard which [...] >demands that comments always be placed on closing braces. >[...] >The convention is "demanded" because it is cheap, easy, has very >few down-sides, and the _possibility_ of significant up-sides. I'd say that the down side of this rule includes two problems which are (to me) very significant: such comments clutter the code and they make commentary a very low-level syntactical entity. In my opinion, mandatory comments on *syntactic* grounds are likely to lead to worse-than-nothing garbage like "++x; /* add one to x */" as programmers fill in just anything to comply with the standard. -- Chip Salzenberg at Teltronics/TCT , "I've been cranky ever since my comp.unix.wizards was removed by that evil Chip Salzenberg." -- John F. Haugh II