cvs.gedasymbols.org/archives/browse.cgi   search  
Mail Archives: djgpp/1997/02/10/21:25:06

From: mert0407 AT sable DOT ox DOT ac DOT uk (George Foot)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: ISO "C" violation.
Date: Sun, 09 Feb 1997 17:32:06 GMT
Organization: Oxford University
Lines: 17
Message-ID: <32fe09ad.5473098@news.ox.ac.uk>
References: <19970208 DOT 183318 DOT 4231 DOT 0 DOT stodmaster AT juno DOT com> <slrn5froki DOT 7de DOT nxk3 AT dante DOT student DOT cwru DOT edu> <slrn5frp00 DOT 7de DOT nxk3 AT dante DOT student DOT cwru DOT edu>
NNTP-Posting-Host: mc31.merton.ox.ac.uk
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

On 9 Feb 1997 14:49:39 GMT, nxk3 AT dante DOT student DOT cwru DOT edu (Natarajan
Krishnaswami) wrote:

>I know it's tacky to follow up to my own post, but I just looked at the 
>libc.inf description of fprintf's return value--it says only that it returns
>the number of characters written.  
>
>Perhaps an error in the documentation?

More of an ommision...

As far as I tested it, it complies with the ANSI C specification, i.e.
returning the number of items processed, or EOF on file I/O error.
Maybe the docs should be extended in this way... It's certainly a
useful fact, the EOF condition.

George Foot

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019