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=unavailable autolearn_force=no version=3.4.4
Path: 
 border1.nntp.dca3.giganews.com!border2.nntp.dca3.giganews.com!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!feeder.erje.net!eu.feeder.erje.net!news.szaf.org!news.gnuher.de!news.enyo.de!.POSTED!not-for-mail
From: Florian Weimer <fw@deneb.enyo.de>
Newsgroups: comp.lang.ada
Subject: Accessibility checks
Date: Wed, 17 Jul 2013 22:09:24 +0200
Message-ID: <87mwplvthn.fsf@mid.deneb.enyo.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: news.enyo.de 1374091733 739 172.17.135.6 (17 Jul 2013 20:08:53 GMT)
X-Complaints-To: news@enyo.de
Cancel-Lock: sha1:nQCckZZMbLeEKUdYQgq5PHfMiTE=
X-Original-Bytes: 1147
Xref: number.nntp.dca.giganews.com comp.lang.ada:182553
Date: 2013-07-17T22:09:24+02:00
List-Id: <comp.lang.ada>

One thing in Ada I could never quite grasp where the accessiblity
checks.  I haven't seen much Ada code, and personally, I didn't have
much need for nested access types anyway.  If I have used them, they
were still potentially unsafe due to aliasing or calls to
Unchecked_Deallocation in neighboring code.

So what's the point for this language feature?  It seems to add quite
a bit of complexity to the language.