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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,53cc1587f9eb1d02
X-Google-Attributes: gid103376,public
From: "Geg Bek" <gab@rational.com>
Subject: Re: Diana specification for Ada
Date: 2000/08/25
Message-ID: <sqep5td6t9141@corp.supernews.com>#1/1
X-Deja-AN: 662640429
References: <39A54478.68D5EA7C@excite.com>
Organization: Posted via Supernews, http://www.supernews.com
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Newsgroups: comp.lang.ada
X-Complaints-To: newsabuse@supernews.com
Date: 2000-08-25T00:00:00+00:00
List-Id: <comp.lang.ada>

This information is from:
DIANA
An Intermediate Language for Ada
William A. Wulf, Arthur Evans, Jr., Kenneth J. Butler
Tartan Labs.
ISBM 3-540-12695-3
Published by Springer-Verlag

This is dated 1988, so wouldn't have any Ada95 in it at all.

I think Rational is the only vendor that ever really used DIANA.
But the way it is physically represented is very implementation
dependent.  For instance, for Rational Apex we make sure
we represent DIANA in a way that permits incremental updates.

As Tucker said, the best way to read DIANA is through ASIS.
Updating/writing DIANA is best left to the compiler.

GReg

Dragonboy wrote in message <39A54478.68D5EA7C@excite.com>...
>Does anyone know where I can object a functional/design specification
>for the Diana intermediate representation that is used by Ada
>compilers?  I know that it's some form of abstract syntax tree, but
>that's about it.
>
>Thanks.
>
>-DB
>