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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,38fc011071df5a27 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-06-16 12:14:30 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.freenet.de!news-lei1.dfn.de!news-koe1.dfn.de!RRZ.Uni-Koeln.DE!uni-duisburg.de!not-for-mail From: Georg Bauhaus Newsgroups: comp.lang.ada Subject: Re: Ideas for Ada 200X Date: Mon, 16 Jun 2003 19:14:29 +0000 (UTC) Organization: GMUGHDU Message-ID: References: <3EE7CC70.E1FD3A67@adaworks.com> <3EECA772.4B662024@adaworks.com> NNTP-Posting-Host: d2-hrz.uni-duisburg.de X-Trace: a1-hrz.uni-duisburg.de 1055790869 18814 134.91.1.15 (16 Jun 2003 19:14:29 GMT) X-Complaints-To: usenet@news.uni-duisburg.de NNTP-Posting-Date: Mon, 16 Jun 2003 19:14:29 +0000 (UTC) User-Agent: tin/1.5.8-20010221 ("Blue Water") (UNIX) (HP-UX/B.11.00 (9000/831)) Xref: archiver1.google.com comp.lang.ada:39269 Date: 2003-06-16T19:14:29+00:00 List-Id: Bill Findlay wrote: : On 16/6/03 18:09, in article bcktkf$ep$2@a1-hrz.uni-duisburg.de, "Georg : Bauhaus" wrote: : :> :> : shiftTally(shift)(dayOfWeek(month).tallyIndex).sortTally(s).nbRejects := :> :> : idem + 1; :> :> :> :> Hm. How about renaming and access values? :> : :> : Unfortunately, there are significant restrictions on the types of objects :> : that can be renamed; and explicitly using access values introduces aliasing, :> : which is better avoided if possible. :> :> (But it doesn't required explicit aliasing.) : : I must be mistaking your meaning. How do you obtain and use an access value : without aliasing the object it references; and explicitly so, if it is a : global or local object? What I had been thinking of was that there is no need to explicitly introduce bar: aliased Foo; if bar has been allocated with new, which surely is a restriction. (f being a function returning an access value to some new record with a component c, I can write f.c := f.c + baz; (and loose the anonymous object in this scope unless it is hooked somewhere else.) Am I right in thinking that there is an aliased view here, due to the implicit dereference in f.c, but not explicit aliasing in the sense described above?) -- Georg