Path: utzoo!attcan!uunet!steinmetz!ge-dab!ge-rtp!edison!rja
From: rja@edison.GE.COM (rja)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Turbo C 2.0 Bugs
Summary: not really bugs
Message-ID: <1777@edison.GE.COM>
Date: 18 Jan 89 13:11:39 GMT
References: <31050@tut.cis.ohio-state.edu> <597@dms.UUCP> <5543@phoenix.Princeton.EDU>
Organization: GE-Fanuc North America
Lines: 21

In article <5543@phoenix.Princeton.EDU>, jwbirdsa@phoenix.Princeton.EDU (James Webster Birdsall) writes:
>    cprintf() treats the character '\n' as a linefeed only -- it omits
> the carriage return. 

cprintf() is a Borland (maybe in MS C too) specific call.  Moreover, the
TC 2.0 documentation clearly notes that cprintf treats '\n' as linefeed only.
While folks might not like the behavior, this is NOT a bug.

>    As for other bugs, didn't somebody report an odd bug in the stat()
> function a few days ago?

As I noted in e-mail to that poster, the stat() difficulty isn't really
a bug but a compatibility problem inherent in the way that IBM PCs handle
their internal clock/calendar (different from the UNIX/C way of doing things).
Borland did the best that they could with stat(), given the architecture
of the IBM PCs.

______________________________________________________________________________
         rja@edison.GE.COM      or      ...uunet!virginia!edison!rja  
     via Internet (preferable)          via uucp  (if you must)
______________________________________________________________________________