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!cbosgd!ihnp4!mhuxn!mhuxr!ulysses!allegra!mit-eddie!think!harvard!seismo!brl-tgr!gwyn
From: gwyn@brl-tgr.ARPA (Doug Gwyn )
Newsgroups: net.lang.c
Subject: Re: if (p), where p is a pointer - PLEASE READ
Message-ID: <1698@brl-tgr.ARPA>
Date: Tue, 24-Sep-85 17:13:01 EDT
Article-I.D.: brl-tgr.1698
Posted: Tue Sep 24 17:13:01 1985
Date-Received: Sun, 29-Sep-85 04:12:39 EDT
References: <118@mit-hector.UUCP> <2792@sun.uucp> <693@sfmag.UUCP> <268@ccivax.UUCP>
Organization: Ballistic Research Lab
Lines: 12

> By the way, has anybody figured out how to get lint to shut up about
> the return codes for { ,s,f}printf().  I have yet to see a standard definition
> of the return code, but lint keeps giving me "value returned but not used".
> Isn't this just a tramp from doprntf?  I've had one version hand back the
> value of write (and blew away my stack) even though the return code was
> supposed to return a char* (sprintf),  (Seems it didn't like writing a
> 4k message).  This appears to be a good case for using if(sprintf(...)).

This subject has been discussed to death before.  In X3J11 and UNIX
System V, the *printf() functions return a value (# chars transmitted,
or negative on output error).  If you don't wish to test this value
(shame on you), then cast it to (void).