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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,ec4cde5d799065b6 X-Google-Attributes: gid103376,public From: mab@dst1.wdl.loral.com (Mark A Biggar) Subject: Re: Coding Standards & GOTO Date: 1997/09/23 Message-ID: <6092vo$aai@wdl1.wdl.lmco.com>#1/1 X-Deja-AN: 275056093 References: <3426B51E.7296@lmco.com> Organization: Loral Western Development Labs Newsgroups: comp.lang.ada Date: 1997-09-23T00:00:00+00:00 List-Id: In article mheaney@ni.net (Matthew Heaney) writes: >In article <3426B51E.7296@lmco.com>, William.Dale.Jr@lmco.com wrote: >>As my charter for implementing a new Ada 95 standard is to have only >>absolute rules that cannot be violated, >You are setting yourself up for failure, as there is no such thing as an >absolute rule. >>I am forced to through out most >>of AQ&S as mearly advice. >Why the pejorative "merely advice"? That's exactly what a coding standard >should be, advice on how to use language. >>A major segment wants to use GOTO's ( visible >>objects in specs too ). I'd use the AQ&S right out of the box if I >>could. >A "rule" comprises "guidelines," plus a list of the times when the >guidelines don't apply, ie >rule = guidelines + exceptions >For example, state your rule for the use of goto as follows: It is also usefull to have a meta-exception at the start of your Style Guide that says something like: Almost any of the guidelines in this stype guide can be violated in specific cases, if you can get your inspection/walkthrough team to buy off on it. You do have inspections don't you? Also, the best way to enforce any code formatting style guidelines is to provide a standard pretty-printer that must be run before the inspection. -- Mark Biggar mab@wdl.lmco.com