Path: utzoo!attcan!lsuc!ncrcan!ziebmef!mdfreed
From: mdfreed@ziebmef.uucp (Mark Freedman)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Turbo C 2.0 and EMS
Message-ID: <1989Jan19.103005.18755@ziebmef.uucp>
Date: 19 Jan 89 15:30:02 GMT
References: <31050@tut.cis.ohio-state.edu> <597@dms.UUCP> <6957@june.cs.washington.edu>
Reply-To: mdfreed@ziebmef.UUCP (Mark Freedman)
Organization: Ziebmef Public Access Unix, Toronto, Ontario
Lines: 15


(known bugs in Turbo C 2.0)
   This isn't a bug, but I did spend some enjoyable time with Turbo Debugger
verifying that fgets() works as it SHOULD, not as it's DOCUMENTED.

   On page 122 of the "Turbo C Reference Guide", the "Remarks" section for
fgets() states "fgets does not place the newline character in the string".
Aside from the questionable English, this statement contradicts every other
definition of fgets which I have AND the actual behaviour of the function.

   Perhaps Borland has to add an "is this blatantly false" checker to the
Sprint wordprocessor :-)

(yes, I ***KNOW*** that "REAL" programmers determine what a function does by
stepping through it with a debugger, rather than by reading the manual :-))