home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!sgigate!sgi!igor!kevin
- From: kevin@tamri.com (Kevin Dalley)
- Newsgroups: comp.sys.sgi.bugs
- Subject: Re: lint doesn't recognize '#' ansi operator
- Message-ID: <KEVIN.92Dec17190638@polkacide.tamri.com>
- Date: 18 Dec 92 03:06:40 GMT
- References: <1992Dec17.102241.12183@itnsg1.cineca.it>
- <DSG.92Dec17085443@blackbird.mitre.org>
- Sender: kevin@igor.tamri.com (Kevin Dalley)
- Reply-To: kevin@tamri.com
- Organization: TOSHIBA America MRI, South San Francisco, CA
- Lines: 28
- In-Reply-To: dsg@blackbird.mitre.org's message of 17 Dec 92 13:54:43 GMT
-
- In article <DSG.92Dec17085443@blackbird.mitre.org>
- dsg@blackbird.mitre.org (David S. Goldberg) writes:
-
- > Nntp-Posting-Host: blackbird.mitre.org
-
-
- >>>>>> In article <1992Dec17.102241.12183@itnsg1.cineca.it>,
- >>>>>> root@itnsg1.cineca.it (Valter Cavecchia) writes:
-
- >Valter> This is not a bug, lint doesn't recognize the # ansi
- >Valter> "tokenizer" because it actually uses "cpp" and not "acpp"
- >Valter> (lint ignores -ansi keywords). This is really annoying... Is
- >Valter> there any fix to this?
-
- > I don't have a true fix, but I've been annoyed by this too. My
- > solution (I call it a kludge) has been to preprocess the file with
- > acpp, redirecting to another file, and then running lint on that
- > second file. It's not as nice as having lint use acpp directly
- > because line numbers don't always match up, but it does help somewhat.
-
- Another solution is to "gcc -Wall". Through in a few other warnings
- if you so desire. gcc gives substantially better warning messages
- than either SGI's "cc -fullwarn" or lint.
-
- --
- Kevin Dalley
- Toshiba America MRI, Inc.
- kevin@tamri.com
-