home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #27 / NN_1992_27.iso / spool / comp / lang / ada / 3329 < prev    next >
Encoding:
Internet Message Format  |  1992-11-21  |  769 b 
  1. Path: sparky!uunet!spool.mu.edu!uwm.edu!cs.utexas.edu!sun-barr!lll-winken!taurus!atlas!erickson
  2. From: erickson@atlas.cs.nps.navy.mil (David Erickson)
  3. Newsgroups: comp.lang.ada
  4. Subject: TEXT_IO & Tasks
  5. Message-ID: <7018@atlas.cs.nps.navy.mil>
  6. Date: 20 Nov 92 00:35:00 GMT
  7. Organization: Naval Postgraduate School, Monterey CA
  8. Lines: 11
  9.  
  10.  
  11. Perhaps this is covered in the LRM.  If so, I couldn't find it:
  12.  
  13. should blocking I/O (e.g. GET & PUT) block only the task which is
  14. executing the I/O?  This seems like a reasonable assumption, but is
  15. it required?  I know that the Meridian and Verdix compilers block
  16. only the task which is executing the I/O.  So, for example, if task A
  17. is executing a GET from stdin, task B can still PUT to stdout while
  18. A is blocked.
  19.  
  20. -Dave Erickson
  21.