Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!purdue!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.unix.wizards
Subject: Re: sticky EOF
Keywords: stdio
Message-ID: <10229@smoke.BRL.MIL>
Date: 7 May 89 22:43:55 GMT
References: <2017@thor.acc.stolaf.edu>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 9

In article <2017@thor.acc.stolaf.edu> mike@thor.acc.stolaf.edu (Mike Haertel) writes:
>After EOF is returned for the first time, Berkeley stdio functions
>will not attempt to read further input if the user tries, but will
>instead continue returning EOF.

Yeah, we went all over this many moons ago.  Sticky EOF was
introduced at one point by Bill Shannon.  It's not considered
proper behavior and should have been removed by now.  (Chris
Torek should be able to tell us if it was.)