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=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no 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-14 21:55:52 PST Path: supernews.google.com!sn-xit-02!supernews.com!216.227.56.88.MISMATCH!telocity-west!TELOCITY!HSNX.atgi.net!cyclone-sjo1.usenetserver.com!news-out.usenetserver.com!cyclone-west.rr.com!news.rr.com!news-west.rr.com!lsnws01.we.mediaone.net!cyclone-LA3.rr.com!typhoon.we.rr.com.POSTED!not-for-mail Reply-To: "Keith " From: "Keith " Newsgroups: comp.lang.ada References: Subject: Re: Bad coding standards Organization: Home X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Message-ID: Date: Fri, 15 Dec 2000 05:55:46 GMT NNTP-Posting-Host: 24.24.164.220 X-Complaints-To: abuse@mediaone.net X-Trace: typhoon.we.rr.com 976859746 24.24.164.220 (Thu, 14 Dec 2000 21:55:46 PST) NNTP-Posting-Date: Thu, 14 Dec 2000 21:55:46 PST Xref: supernews.google.com comp.lang.ada:3162 Date: 2000-12-15T05:55:46+00:00 List-Id: Are there any software QA orgs out there that try to enforce the non aesthetics rules of the Quality and Style guide? "Beard, Frank" wrote in message news:B6A1A9B09E52D31183ED00A0C9E0888C469949@nctswashxchg.nctswash.navy.mil.. . > (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 >