Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!toe.CS.Berkeley.EDU!bostic From: bostic@toe.CS.Berkeley.EDU (Keith Bostic) Newsgroups: comp.os.386bsd.misc Subject: Re: Prototypes Date: 18 Jun 1993 03:48:22 GMT Organization: University of California, Berkeley Lines: 28 Message-ID: <1vrdu6$kn9@agate.berkeley.edu> References: <1vib9c$oe7@agate.berkeley.edu> <37263@castle.ed.ac.uk> <1993Jun14.234920.22813@uvm.edu> <1993Jun17.211337.22353@fcom.cc.utah.edu> NNTP-Posting-Host: toe.cs.berkeley.edu In article <1993Jun17.211337.22353@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes: > >Ok, I've found several subsets of lint-like utilities, and I'm still >looking for a real lint. Gcc actually does a nice job of doing lint style checking. The only drawback is that you have to compile all of the sources at once. While you often can't compile your program plus the C library, prototypes handle this fairly well. There are, admittedly, some set of warnings that lint offered and that gcc does not. The converse is also true, and I hope that in time gcc will improve. Generally, all of the warnings I care about are available from gcc. >There is a real lint on the Tahoe relerease of Net/2; can anyone tell me >what the encumberances on that were, and why it wasn't made publicly >available on the Net/2 PD tape? 4.3BSD-Reno preceded Net/2 by a year, 4.3BSD-Tahoe was two years before 4.3BSD-Reno. There was no Berkeley release that was a "relerease of Net/2". PCC and lint shared about 10,000 lines of code. The reason that they were originally separated into two programs was that lint checking was too slow -- the source code has always significantly overlapped. --keith