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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,e9c4fd87d5e1f936
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1995-01-19 15:14:48 PST
Newsgroups: comp.lang.ada
Path: 
 nntp.gmd.de!newsserver.jvnc.net!nntpserver.pppl.gov!princeton!gw1.att.com!csn!ncar!gatech!swrinde!pipex!uunet!world!bobduff
From: bobduff@world.std.com (Robert A Duff)
Subject: Re: Adjust, Finalize
Message-ID: <D2oDwo.7Dr@world.std.com>
Organization: The World Public Access UNIX, Brookline, MA
References: <leschkes.790467588@ferret>
Date: Thu, 19 Jan 1995 23:14:48 GMT
Date: 1995-01-19T23:14:48+00:00
List-Id: <comp.lang.ada>

In article <leschkes.790467588@ferret>,
Scott Leschke <leschkes@ferret.cig.mot.com> wrote:
>Just as a check, are the procedures Adjust and Finalize implicitly protected
>against simultanious invocation by multiple tasks ?

No.  If you want that, you have to program it yourself using protected
types.

However, these operations *are* protected from abort.  (Actually, the
entire assignment is protected, and the Initialize and Finalize
operations are protected.)  This is true of any type that is controlled,
or has any controlled subcomponents.  It is not true of plain old types,
of course -- protected assignment of, say, integers from abort would be
too inefficient.

- Bob