Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!aplcen!haven!mimsy!mojo!russotto
From: russotto@eng.umd.edu (Matthew T. Russotto)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Lint for Think C
Message-ID: <1990Aug17.141924.7957@eng.umd.edu>
Date: 17 Aug 90 14:19:24 GMT
References: <1990Aug5.195935.16500@phri.nyu.edu> <1990Aug16.213123.14437@d.cs.okstate.edu> <6529@helios.ee.lbl.gov>
Sender: news@eng.umd.edu (The News System)
Organization: College of Engineering, Maryversity of Uniland, College Park
Lines: 15

In article <6529@helios.ee.lbl.gov> beard@ux5.lbl.gov (Patrick C Beard) writes:
>
>Lint should be part of the compiler, not a separate pass.  MPW C++ is the
>closest thing I've seen.  It's even good to pass regular C code through it
>just to get that extra level of type checking (that's why it's so slow :)).

But what about those of us who don't LIKE lint?  If I wanted a nice, safe
language that whined when I assign chars to unsigned chars, or complained
when I passed a pointer to a routine expecting an integer (SetWRefCon,
anyone),  or complained when the end of a function was not reached, etc,etc,
I'd use Pascal or something.

--
Matthew T. Russotto	russotto@eng.umd.edu	russotto@wam.umd.edu
][, ][+, ///, ///+, //e, //c, IIGS, //c+ --- Any questions?