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!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!brl-tgr!gwyn
From: gwyn@brl-tgr.ARPA (Doug Gwyn <gwyn>)
Newsgroups: net.lang.c
Subject: Re: casts to (void)
Message-ID: <413@brl-tgr.ARPA>
Date: Sun, 4-Aug-85 08:07:54 EDT
Article-I.D.: brl-tgr.413
Posted: Sun Aug  4 08:07:54 1985
Date-Received: Tue, 6-Aug-85 07:48:21 EDT
References: <11@brl-tgr.ARPA> <1288@eagle.UUCP> <15908@watmath.UUCP> <116@rtp47.UUCP> <1096@diku.UUCP>
Organization: Ballistic Research Lab
Lines: 10

The people proposing ways of making
	(void)printf( ... );
easier to enter into their code are missing the point of lint's
complaint!

The printf() function CAN FAIL and if you don't test for it,
Murphy says that it WILL fail, under the worst possible
circumstances (e.g., while updating YOUR pay record).
Instead of looking for ways to avoid testing printf return,
how about making your code more robust.