casts to (void)

[Chris Torek]

>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 at umcp-cs		ARPA:	chris at maryland