From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=3.0 tests=BAYES_40,MSGID_SHORT
	autolearn=no autolearn_force=no version=3.4.5-pre1
Date: 25 Nov 91 17:02:16 GMT
From: agate!spool.mu.edu!wupost!zaphod.mps.ohio-state.edu!ub!dsinc!gvlf3.gvl.un
isys.com!email!parkhill@ucbvax.Berkeley.EDU  (parkhill)
Subject: Re: Ada Tasking problem
Message-ID: <5860@email.sp.unisys.com>
List-Id: <comp.lang.ada>

Humble suggestion:

  Why not treat your output console as a shared device and write a
  standard interface to the device?  Write a package specification
  that provides all the operations you require (locking the device,
  time sharing, type and format of output, whatever).  Hide the exact 
  method of implementation of output and locking of the device in 
  the body of a package.  The body of the package will probably require
  another task be added.

  I have found that it can be unwise to let tasks use an output device
  in an uncontrolled/unsynchronized manner.  Putting the control of 
  the synchronization in a single package keeps the code in the package
  instead of every task that might want to access a device (text_IO
  console).  The body may have to be implemented in a target dependant 
  manner but the other code remains more or less portable.

Robert Parkhill