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: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: Luke A. Guest Newsgroups: comp.lang.ada Subject: Re: Accessibility check failure with Implicit_Dereference aspect Date: Wed, 13 Aug 2014 18:38:34 +0000 (UTC) Organization: Aioe.org NNTP Server Message-ID: <1265553776429647827.181612laguest-archeia.com@nntp.aioe.org> References: <3854a5ec-f49a-4c81-916b-e8cf750dc2ad@googlegroups.com> <85egwku558.fsf@stephe-leake.org> NNTP-Posting-Host: N/pbMdiWC6CASiDfygFGqA.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@aioe.org User-Agent: NewsTap/4.0.1 (iPhone/iPod Touch) X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:21727 Date: 2014-08-13T18:38:34+00:00 List-Id: Stephen Leake wrote: > accessibility checks have to do with not creating dangling pointers; > they depend on exactly where the type is declared and where the access > value is created and used. So we need to see the entire program to help. > > In general, if the access type is at library level, there will be no > accessibility issues. Thanks but I got it sorted and deleted this post. It was an anonymous access type in the controlled type and freeing based on a defined access type. Like