From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Date: 1 Jul 93 21:11:40 GMT
From: cis.ohio-state.edu!math.ohio-state.edu!sdd.hp.com!saimiri.primate.wisc.ed
u!news.crd.ge.com!e7sa!groleau@ucbvax.Berkeley.EDU  (Wes Groleau X7574)
Subject: Re: lint tool for Ada?
Message-ID: <C9I87H.M2q@crdnns.crd.ge.com>
List-Id: <comp.lang.ada>

In article <19930701.105001.319@almaden.ibm.com> jnestoriak@vnet.IBM.COM writes
:
>>How about it compiler vendors? The only third-party tool that responded neede
d POSIX
>>and ASIS compliance. Either the compilers need to go this route so that third
-party
>>software can make Ada programmers lives less miserable, or provide toolsets t
hat
>>actually provided the functionality we need.
>
>There was a panel discussion on tools like this at WADAS yesterday.  I
>gather that for any meaningful analysis of the code ASIS is needed (or
>it will have to be compiler specific) because you need to get at the
>sublib .........

Or the tool (as the only two I've ever seen do) can parse the Ada source code 
itself.  Basically a compiler front-end with a report writer in place of a code
 generator.