Path: utzoo!mnetor!uunet!littlei!foobar!argent!agora!qintar
From: qintar@agora.UUCP (Jim Seymour)
Newsgroups: comp.sys.ibm.pc
Subject: Turbo C bug (?)
Message-ID: <734@agora.UUCP>
Date: 18 Feb 88 05:55:41 GMT
Reply-To: qintar@agora.UUCP (Jim Seymour)
Organization: Cipher Systems, Inc. (North Plains, Oregon)
Lines: 21

I almost hate to do this since I like Turbo C so much, but...

In version 1.0 I noticed what seemed to be a bug in the read() function.
The docs claim (and the standard dictates) that this function returns the
actual byte count read in from the file.  I had a program written originally
for the Manx Aztec C compiler which read data from a file in 16 byte chunks
and checked the return code to verify how many bytes were read.

Under 1.0 it seemed that this number had no bearing on the actual byte count.
It would read in all 16, but return some number close to, but not equal to,
16.

Now, version 1.5 is out and I assumed the bug would be gone.  However, the same
symptoms exist.   Has anybody else encountered this or am I doing something
horribly wrong?

     -Jim Seymour              ...tektronix!reed!percival!agora!qintar
     =================================================================
     Cipher Systems, Inc.                           USMail:
     P.O. Box 329                                   1308 S.E. Division
     North Plains, OR  97133                        Portland, OR 97202