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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,5b86cfa15b273e36
X-Google-Attributes: gid103376,public
From: tmoran@bix.com (Tom Moran)
Subject: Re: Protected types made of ADT's, and Passive Iterators
Date: 1998/09/05
Message-ID: <35f0de0e.49020294@SantaClara01.news.InterNex.Net>#1/1
X-Deja-AN: 388091887
References: <udpvdbl8uf.fsf@tanana.llnl.gov>
Organization: InterNex Information Services 1-800-595-3333
Newsgroups: comp.lang.ada
Date: 1998-09-05T00:00:00+00:00
List-Id: <comp.lang.ada>

> procedure Insert (Into_List : in out Instance; The_Item : in Item);

>    generic
>        with procedure Process
>                          (The_Item : in Item; Continue : in out Boolean);
>    procedure Iterate (Over_List : in Instance);
What happened in the single tasking version when an Insert occurred
during an Iterate?  What should happen in the multi-tasking version?
Should an Insert be locked out during an Iterate?  Or just during the
step from one item to the next? Or something else?
  How about adding to the list a protected component that was
essentially an Access_Allowed flag, ie, put a protected component into
the list, instead of putting the list into a protected record.