Path: utzoo!attcan!uunet!snorkelwacker!usc!zaphod.mps.ohio-state.edu!uwm.edu!bionet!agate!shelby!daemon
From: lane@sumex-aim.stanford.edu (Christopher Lane)
Newsgroups: comp.sys.next
Subject: re: Debuggers for NeXT (plus lint)
Message-ID: <2208@shelby.Stanford.EDU>
Date: 12 Jul 90 18:25:14 GMT
Sender: daemon@shelby.Stanford.EDU
Lines: 23

In <GUMBY.90Jul11194203@Cygnus.COM>, gumby@cygnus.com writes:
> ...
> Have you tried the -Wall option to the C compiler?  No, it ain't lint,
> but it enables warning on almost anything that might trip you up.

We use the following 'csh' script, stored as '/usr/local/bin/lint'
(a variant of which I posted long ago as an alias):

    #! /bin/csh
    set program = $0
    cc -Wall -D$program:t -S -o /dev/null ${argv[1-]}
    unset program

This runs 'cc' with no output and skips the assembly process--useful for a
quick syntax check between edits.  You can also pass it other 'cc' arguments
(eg -I to affect where it finds include directories).  And, assuming you call
it 'lint', constructs like '#ifndef lint' in code should work right.

But, it isn't the same as having 'real' lint, I still occasionally sneak over
to the SparcStation to 'lint' (non-Objective) C code that I'm working on.

- Christopher
-------