On Sat, 22 Feb 1997, Russell Berry wrote:
[snip]
> should not behave as expected. Is this clear now?? I was not
> requesting assistance in writing a simple program, it was meant
> to illustrate the odd behavior of feof(). Now, if feof is
> indeed broken, I believe it is indeed a kernel related issue,
> even if it isn't exactly a direct kernel function.
I'm not sure that it is a kernel related issue at all. ALL of the f*
functions are library implementations, the kernel has no mechanism for
application buffered I/O performed in this manner. If there is indeed a
problem, I would suspect libc above all else. What version of libc are
you running?
+-------------------------------------------------------------------+
+ -- Finger: flood@evcom.net for my PGP public key -- +
+-------------------------------------------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBMw8tNxsjWkWelde9AQErswP9EgZ/ec4UsttTTT8zx4lSCJHLmbKCqYAI
dEiilR3iR4Rhn2t1ZAr2JF9e2SIi1FHUcqXYJZ0n60y1GkAiO3/smhfO4pUlR3v0
DzKgdnrKd9bv3Sq5vVpmG0J6WTsoEJvt8YZKFXVzXRrNDRFmpqinTQlh7QHxXLj7
MdYbKEGFCR8=
=yue9
-----END PGP SIGNATURE-----