Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!husc6!spdcc!tauxersvilli!alphalpha!nazgul From: nazgul@alphalpha.com (Kee Hinckley) Newsgroups: comp.sys.apollo Subject: Re: How ANSI is Apollo's cc 6.7 (SR 10.2) Message-ID: <1990Sep13.153623.15705@alphalpha.com> Date: 13 Sep 90 15:36:23 GMT References: <848@usage.csd.unsw.oz.au> Organization: asi Lines: 22 In article <848@usage.csd.unsw.oz.au> cameron@spectrum.cs.unsw.oz.au (Cameron Simpson) writes: >Prototypes are a great help. But lint does much more than this. I totally agree that lint should work on Apollo header files, however... >It catches unportable code. It catches uninitialised and unused variables. >And so on. It would be nice if the compiler caught some of these. The Apollo compiler catches both of these, there's a flag for unportable code, uninit and unused variables are caught normally. Furthermore you can turn on the -info flags and catch more things than you ever wanted to know. -- Alphalpha Software, Inc. | motif-request@alphalpha.com nazgul@alphalpha.com |----------------------------------- 617/646-7703 (voice/fax) | Proline BBS: 617/641-3722 I'm not sure which upsets me more; that people are so unwilling to accept responsibility for their own actions, or that they are so eager to regulate everyone else's.