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.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!mnetor!uunet!husc6!think!ames!pasteur!ucbvax!ACF2.NYU.EDU!flynn
From: flynn@ACF2.NYU.EDU (Susan Flynn)
Newsgroups: comp.lang.ada
Subject: Tasking and delays,  Robert Dewar's response
Message-ID: <8802192256.AA02476@acf2.NYU.EDU>
Date: 19 Feb 88 22:56:31 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
List-Id: <comp.lang.ada>

From: dewar@acf2.nyu.edu (Robert Dewar)
Date: 17-Feb-88 23:25 EST
Subject: Re: Tasking and delays, again...

An interesting question in the Feldman delay test is whether it is valid
for two tasks to "simultaneously" [i.e. without intermediate synchronization]
write to the standard output file. It could be argued that the file object
accessed is a shared variable, and that thus 9.11 makes such a program
erroneous. 

In the case of FLOAT_IO, the variables DEFAULT_FORE etc are clearly shared
variables, so you CERTAINLY cannot change one of these defaults and then
use the package from some other task.

If some kind of sharing is permitted, what is the rule concerning 
indivisibility. As far as Ada is concerned, putting a string is just as
much an atomic action as putting a character, so there seems no reason
to expect interruption on a character by character basis (if this seems
permissible, why not interrupt after an individual vector or pixel is
drawn on the output screen?)