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.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!eglin-vax.arpa!harbaughs
From: harbaughs@EGLIN-VAX.ARPA
Newsgroups: net.lang.ada
Subject: your suggestion to used parsed form as tools input
Message-ID: <8509270901.AA05872@UCB-VAX.ARPA>
Date: Fri, 27-Sep-85 00:36:42 EDT
Article-I.D.: UCB-VAX.8509270901.AA05872
Posted: Fri Sep 27 00:36:42 1985
Date-Received: Sat, 28-Sep-85 07:38:11 EDT
Sender: daemon@ucbvax.ARPA
Organization: The ARPA Internet
List-Id: <comp.lang.ada>

I frankly don't know if the DEC Ada compiler makes available
parsed form but i've seen nothing in any documentation saying
that it does. Even so I suspect that it would not be a
gaurenteed interface thus any tools that use it as input
may not work with future revisions of the compiler.
     It certainly is good that Intermetrics makes that available.
It will save many trillions of cpu ops to have tools work from
the parsed form. 
     I am not up to date on Diana. Is it standardized
yet? ANSI? ISO? Is there a validation suite? A language
control facility? I am very reluctant to do any work
on an interface that isn't frozen, validated, and maintained
by the vendor. Also I am reluctant to get locked into
sole-source thus I would rather burn the cpu ops than
limit my choice of validated Ada compilers. Looking
forward to a standard compiler front-end output
interface.
regards, sam harbaugh
---------------------