Path: utzoo!attcan!uunet!mitel!sce!scs!spl1!gargoyle!tank!uwvax!dogie.macc.wisc.edu!csd4.milw.wisc.edu!bionet!agate!shelby!labrea!daemon
From: lane@sumex-aim.stanford.edu (Christopher Lane)
Newsgroups: comp.sys.next
Subject: re: A Few Questions...
Message-ID: <23966@labrea.Stanford.EDU>
Date: 3 Jul 89 18:50:28 GMT
Sender: daemon@labrea.Stanford.EDU
Lines: 16

In article <10374@polya.Stanford.EDU> Ali T. Ozer writes:
>In article <15094@pasteur.Berkeley.EDU> dean@xcssun.Berkeley.EDU () writes:
>>7) Why did lint go away ?
>With an ANSI compiler, you probably won't need it.

If you miss 'lint' as an entity, you can always do something like:

    alias lint "cc -Wall -S -o /dev/null"

and then 'lint program.c' prints the warning messages but produces no binary.
Of course, to redirect output to a file you'll need to redirect stderr, eg. 

    lint program.c >& program.lint

- Christopher
-------