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,20fe5a249f5f6562 X-Google-Attributes: gid103376,public X-Google-Thread: ffc1e,9425605c29366d79 X-Google-Attributes: gidffc1e,public From: Laurent Guerby Subject: Re: multi reads, single write Date: 1999/12/16 Message-ID: <861z8mfthx.fsf@ppp-107-102.villette.club-internet.fr>#1/1 X-Deja-AN: 561686763 References: <3847B024.EC4FD04F@essex.ac.uk> <3854FCC0.D0127CD8@bbnplanet.com> <3858F8FA.CA9BD032@bbnplanet.com> X-Trace: front3m.grolier.fr 945380574 10322 194.158.107.102 (16 Dec 1999 21:42:54 GMT) Organization: Club-Internet (France) NNTP-Posting-Date: 16 Dec 1999 21:42:54 GMT Newsgroups: comp.programming.threads,comp.lang.ada Date: 1999-12-16T21:42:54+00:00 List-Id: "Mike Silva" writes: > I've cross-posted this to comp.lang.ada because I'm interested in any > insight they may have there. While an Ada task entry can easily do such > bounded waiting (see e.g. http://www.adahome.com/Ammo/cpp2ada.html "7.2.4 > delays"), it appears from my newbie reading on protected types that they do > not allow this. [...] They do, a protected entry is just like a task entry. The difference is between protected procedure and protected entries. Calling a protected procedure is conceptually not blocking (the model is spin locking). Example of bounded waiting on an entry: R : Resource; ... select R.Seize; or delay 1.0; -- resource still not available after 1 second, try something else end select; --LG