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.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,473e6b129c2f30cd
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news3.google.com!news4.google.com!newsfeed2.dallas1.level3.net!news.level3.com!newsfeed-00.mathworks.com!news.tele.dk!feed118.news.tele.dk!news.tele.dk!small.news.tele.dk!newsfeed.cw.net!cw.net!news-FFM2.ecrc.de!news.netplace.de!newsfeed.stueberl.de!peer-uk.news.demon.net!kibo.news.demon.net!mutlu.news.demon.net!news.demon.co.uk!demon!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: ANNOUNCE: Avatox 1.0 is now available
Date: Thu, 07 Sep 2006 21:46:13 +0100
Organization: Pushface
Message-ID: <m2u03jquay.fsf@grendel.local>
References: <JaPEg.6886$Qf.5686@newsread2.news.pas.earthlink.net>
 <m2odudyfdm.fsf@grendel.local>
 <OA6Hg.840$bM.366@newsread4.news.pas.earthlink.net>
 <m264giacw2.fsf@grendel.local>
 <XfSdncT-efwBxGLZnZ2dnUVZ_tqdnZ2d@megapath.net>
NNTP-Posting-Host: pogner.demon.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: news.demon.co.uk 1157661989 12058 62.49.19.209 (7 Sep 2006 20:46:29
 GMT)
X-Complaints-To: abuse@demon.net
NNTP-Posting-Date: Thu, 7 Sep 2006 20:46:29 +0000 (UTC)
Cancel-Lock: sha1:qx7Xso9srOCZJrcD/XUTWecVuxo=
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (darwin)
Xref: g2news2.google.com comp.lang.ada:6508
Date: 2006-09-07T21:46:13+01:00
List-Id: <comp.lang.ada>

"Randy Brukardt" <randy@rrsoftware.com> writes:

> It is reported that determining whether a type is limited takes 96
> lines of Ada (ASIS) code - but this is a property that every Ada
> compiler has a subprogram to calculate. It should be directly
> available in ASIS.

Via Traits, yes? (which struck me as more than a bit of a kludge when
I grasped it). It takes me about 60 lines to process all the
possible/appropriate traits (assuming that the ASIS tree is
well-formed, so that if a declaration has an
Asis.An_Abstract_Limited_Private_Trait it's appropriate to mark it
abstract, limited and private).

I see that this isn't always quite obvious: I have

    type Request is limited private;

giving

    <private_type_declaration limited="true" private="true">
      <defining_identifier>Request</defining_identifier>
      <private_type_definition limited="true" private="true">
      </private_type_definition>
    </private_type_declaration>

which seems odd (I guess that the definition is of the anonymous type
of which the declaration is the first named subtype?)

> Moreover, virtually everything in ASIS is currently optional, which
> makes writing ASIS programs that are portable very difficult. Plus,
> the standard itself is poorly written, and it's organization is such
> that it is arguable that ASIS users (not to mention implementers)
> need a license from ISO. So we're going to be busy redoing the
> entire standard.

This sounds like good news.