Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.lang.c
Subject: Re: casts to (void)
Message-ID: <1154@umcp-cs.UUCP>
Date: Thu, 8-Aug-85 06:56:23 EDT
Article-I.D.: umcp-cs.1154
Posted: Thu Aug  8 06:56:23 1985
Date-Received: Sun, 11-Aug-85 05:14:29 EDT
References: <11@brl-tgr.ARPA> <484@talcott.UUCP>
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 15

>The fundamental problem here is that the way stdio indicates that
>a write failed is just inconvenient. In 99.999% of all cases, you
>don't want to care about failing printf's. The appropriate default 
>action is to print a diagnostic message (where?) and to kill the
>process, not to return a failure code that has to be checked
>every single time you print something.

True; however, if you are ever writing something intended as a
general library, *never ever ever* put something like that in
without at the very least providing some way around it.  When you
need to recover and can't, you'll be sorry. . . .
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@maryland