Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83 (MC840302); site diku.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!mcvax!diku!kimcm
From: kimcm@diku.UUCP (Kim Christian Madsen)
Newsgroups: net.lang.c
Subject: Re: casts to (void)
Message-ID: <1096@diku.UUCP>
Date: Sat, 3-Aug-85 19:11:24 EDT
Article-I.D.: diku.1096
Posted: Sat Aug  3 19:11:24 1985
Date-Received: Sun, 4-Aug-85 07:14:53 EDT
References: <11@brl-tgr.ARPA> <1288@eagle.UUCP> <15908@watmath.UUCP> <116@rtp47.UUCP>
Reply-To: kimcm@diku.UUCP (Kim Christian Madsen)
Organization: DIKU, U of Copenhagen, DK
Lines: 25
Keywords: lint

In article <116@rtp47.UUCP> meissner@rtp47.UUCP (Michael Meissner) writes:
>
>Whenever I use things like printf with lint, I define things like:
>
>	#define	Printf	(void) printf
>	#define	Fputs	(void) fputs
>
>		/* ... */
>
>	Printf("Hello World!\n");
>
>Which translates to:
>
>	(void) printf("Hello World!\n");
>
>Thus lint is kept happy, and my program is not cluttered up with casts to void.

That's a mediocre solution, it shouldn't be necessary lint should know the
set of standard functions which results needn't be used. It's not accept-
able to either put (void) in front of printf(), scanf(), ...etc. or make
defines like "#define Printf (void) printf".

						Regards
						Kim Chr. Madsen
					a.k.a.	kimcm@diku.uucp