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.6 required=5.0 tests=BAYES_05,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,ba049bdce87e95c1,start X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1994-09-22 12:30:57 PST Path: bga.com!news.sprintlink.net!howland.reston.ans.net!agate!barrnet.net!rational.com!rlk From: rlk@rational.com (Bob Kitzberger) Newsgroups: comp.lang.ada Subject: Re: Newbie question about generic linked list tasks Date: 22 Sep 1994 17:55:09 GMT Organization: Rational Software Corp Message-ID: <35sgdt$7e1@rational.rational.com> References: <35qb51$ksu@rational.rational.com> NNTP-Posting-Host: bonnie.rational.com X-Newsreader: TIN [version 1.2 PL2] Date: 1994-09-22T17:55:09+00:00 List-Id: I (rlk@rational.com) wrote some drivel: : generic : type Element ... : package List_Generic is : type List is private; : ... : end; ... : package body List_Generic is : task Access_Control is : entry Start_Reader ...; ... : end Access_Control; This is an example of what happens when firing off an answer before thinking it through (and yes, I had my morning coffee, so I can't use that as an excuse ;-) This solution will technically work, but will serialize access across all List objects for a particular List_Generic instantiation... when what is desired is serialized access to a particular List object. This implies the need for one task per List object, rather than one task per List_Generic instantiation. Egg on my face... see Robert Eachus' solution for a better approach. .Bob. -- Bob Kitzberger +1 (916) 274-3075 rlk@rational.com Rational Software Corp., 10565 Brunswick Rd. #11, Grass Valley, CA 95945