Date:	Wed, 22 Dec 93 13:13:53 +0100
From:	kuku AT acds DOT physik DOT rwth-aachen DOT de (Christoph Kukulies)
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: fscanf different behaviour

I said in a previous mail that fscanf() does not return EOF in 1.11 while
it does under 1.10 when end of file is reached. 

Robert D. Seals (rob AT dinner DOT asrc DOT albany DOT edu) wrote that EOF ain't got 
nothing to do with scanf and friends.

This is wrong. In fact according to ANSI X3.159-1989 (``ANSI C'') fscanf
should return EOF when end-of-file occurs. This is also in K&R second
edition p. 245.

So I regard this a bug in the 1.11 implementation of fscanf(). Sorry
for not being able to supply a fix since I havn't yet built up a
compile environment to build djgpp 1.11 in full (or libc only).

--Chris
----------------------------------------------------------------------------
Christoph P. U. Kukulies                 | BIX: chriskuku AT bix DOT com
kuku AT acds DOT physik DOT rwth-aachen DOT de          | CIS: 73007,1525
*** Error code 1

Stop.

- Raw text -