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: ffc1e,fb45e48e8dddeabd
X-Google-Attributes: gidffc1e,public
X-Google-Thread: 103376,fb45e48e8dddeabd
X-Google-Attributes: gid103376,public
From: Robert A Duff <bobduff@world.std.com>
Subject: Re: Ada Protected Object Tutorial #1
Date: 1999/12/17
Message-ID: <wcc3dt28klk.fsf@world.std.com>#1/1
X-Deja-AN: 561748186
Sender: bobduff@world.std.com (Robert A Duff)
References: <839toq$pu$1@bgtnsc03.worldnet.att.net>
Organization: The World Public Access UNIX, Brookline, MA
Newsgroups: comp.programming.threads,comp.lang.ada
Date: 1999-12-17T00:00:00+00:00
List-Id: <comp.lang.ada>

"James S. Rogers" <jimmaureenrogers@worldnet.att.net> writes:

> This is the first of hopefully several examples of uses for Ada Protected
> Objects.

People seem to get confused about the difference between waiting for a
lock to become free, and waiting for a barrier to become true.  Only the
latter is called "blocking" in Ada 95 terms, and the former is sort of
swept under the rug.  If your tutorial can explain all that clearly and
simply, you will have done a great service.

- Bob