From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,577df5d4a0e88785 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2000-12-13 14:25:11 PST Path: supernews.google.com!sn-xit-02!supernews.com!216.227.56.88.MISMATCH!telocity-west!TELOCITY!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!oleane.net!oleane!jussieu.fr!enst!enst.fr!not-for-mail From: "Beard, Frank" Newsgroups: comp.lang.ada Subject: RE: Bad coding standards Date: Wed, 13 Dec 2000 17:23:12 -0500 Organization: ENST, France Sender: comp.lang.ada-admin@ada.eu.org Message-ID: Reply-To: comp.lang.ada@ada.eu.org NNTP-Posting-Host: marvin.enst.fr Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Trace: avanie.enst.fr 976746309 18784 137.194.161.2 (13 Dec 2000 22:25:09 GMT) X-Complaints-To: usenet@enst.fr NNTP-Posting-Date: Wed, 13 Dec 2000 22:25:09 +0000 (UTC) To: "'comp.lang.ada@ada.eu.org'" Return-Path: X-Mailer: Internet Mail Service (5.5.2448.0) Errors-To: comp.lang.ada-admin@ada.eu.org X-BeenThere: comp.lang.ada@ada.eu.org X-Mailman-Version: 2.0beta5 Precedence: bulk List-Id: comp.lang.ada mail<->news gateway Errors-To: comp.lang.ada-admin@ada.eu.org X-BeenThere: comp.lang.ada@ada.eu.org Xref: supernews.google.com comp.lang.ada:3098 Date: 2000-12-13T17:23:12-05:00 (was Re: constant string array) Ken Garlington wrote: > I say, why stop at one set? I think a nice rule would be to encode tests in > double parentheses, similar to label constructs, i.e. > > if ((a * b + c)) then > ... > end if; > > so that, if you're doing structural test coverage analysis, you can find the > essential elements easily. Wouldn't that just be a lovely standard? Well, I suppose they had to stop somewhere, as all standards do. Assuming you're being facetious, I assume no-one is under the delusion that everyone out there in the Ada world, or even everyone on CLA, uses the same style guide, or even likes everything about the coding standards they're using. After all, style guides are subjective. It's not science. If it were, there would probably be only one style guide (maybe two). But instead it is subject to preference. Using upper case or lower case has no bearing on how the code runs. Unless your talking about style guide issues that specify using "for loops" as opposed to a "slices", or using "case" statements instead of an "if" statements, then it has no impact on the operation or performance of the software, just aesthetics. Is there supposed to be an "official" style guide all Ada developers are to be using (the implied LRM standard, Ada Quality and Style, ...)? All I was saying in the very beginning was I wasn't willing to fight over the paren issue in conditional statements, but when they said you couldn't use "use" and you also couldn't use "renames", we went to war. There was no way I was going to use full path names on the operators. Fortunately, no-one seems to object to "use type". Fortunately, none of coding standards I've used have been as bad as the one's Marc described. Frank