Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!uunet!brunix!rca From: rca@cs.brown.edu (Ronald C.F. Antony) Newsgroups: comp.sys.next Subject: Re: C Programming questions Message-ID: <71369@brunix.UUCP> Date: 9 Apr 91 07:02:18 GMT References: <1466@toaster.SFSU.EDU> Sender: news@brunix.UUCP Reply-To: rca@cs.brown.edu (Ronald C.F. Antony) Organization: Brown University Department of Computer Science Lines: 34 In article jwright@cfht.hawaii.edu (Jim Wright) writes: >eps@toaster.SFSU.EDU (Eric P. Scott) writes: >>In article gad@eclipse.its.rpi.edu writes: >>> the fprintf subroutine seems to always return a value of zero. > >>Different UNIX implementations disagree here. This is just >>something you'll have to live with. You're the first person >>I've seen who actually cared--usually the question comes up >>with respect to sprintf. > >I can find no NeXT documentation on what the printf family returns. I know >the agony of porting code that uses these return values, but that's no >reason not to document them. Nothing in digital librarian. grep turned >up only: > >stdio.h:extern int fprintf(FILE *stream, const char *format, ...); Good advice here: For UNIX questions look in the MAN PAGES, and NOT in the NeXT Developer Docs. If you are interested further in this topic, have a look at the vprintf, vfprintf and vsprintf functions and their MAN PAGE entry. Ronald ------------------------------------------------------------------------------ "The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man." G.B. Shaw | rca@cs.brown.edu or antony@browncog.bitnet