From: john@assen.demon.co.uk (John McCabe)
Subject: Re: Uninterruptible (atomic) operation?
Date: 1996/12/09
Date: 1996-12-09T00:00:00+00:00 [thread overview]
Message-ID: <32abcb40.740498@news.demon.co.uk> (raw)
In-Reply-To: 9612111939.AA14087@most
"W. Wesley Groleau (Wes)" <wwgrol@PSESERV3.FW.HAC.COM> wrote:
>> In article <E25tK3.3G7@world.std.com> bobduff@world.std.com (Robert A Duff)
>> writes:
>>
<..snip..>
>This is pretty close. But why do we need the lock? Isn't that implied
>by Atomic/Shared? LRM 83 9.11 (11) "each of direct reading and direct
>updating is implemented as an individual implementation."
Just a brief note, but don't trust pragma shared (in Ada 83) to do
what would seem reasonable. I've learned through experience that this
is the case. The LRM 83 reference is very woolly. It's well worth
reading Robert Dewar's report on Shared Variables and Ada 9X issues
available from AdaIC on this matter.
Best Regards
John McCabe <john@assen.demon.co.uk>
next prev parent reply other threads:[~1996-12-09 0:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-12-11 0:00 Uninterruptible (atomic) operation? W. Wesley Groleau (Wes)
1996-12-09 0:00 ` John McCabe [this message]
1996-12-13 0:00 ` Robert Dewar
1996-12-12 0:00 ` Robert Dewar
1996-12-13 0:00 ` J-P. Rosen
1996-12-13 0:00 ` Robert I. Eachus
-- strict thread matches above, loose matches on Subject: below --
1996-12-09 0:00 W. Wesley Groleau (Wes)
1996-12-09 0:00 ` Robert A Duff
1996-12-10 0:00 ` Bob Gilbert
1996-12-11 0:00 ` Robert I. Eachus
1996-12-11 0:00 ` Robert S. White
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox