James Giles wrote:
> But, I didn't propose that unbuffered I/O be provided. I proposed that,
> by default, all WRITE statements should be implemented to flush as
> the last operation before control is returned to the user (on those
> systems that require explicit flushes).
Sorry, that can't be done due to legacy codes---one cannot change this now, or
a lot of codes will plumet in efficiency. What could maybe be added in some
next revision is an OPEN keyword which allows one to turn buffering off, in
the sense that every WRITE to that unit will be flushed immediately. Moot
area of the standard anyway. How to deal with stdout though?
Aleksandar
|