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,55f6e230b02eff2f
X-Google-Attributes: gid103376,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!postnews.google.com!d55g2000hsg.googlegroups.com!not-for-mail
From: Matthew Heaney <mheaney@on2.com>
Newsgroups: comp.lang.ada
Subject: Re: Containers - nontrivial element access
Date: Tue, 02 Oct 2007 09:44:00 -0700
Organization: http://groups.google.com
Message-ID: <1191343440.985588.143470@d55g2000hsg.googlegroups.com>
References: <1191275759.184463.238350@n39g2000hsh.googlegroups.com>
   <grgMi.113544$Xa3.78829@attbi_s22>
NNTP-Posting-Host: 66.162.65.129
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Trace: posting.google.com 1191343441 8796 127.0.0.1 (2 Oct 2007 16:44:01
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Tue, 2 Oct 2007 16:44:01 +0000 (UTC)
In-Reply-To: <grgMi.113544$Xa3.78829@attbi_s22>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7,gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: d55g2000hsg.googlegroups.com; posting-host=66.162.65.129;
   posting-account=ps2QrAMAAAA6_jCuRt2JEIpn5Otqf_w0
Xref: g2news2.google.com comp.lang.ada:2249
Date: 2007-10-02T09:44:00-07:00
List-Id: <comp.lang.ada>

On Oct 1, 8:39 pm, "Jeffrey R. Carter"
<spam.jrcarter....@acm.nospam.org> wrote:

> You have to compare apples to apples. In C/++, everything is aliased, so
> you have to make everything aliased on the Ada side, too. That means you
> store access values, not objects.

But then you're not comparing apples to apples.  This problem has a
straight-forward solution, as I demonstrated in my earlier post.


>Then you have something similar:
>
> Swap (Left  => People.Element (Left).Salary,
>        Right => People.Element (Right).Salary);

This is far less safe then simply using Update_Element in nested
fashion.