Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!olivea!tymix!cirrusl!ss168!dhesi From: dhesi%cirrusl@oliveb.ATC.olivetti.com (Rahul Dhesi) Newsgroups: comp.bugs.4bsd Subject: Re: lint fails to be my friend Message-ID: <3037@cirrusl.UUCP> Date: 5 Apr 91 01:17:18 GMT References: <1059@eplunix.UUCP> <380@ptcburp.ptcbu.oz.au> <1991Apr04.212837.13505@ima.isc.com> Sender: news@cirrusl.UUCP Organization: Cirrus Logic Inc. Lines: 17 In <1991Apr04.212837.13505@ima.isc.com> suitti@ima.isc.com (Stephen Uitti) writes: Lint belongs in the compiler, anyway. Turbo C generates considerably more complete checking during compilation than 'lint' ever did, at over 3,000 lines per minute on a 7 MHz 8088 Pc/xt. Turbo C does good intrafile checking. However, lint really shines when it does interfile checking. Until we get smarter (and slower) linkers, we will have to rely upon lint and similar programs for this. A compiler that did interfile checking would essentially be a linker. Properly created headers can help the compiler do some of what lint does, but then who checks the headers? Lint, of course. -- Rahul Dhesi UUCP: oliveb!cirrusl!dhesi