Date: Mon, 18 Nov 1996 00:58:54 +1100 From: Bruce Evans <bde@zeta.org.au> To: j@uriah.heep.sax.de, wosch@cs.tu-berlin.de Cc: bde@zeta.org.au, cvs-all@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, cvs-usrbin@freefall.freebsd.org, joerg@freefall.freebsd.org, joerg_wunsch@uriah.heep.sax.de Subject: Re: cvs commit: src/usr.bin/sed main.c Message-ID: <199611171358.AAA19233@godzilla.zeta.org.au>
index | next in thread | raw e-mail
>> >> Erm, as I told the submitter, this introduces C programmer's bug >> >> #<a bit larger than 1>: feof() is not valid until EOF has been read. >> > >> >Huh? I can't find any reference claiming this. >> >> The reference is in my private mail box, as Bruce wrote. > >Nope, my question was which standard claims that feof() could return >wrong results after a successful fopen() but before reaching the EOF >of the stream. It returns correct but uninteresting results (always 0) from after fopen() until EOF has been read from the stream. ANSI standard. Brucehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611171358.AAA19233>