Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!stanford.edu!agate!ziploc!eps
From: eps@toaster.SFSU.EDU (Eric P. Scott)
Newsgroups: comp.sys.next
Subject: Re: Fprintf (& friends) subroutines on NeXT
Summary: It really is 4.3 BSD compatible
Message-ID: <1473@toaster.SFSU.EDU>
Date: 9 Apr 91 00:12:51 GMT
References: <br=gvxf@rpi.edu>
Reply-To: eps@cs.SFSU.EDU (Eric P. Scott)
Organization: San Francisco State University
Lines: 19

In article <br=gvxf@rpi.edu> gad@eclipse.its.rpi.edu writes:
>That kinda begs the question though, why does fprintf *on the NeXT* return zero
>all the time?

I doubt it returns 0 *all* the time.

>       Does fprintf on the NeXT ever return anything *other* than zero?  If so,
>what?  When?  Why?

Maybe EOF when ferror would?

>Why did NeXT choose to do it this way?

Because 4.3 BSD did it that way (because UNIX/32V did it that way
(because V7 did it that way (because K&R did it that way))).

4.3-tahoe BSD (and later) returns the character count.

					-=EPS=-