From: "J-P. Rosen" <rosen@adalog.fr>
Subject: Re: Read-write mutex sometimes fails on deadlock
Date: Sun, 12 Nov 2017 06:21:20 +0100
Date: 2017-11-12T06:21:20+01:00 [thread overview]
Message-ID: <ou8lod$3iq$3@dont-email.me> (raw)
In-Reply-To: <1810768e-7846-43ca-9871-b2468a060c37@googlegroups.com>
Le 12/11/2017 à 05:33, Robert Eachus a écrit :
> On Monday, November 6, 2017 at 1:31:07 PM UTC-5, Simon Wright wrote:
>> Robert Eachus <rieachus@comcast.net> writes:
>>
>>> entry Write (D: in Data) is
>>> begin
>>> The_Data := D;
>>> Some_Data := True;
>>> Print(D);
>>> delay 0.1;
>>> end Write;
>>
> Having said that, the delay 0.1 is very naughty, but on most hardware it will be implemented as a counting loop. (Make it delay 0.0001 if that makes you happier. ;-) It is not illegal, and is only erroneous if it results in a scheduling action.
>
Delay is potentially blocking operation, so this is definitely a bounded
error. But it is allowed for a bounded error situation to give the
proper result...
--
J-P. Rosen
Adalog
2 rue du Docteur Lombard, 92441 Issy-les-Moulineaux CEDEX
Tel: +33 1 45 29 21 52, Fax: +33 1 45 29 25 00
http://www.adalog.fr
next prev parent reply other threads:[~2017-11-12 5:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-28 20:02 Read-write mutex sometimes fails on deadlock pascal.malaise
2017-11-06 18:24 ` Robert Eachus
2017-11-06 18:31 ` Simon Wright
2017-11-12 4:33 ` Robert Eachus
2017-11-12 5:21 ` J-P. Rosen [this message]
2017-11-15 22:57 ` Randy Brukardt
2017-11-15 23:05 ` Randy Brukardt
2017-11-06 21:01 ` Dmitry A. Kazakov
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox