Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: goto's and switch statements -- mild proposal
Message-ID: <6395@brl-smoke.ARPA>
Date: Wed, 31-Dec-69 18:59:59 EDT
Article-I.D.: brl-smok.6395
Posted: Wed Dec 31 18:59:59 1969
Date-Received: Sat, 5-Sep-87 12:18:47 EDT
References: <855@tjalk.cs.vu.nl> <2683@hoptoad.uucp> <916@haddock.ISC.COM> <929@haddock.ISC.COM> <867@mcgill-vision.UUCP> <869@tjalk.cs.vu.nl>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 8

In article <869@tjalk.cs.vu.nl> rblieva@cs.vu.nl (Roemer B. Lievaart) writes:
>BTW. Does anybody know how to stop lint complaining about functions
>returning values wich are always/sometimes ignored? I get one for every
>time I use sprintf, fclose, strcpy and quite a few others!

Traditionally, one just applies a (void) cast to the function result.
By the way, if you're not testing fclose() return value, you're risking
not detecting a write error.  fclose() can cause a write.