Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!ncis!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!purdue!gatech!udel!rochester!pt.cs.cmu.edu!cadre!pitt!cisunx!jcbst3
From: jcbst3@cisunx.UUCP (James C. Benz)
Newsgroups: comp.lang.c
Subject: Re: lint question
Message-ID: <15024@cisunx.UUCP>
Date: 17 Jan 89 20:08:23 GMT
References: <491@babbage.acc.virginia.edu> <9322@smoke.BRL.MIL>
Reply-To: jcbst3@unix.cis.pittsburgh.edu (James C. Benz)
Organization: Univ. of Pittsburgh, Comp & Info Sys
Lines: 10

In article <9322@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
>you should indeed test their return values and take proper error-
>recovery actions.  The one possible exception is
>	(void)fprintf(stderr, "...: operation failed\n");
>because if a write to the standard error output fails, you may have just

Okay, so where does one find out what error codes are returned from these
stdio functions?  The UNIX (AT&T 3B2) manuals I have say nothing in printf(3S)
about error codes, and stdio(3S) says "Individual function descriptions 
describe the possible error conditions"  Sounds like Catch 22 to me.