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,ba4846af158825ee
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!nntp.megapath.net!news.megapath.net.POSTED!not-for-mail
NNTP-Posting-Date: Tue, 20 Dec 2005 14:56:41 -0600
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
References: <1135101609.527495.321500@g49g2000cwa.googlegroups.com>
Subject: Re: Update_Element Spec. in Containers.Indefinite_Hashed_Maps
Date: Tue, 20 Dec 2005 15:01:01 -0600
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4952.2800
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4952.2800
Message-ID: <LdOdnSbgqZOU7TXeRVn-uQ@megapath.net>
NNTP-Posting-Host: 64.32.209.38
X-Trace: 
 sv3-ODK0OLDtHO4K6YkdYC6Sz/D+Z9/4zEQNHN7/2sfjgZFqmQdNO5Q10djLcQcT6UiP4ncJ+hq0QZdMJSG!N0YzqakJC01O+C229E2tynNxO4egaICbzYaPNt4aXs1VYcX5f0fJYPQCNJugo1PSt6t/DbhT/lvk
X-Complaints-To: abuse@megapath.net
X-DMCA-Complaints-To: abuse@megapath.net
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint
 properly
X-Postfilter: 1.3.32
Xref: g2news1.google.com comp.lang.ada:6947
Date: 2005-12-20T15:01:01-06:00
List-Id: <comp.lang.ada>

"Anh Vo" <anhvofrcaus@gmail.com> wrote in message
news:1135101609.527495.321500@g49g2000cwa.googlegroups.com...
> The Update_Element procedure specification has two paramters, Position
> and Process as implemented in GNAT-GPL. The one in the LRM 2005 has
> three paramters, Container as the additional and first paramter. Which
> one is the right one?

The Ada Amendment isn't quite finalized yet, so it still is changing
slightly. That means that older versions are likely to be somewhat out of
sync.

The change adding "Container" parameters to some operations, and changing
the modes of others, was approved at the York ARG meeting, and was made
shortly thereafterwards. (There were a dozen or so other changes approved,
including changes in the formal parameters for some of the generics).

The reason for this particular change is to ensure that a writeable
container is present for every operation that modifies a container. With the
original specification, you could modify a constant container (such as an
'in' parameter) simply by retrieving an appropriate cursor and then calling
Update_Element. We don't want to make modifying constants easy!

                               Randy.