Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!mcvax!botter!tjalk!rblieva
From: rblieva@cs.vu.nl (Roemer b Lievaart)
Newsgroups: comp.lang.c
Subject: Re: goto's and switch statements -- mild proposal
Message-ID: <869@tjalk.cs.vu.nl>
Date: Wed, 2-Sep-87 10:17:38 EDT
Article-I.D.: tjalk.869
Posted: Wed Sep  2 10:17:38 1987
Date-Received: Sat, 5-Sep-87 09:43:40 EDT
References: <855@tjalk.cs.vu.nl> <2683@hoptoad.uucp> <916@haddock.ISC.COM> <929@haddock.ISC.COM> <867@mcgill-vision.UUCP>
Reply-To: rblieva@cs.vu.nl (Roemer B. Lievaart)
Organization: VU Informatica, Amsterdam
Lines: 19

In article <867@mcgill-vision.UUCP> mouse@mcgill-vision.UUCP (der Mouse) writes:
>
>I agree 155%.  Any warning should have a means to turn it off.  (For
>most current warnings, which tend to be type clashes, this means is
>provided: it's called a cast.)
>
Oh yeah? How about the message I get for EVERY casted malloc or realloc:

:: somefile.c(007): warning: possible pointer alignment problem

Can't shut lint up about that.

		--Roemer (pronounced "Rumo(u)r")

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!
[ OK, I meant another way than indeed using the values.
  I just don't need them (always)! ]