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!gwyn@BRL.ARPA
From: gwyn@BRL.ARPA (VLD/VMB)
Newsgroups: net.lang.c
Subject: Re:  casts to void
Message-ID: <485@brl-tgr.ARPA>
Date: Tue, 6-Aug-85 21:10:09 EDT
Article-I.D.: brl-tgr.485
Posted: Tue Aug  6 21:10:09 1985
Date-Received: Sun, 11-Aug-85 00:16:51 EDT
Sender: news@brl-tgr.ARPA
Lines: 9

No, I want you to do something INTELLIGENT when a write operation fails.
Properly-designed tools are NOT necessarily writing to a terminal
with their printf()s; they may be writing into a disk file on a
full filesystem or onto a communication link or a number of other
possibilities.  By assuming that your program is always being run
in its simplest mode with a human attendant, you are providing your
users with UNFRIENDLY software that will sooner or later cause them
unnecessary grief.  UNIX has enough crappy code already.  Let's
make OUR code better!