Path: utzoo!utgpu!attcan!uunet!lll-winken!ames!mailrus!bbn!oberon!skat.usc.edu!blarson
From: blarson@skat.usc.edu (Bob Larson)
Newsgroups: comp.lang.c
Subject: Re: Yet Another Lint Foul-up
Message-ID: <14502@oberon.USC.EDU>
Date: 7 Jan 89 06:06:50 GMT
References: <1298@tank.uchicago.edu> <9296@smoke.BRL.MIL>
Sender: news@oberon.USC.EDU
Reply-To: blarson@skat.usc.edu (Bob Larson)
Organization: USC AIS, Los Angeles
Lines: 24

In article <9296@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:

>Here are things that I don't know of any way to keep "lint" from
>unjustly complaining about without deliberately sabotaging it:
>	return from malloc() being used other than as a (char *)
>	functions like exit() that don't return
>	loops that will never terminate but not patently so
>	use of pointer casts

Depending on which version of lint you use, (I've heard it is fixed
in sunos 4.0) you should add:

	varargs functions

At least one version of varargs does not allow any arguments to
the function besides va_alist, and the /*VARARGS0*/ comment does
not shut the lint I use (sunos 3.2) up.  /*VARARGSn*/ n!=0 is not
portable.  (But does have potential use in non-portable lint libraries,
etc.)

Bob Larson	Arpa: Blarson@Ecla.Usc.Edu	blarson@skat.usc.edu
Uucp: {sdcrdcf,cit-vax}!oberon!skat!blarson
Prime mailing list:	info-prime-request%ais1@ecla.usc.edu
			oberon!ais1!info-prime-request