comp.lang.ada
 help / color / mirror / Atom feed
From: netwrk!peg@uunet.uu.net  (Phillip Gardner)
Subject: Re: Ada Coding Rules
Date: 23 Feb 93 18:57:48 GMT	[thread overview]
Message-ID: <123@netwrk.UUCP> (raw)

This article is being posted by someone other than the author.  Please direct
followup email to jak@pseserv2.magec.com (or uunet!netwrk!pseserv2!jak).


In article <1993Feb19.024311.210@leeweyr.sccsi.com>, bill@leeweyr.sccsi.com (Bi
ll Lee) writes:
> I suggest you get a copy of the latest "Ada Quality and Style: Guidelines 
> for ProfessionalProgrammers"  SPC-91061-CMC VERSION 02.01.01

I read your request for information about Ada Coding Standards documentation an
d
tools posted to comp.lang.ada.

I absolutely agree (with Bill from Lee Aerie) that the "Ada Quality and Style:
Guideline for Professional Programmers" from the Software Productivity
Consortium is a good start.

At Magnavox, we use AdaMAT from:

        Dynamics Research Corporation (DRC)
        60 Frontage Road
        Andover, MA 01810
        (800) 522-7321, (508) 475-9090

AdaMAT is an automated, Ada-specific static source code analyzer which
automatically checks for various coding standards and guidelines.  It follows
almost all of the suggestions in the Ada Quality and Style Guideline.

We use AdaMAT on the RATIONAL system.  The RATIONAL system is a well known Ada
development system.  One of its features is that the Editor automatically
controls the format of the Ada code (indentation, upper case/lower case, etc.)
and some language features (eg. prevents using "use" and "anonymous array
types").

I'm sure AdaMAT runs on other platforms such as VAX/VMS, Sun/UNIX, HP/UNIX, etc
.

I've used VAX/VMS before, and it has VAXset (or DECset) with a Language
Sensitive Editor (LSE) which will also aid in controlling the format of the Ada
code.

Some of the things that we have learned about Ada at Magnavox:

For DOD-STD-2167 or 2167A, CSUs = Ada Packages.
Never use "use".
Avoid global variables (variables declared in package specifications).
Use "named loops, exits, and declare blocks".
Use "named parameters" when calling subprograms.
Avoid "anonymous array types".
Add comments to "begin", "else", "end if", "end case", etc.
Many others that you'll learn with additional Ada experience...
--
-------------------------------------------------------------------------------
-
James A. Krzyzanowski - Software Engineer
Magnavox Electronic Systems Company * Fort Wayne, IN 46808 * (219) 429-6446
E-Mail : uunet!netwrk!pseserv2!jak (UUCP) * jak@pseserv2.magec.com (Internet)
-------------------------------------------------------------------------------
-

             reply	other threads:[~1993-02-23 18:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-02-23 18:57 Phillip Gardner [this message]
  -- strict thread matches above, loose matches on Subject: below --
1993-02-26 15:41 Ada Coding Rules cis.ohio-state.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!caen!uvaarpa!soft
1993-02-22 22:17 ADA CODING RULES Scott McCoy
1993-02-22 18:47 cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!uwm.edu!cs.utexas.edu
1993-02-21 22:54 Ada Coding Rules Jon Spear
1993-02-21  1:45 Mich ael Feldman
1993-02-19  5:22 Alex Blakemore
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox