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=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,73975695cdfcb86f
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.230.68 with SMTP id sw4mr4232364pbc.7.1333659845775;
        Thu, 05 Apr 2012 14:04:05 -0700 (PDT)
MIME-Version: 1.0
Path: 
 r9ni22669pbh.0!nntp.google.com!news2.google.com!goblin2!goblin.stu.neva.ru!newsfeed.x-privat.org!news.jacob-sparre.dk!munin.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
Subject: Re: Dispatching callback handed over to C
Date: Thu, 5 Apr 2012 16:04:00 -0500
Organization: Jacob Sparre Andersen Research & Innovation
Message-ID: <jll1c4$dsu$1@munin.nbi.dk>
References: <slrnjnl944.1lme.lithiumcat@sigil.instinctive.eu>
 <6fb83c74-b2a4-4ae8-9c89-d755b737198f@v22g2000vby.googlegroups.com>
 <slrnjnlpmo.1lme.lithiumcat@sigil.instinctive.eu>
 <85d1ad51-c02b-44fa-87b6-02aa1d8ba1b2@x17g2000vba.googlegroups.com>
 <jlfm35$ohb$1@munin.nbi.dk> <slrnjnnvk6.1lme.lithiumcat@sigil.instinctive.eu>
 <jli7ca$6cr$1@munin.nbi.dk> <slrnjnqnng.1lme.lithiumcat@sigil.instinctive.eu>
NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net
X-Trace: munin.nbi.dk 1333659844 14238 69.95.181.76 (5 Apr 2012 21:04:04 GMT)
X-Complaints-To: news@jacob-sparre.dk
NNTP-Posting-Date: Thu, 5 Apr 2012 21:04:04 +0000 (UTC)
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Date: 2012-04-05T16:04:00-05:00
List-Id: <comp.lang.ada>

"Natasha Kerensikova" <lithiumcat@gmail.com> wrote in message 
news:slrnjnqnng.1lme.lithiumcat@sigil.instinctive.eu...
> On 2012-04-04, Randy Brukardt <randy@rrsoftware.com> wrote:
...
> Now about aliasing, I read somewhere (but can't find anymore where) that
> arguments whose type is tagged is automatically aliased. Is it enough
> aliasing, or should the original object be declared as aliased too?

It probably doesn't hurt to declare the original object as aliased, but as 
always it depends on the compiler. If you're actually passing these to the C 
code, then of course the assumption that the (by-reference) parameters can 
change will cover you in any case. If they're passed some other way, then 
marking them as aliased (or volatile as you noted elsewhere) would be a good 
idea.

                                          Randy.