Path: utzoo!attcan!uunet!husc6!uwvax!oddjob!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: stdio EOF
Message-ID: <13427@mimsy.UUCP>
Date: 7 Sep 88 15:24:57 GMT
References: <813@ms3.UUCP> <1246@mcgill-vision.UUCP> <669@super.ORG> <8422@smoke.ARPA>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 13

In article <8422@smoke.ARPA> gwyn@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@mimsy.umd.edu	Path:	uunet!mimsy!chris