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
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,cdf9d37fddaced23
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1994-09-10 12:37:45 PST
Path: 
 nntp.gmd.de!xlink.net!howland.reston.ans.net!usc!nic-nac.CSU.net!charnel.ecst.csuchico.edu!olivea!decwrl!pa.dec.com!crl.dec.com!jac.zko.dec.com!i.enet.dec.com!brett
From: brett@i.enet.dec.com (Bevin R. Brett)
Newsgroups: comp.lang.ada
Subject: Re: Ada 9X features
Date: 9 SEP 94 18:52:51 EST
Organization: Digital Equipment Corporation
Message-ID: <34qp9b$jqu@jac.zko.dec.com>
References: <940908231244_73672.2025_DHR48-1@CompuServe.COM>
NNTP-Posting-Host: I
Date: 1994-09-09T18:52:51-05:00
List-Id: <comp.lang.ada>


In article <940908231244_73672.2025_DHR48-1@CompuServe.COM>, Ken Garlington <73672.2025@COMPUSERVE.COM> writes...
>I would disagree with Bevin Brett's assessment of Ada 9X requirements bloat in
>one area: the ability to have access values that don't reference the heap. We

All that was required to satisfy this was a Foo'access attribute and a
pragma accessed(Foo).

Instead we got an incredible collection of general access types, lifetime
checking rules, 'unchecked_access, etc.

The ability to detect violations of lifetimes should have been left to
the implementor to do if the market really wanted it.

I agree that the fundamental reqt had to be met (there is probably a couple
of other oversights too in my list - for example a simple access-to-subprogram
was also needed) but the satisfaction of that requirement is an excellent
example of feature bloat.,

/Bevin

ps: I am somewhat surprised at the quietness of the reaction to what I thought
was a very radical position for a DR to be taking publicly - perhaps more
people agree with me than I guessed.