Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site codas.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!akguc!codas!mikel
From: mikel@codas.UUCP (Mikel Manitius)
Newsgroups: net.lang.c
Subject: Re: if (p), where p is a pointer - PLEASE READ
Message-ID: <157@codas.UUCP>
Date: Sat, 5-Oct-85 23:15:26 EDT
Article-I.D.: codas.157
Posted: Sat Oct  5 23:15:26 1985
Date-Received: Mon, 7-Oct-85 04:06:10 EDT
References: <118@mit-hector.UUCP> <2792@sun.uucp> <693@sfmag.UUCP> <268@ccivax.UUCP> <1698@brl-tgr.ARPA>
Organization: AT&T Information Systems (SDSS) - Orlando
Lines: 23

> > 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).

I don't have any trouble with lint,
It never complains,
Then again, I never use then damn beast!
-- 
                                        =======
     Mikel Manitius                   ==----=====    AT&T
     (305) 869-2462 RNX: 755         ==------=====   Information Systems 
     ...{akguc|ihnp4}!codas!mikel    ===----======   SDSS Regional Support
     ...attmail!mmanitius             ===========    Altamonte Springs, FL
     My opinions are my own.            =======