Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.unix.programmer
Subject: Re: Lint woes
Message-ID: <8038@auspex.auspex.com>
Date: 26 May 91 19:03:21 GMT
Article-I.D.: auspex.8038
References: <1991May21.033422.21445@kfw.COM> <7992@auspex.auspex.com> <4405@inews.intel.com>
Organization: Auspex Systems, Santa Clara
Lines: 14

>>Most, if not all, "lint"s are basically modified versions of C
>>compilers, and most, if not all, haven't been sufficiently modified that
>>they can catch that problem.
>
>Most, if not all, are hardly being modified at all, any more.

Definitely not all; System V Release 4 includes a new "lint" that
allegedly handles ANSI C and has a bunch of other new stuff in it
(including checks of the format string of "printf"-like routines against
the argument list - i.e., they finally got around to implementing
/*PRINTFLIKE*/ - as well as similar checks for "scanf"-like routines
*and* a /*LINTED*/ construct that can help you shut "lint" up about some
things - as I remember, it accepts something like /*TRUSTME*/ or some
other amusing keyword as a synonym for /*LINTED*/).