stdio EOF
Chris Torek
chris at mimsy.UUCP
Thu Sep 8 01:24:57 AEST 1988
In article <8422 at smoke.ARPA> gwyn at smoke.ARPA (Doug Gwyn ) writes:
>... In fact [stdio] EOF should not be "sticky"; if more data becomes
>available, as on a terminal, it should be available for subsequent
>reading. The 4.2BSD implementation broke this but it might be okay
>on 4.3BSD.
I thought this behaviour was added to 4.2BSD to conform to some
existing standard.
What does the dpANS say? POSIX?
--
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain: chris at mimsy.umd.edu Path: uunet!mimsy!chris
More information about the Comp.unix.wizards
mailing list