From: Stephen Leake <stephen_leake@stephe-leake.org>
Subject: Re: Accessibility check failure with Implicit_Dereference aspect
Date: Wed, 13 Aug 2014 04:10:11 -0500
Date: 2014-08-13T04:10:11-05:00 [thread overview]
Message-ID: <85egwku558.fsf@stephe-leake.org> (raw)
In-Reply-To: 3854a5ec-f49a-4c81-916b-e8cf750dc2ad@googlegroups.com
Lucretia <laguest9000@googlemail.com> writes:
> generic
> type T is new Quicksilver.Containers.Counted_Items.Counted_Item with private;
> package Quicksilver.Containers.Smart_Pointers is
> type Access_T is access all T;
>
> <snip>
>
> On compiling a test, I get the following warnings:
>
> >>> warning: accessibility check failure
>
> Is this a compiler issue or me?
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.
--
-- Stephe
next prev parent reply other threads:[~2014-08-13 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 17:03 Accessibility check failure with Implicit_Dereference aspect Lucretia
2014-08-13 9:10 ` Stephen Leake [this message]
2014-08-13 18:38 ` Luke A. Guest
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox