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.1 required=5.0 tests=BAYES_05,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: Tom Payne Subject: Re: multi reads, single write Date: 1999/12/14 Message-ID: <836gbn$j72$2@pravda.ucr.edu>#1/1 X-Deja-AN: 560750415 References: <3847B024.EC4FD04F@essex.ac.uk> <833uh9$e4p$1@pravda.ucr.edu> Organization: University of California, Riverside User-Agent: tin/pre-1.4-19990216 ("Styrofoam") (UNIX) (Linux/2.2.8 (i686)) Newsgroups: comp.programming.threads,comp.lang.ada Date: 1999-12-14T00:00:00+00:00 List-Id: In comp.programming.threads Vladimir Olensky wrote: > Tom Payne wrote in message <833uh9$e4p$1@pravda.ucr.edu>... [...] >>Vladimir Olensky wrote: >>[...] >>> My answer was exactly how to do that in a very simple and efficient >>> way - using protected types in Ada that are specially designed for >>> "multi-read single write" scenario in multithreaded/multitasking >>> environment. >> >>Your answer does not, however, respond to the question of "what is the >>most efficient way to implement" a CREW protocol. It merely states >>that all Ada implementations have a built-in implementation, which is >>interesting but not particularly helpful. [...] > ============================================= > Some quotes from Ada ARM (9.1): [...] > Ada 95 protected objects are an amalgam of the best features > of conditional critical regions and monitors: they collect all the > data and operations together, like monitors, and yet they have > barriers, like conditional critical regions. The barriers describe > the required state that must exist before an operation can be > performed in a clear manner which aids program proof and > understanding. Protected objects are very similar to the shared > objects of the Orca language developed by Bal, Kaashoek and > Tanenbaum [Bal 92]. That's helpful and interesting, especially the last sentence. Thanks, ;-) Tom Payne