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.1 required=5.0 tests=BAYES_05,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,2de3952aea423411 X-Google-Attributes: gid103376,public From: John McCabe Subject: Re: coding standard for ada95 Date: 1998/06/10 Message-ID: <6lloho$nc7@gcsin3.geccs.gecm.com>#1/1 X-Deja-AN: 361326380 Content-Transfer-Encoding: 7bit References: Content-Type: text/plain; charset=us-ascii Organization: GMS&T Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1998-06-10T00:00:00+00:00 List-Id: The Quality and Style guide would be a good place to start. I am not a fan of coding standards but then again in my experience they have been produced by QA guys who don't know much about the language and start putting restrictions on the use of certain features (e.g. tasking, generics) because at some point they heard they were not very efficient and so on. I would recommend that if you are going to produce a coding standard that you try to place as few restrictions as possible on language feature usage, and only then when you can justify the restrictions based on knowledge of the operating system and compiler you are using. Also you may wish to define a format for the layout of the code. For specific projects I would recommend that you define a standard text editor which can be configured for use with the language in question. Emacs would be a prime example using ada-mode with a standard set of customisation options. Hope this helps ;-) -- Best Regards John McCabe ===================================================================== Not necessarily my company or service providers opinions. =====================================================================