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,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII
Path: 
 g2news2.google.com!news4.google.com!proxad.net!feeder1-2.proxad.net!cleanfeed2-b.proxad.net!nnrp16-2.free.fr!not-for-mail
Date: Wed, 01 Jul 2009 21:22:10 +0200
From: Damien Carbonne <damien.carbonne@free.fr>
User-Agent: Thunderbird 2.0.0.22 (X11/20090605)
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Issue with GNAT GPL 2009 and GtkAda
References: <4A414EBB.8060204@free.fr> <uk532lyzd.fsf@stephe-leake.org>
 <utz24lm2n.fsf@stephe-leake.org>
 <1avd65rn49abv$.krcxo2gdzb16$.dlg@40tude.net>
 <4a43c9ce$0$420$426a74cc@news.free.fr> <u1vp7l4tm.fsf@stephe-leake.org>
 <4a4537a3$0$441$426a34cc@news.free.fr> <ueit5kjl4.fsf@stephe-leake.org>
 <4a460fd7$0$10813$426a74cc@news.free.fr>
 <4a46121a$0$414$426a74cc@news.free.fr> <h2beeg$d5c$1@munin.nbi.dk>
In-Reply-To: <h2beeg$d5c$1@munin.nbi.dk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Message-ID: <4a4bb763$0$31137$426a34cc@news.free.fr>
Organization: Guest of ProXad - France
NNTP-Posting-Date: 01 Jul 2009 21:22:11 MEST
NNTP-Posting-Host: 82.247.219.63
X-Trace: 1246476131 news-4.free.fr 31137 82.247.219.63:36092
X-Complaints-To: abuse@proxad.net
Xref: g2news2.google.com comp.lang.ada:6787
Date: 2009-07-01T21:22:11+02:00
List-Id: <comp.lang.ada>

I think I now understand the issue.
Thanks to all of you for your patience and explanations.

I also think that all this explains the issues I had had in the past 
(also with GtkAda) when mixing [in] [out] parameters and access.
I always needed to use Unchecked_Access which I did not find 
satisfactory. This seems to be the only solution when mixing standard 
parameters modes and access.
This time, the Object.Func notation made things less obvious. Next time 
I will be more careful !

Regards,

Damien

Randy Brukardt a �crit :
> "Damien Carbonne" <damien.carbonne@free.fr> wrote in message 
> news:4a46121a$0$414$426a74cc@news.free.fr...
> ...
>> This behaves as expected (by me).
>> So a tagged type is really and always aliased, whatever its mode (in, out, 
>> in out) is. At least, this is what understand from those examples.
> 
> That's not right, unfortunately. Tagged *parameters* are always considered 
> aliased, but other kinds of tagged objects are not (necessarily) considered 
> aliased. The designated object of an access value is considered aliased, 
> though.
> 
> Bob explained this in more detail.
> 
>                                        Randy.
> 
>