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.2 required=5.0 tests=BAYES_00,INVALID_MSGID,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,15890893c0618a8a
X-Google-Attributes: gid103376,public
From: crispen@hiwaay.net (Bob Crispen)
Subject: Re: [Q] Tools for Ada Quality and Style
Date: 1996/04/27
Message-ID: <4ltjat$dao@parlor.hiwaay.net>#1/1
X-Deja-AN: 151771136
references: <9604172134.AA27114@eight-ball> <767968529wnr@diphi.demon.co.uk>
organization: http://hiwaay.net/~crispen/
reply-to: crispen@hiwaay.net
newsgroups: comp.lang.ada
Date: 1996-04-27T00:00:00+00:00
List-Id: <comp.lang.ada>


JP Thornley <jpt@diphi.demon.co.uk> wrote:

>We are currently looking at redoing our standards and are likely to base 
>them closely on these. [Ada Quality & Style]

>What would also be very useful is a pretty-printer (or a conformance 
>checker) that can implement the standards we end up with.  I have found 
>one tool on the Walnut Creek CD-ROM - I don't have this available at 
>present but I think it is called NAPPI (IIRC its from NASA and dates 
>from around 1988).

>Does anyone have any experience of using this (is it a good base for a 
>tailored pretty-printer)?  Alternatively does anyone know of any other 
>similar tools.  (Note that we will be using Ada 83 for some time yet as 
>well as Ada 95).

Try http://hiwaay.net/~crispen/us/our_computer.html

There's a version in C that does Ada 83 prettifying and a version in
Ada 95 that does Ada 95 prettifying.  They're both in source code
form, and I haven't uploaded them to the PAL because they're really
not high enough quality or elaborate enough (IMHO).  But I use them
all the time and have them mapped to function keys in vi.

Note that all these little tools handle is capitalization and some
spacing within a line.

There's another little tool there that aligns colons in a "paragraph"
that I also use a bunch.

I use something similar at work, but these were developed on my own
time.

Bob Crispen
crispen@hiwaay.net
Speaking for myself, not my company