Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!decwrl!shelby!labrea!daemon
From: lane@sumex-aim.stanford.edu (Christopher Lane)
Newsgroups: comp.sys.next
Subject: lint
Message-ID: <23970@labrea.Stanford.EDU>
Date: 5 Jul 89 18:27:37 GMT
Sender: daemon@labrea.Stanford.EDU
Lines: 10

Clearly, 'cc -Wall' != 'lint' as it doesn't check argument use consistency
either nor report functions whose values aren't used, etc.

I'd like to see 'lint' be a special case of the compiler (possibly under
separate name) and do both what 'cc -Wall' and real 'lint' do as well as any
other questionable code checks that can be done.

The alias of 'cc -Wall ...' should handle multiple source files if 'cc' does.

- Christopher