Re: Ada replacements for DOS I/O

[eachus@spectre.mitre.org (Robert I. Eachus)]

In article <392r15$gl3@schonberg.cs.nyu.edu> dewar@cs.nyu.edu (Robert Dewar) writes:

 > Of course simultaneous text_io from separate tasks to the same file (e.g.
 > standard output) is pretty hard to define anyway (at what level does the
 > output get interleaved - lines, text_io calls, characters, pixels?)

   Characters, Robert, characters. ;-)

   More seriously, chapter 14 is written to require, at worst, that
gets and puts of individual characters be treated as indivisible
actions.  Any reasonable tasking aware version of TEXT_IO can and
should lock at a higher level, but it is almost impossible to treat
Text_IO calls as atomic.  (For example, a read of a number can require
reading thousands of bytes from the external file.)

   When I've written tasking aware versions of Text_IO (usually by
revising the vendor supplied I/O routines and calling the result
Nice_IO or Tasking_IO), the locking granularity was either a line of
text or a text_io call, whichever was smaller.

--

					Robert I. Eachus

with Standard_Disclaimer;
use  Standard_Disclaimer;
function Message (Text: in Clever_Ideas) return Better_Ideas is...