Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!linus!philabs!cmcl2!seismo!brl-tgr!tgr!Purtill@MIT-MULTICS.ARPA
From: Purtill@MIT-MULTICS.ARPA (Mark Purtill)
Newsgroups: net.lang.c
Subject: Re: casts to void
Message-ID: <503@brl-tgr.ARPA>
Date: Wed, 7-Aug-85 21:57:04 EDT
Article-I.D.: brl-tgr.503
Posted: Wed Aug  7 21:57:04 1985
Date-Received: Sat, 10-Aug-85 23:57:35 EDT
Sender: news@brl-tgr.ARPA
Lines: 14


1. Who says you're on UNIX anyway?  UNIX may have uniform treatment of
I/O, but not all systems do, and some of them have C.

2. I'll conceed the point that usually you should do something when
printf fails.  However, usually that is print an error message (or fail
to do so) and die.  I claim the system should have some way of doing
that for me.  Perhaps there should be an io error signal which has
default action of doing nothing (where-upon the routine in question
returns an error value) but can be reset to print an error and die.

       Mark
^.-.^  Purtill at MIT-MULTICS.ARPA    **Insert favorite disclaimer here**
(("))  2-032 MIT Cambrige MA 02139