Path: utzoo!attcan!uunet!nih-csl!elsie!ado
From: ado@elsie.UUCP (Arthur David Olson)
Newsgroups: comp.lang.c
Subject: Re: Yet Another Lint Foul-up
Message-ID: <8605@elsie.UUCP>
Date: 7 Jan 89 17:58:24 GMT
References: <1298@tank.uchicago.edu> <9296@smoke.BRL.MIL>
Organization: NIH-LEC, Bethesda, MD
Lines: 33

In article <9296@smoke.BRL.MIL>, gwyn@smoke.BRL.MIL (Doug Gwyn...) writes:
> 
> Ignoring certain "lint" output that could have been avoided is
> one bad habit.  There is another one in the opposite direction:
> Some C programmers use tricks to "shut lint up" rather than
> fixing a genuinely non-portable aspect of their code.

Indeed.  One local addition to "lint" is illustrated below:

	Script started on Sat Jan  7 12:51:10 1989
	elmer$ cat try.c
	/*LINTLIBRARY*/

	/*ARGSUSED*/
	int
	func(i)
	{
		return i;
	}
	elmer$ lint try.c
	try.c:
	try.c(8): warning: function func has superfluous ARGSUSED
	elmer$ exit

	script done on Sat Jan  7 12:51:27 1989

It surprises me how much off-the-net code produces "superfluous ARGSUSED"
messages; some C programmers just uniformly use tricks, whether they're
needed or not.
-- 
Wolf is a registered trademark of the boy who cried it.
-- 
	Arthur David Olson    ado@ncifcrf.gov    ADO is a trademark of Ampex.