Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!ukma!sean
From: sean@ms.uky.edu (Sean Casey)
Newsgroups: comp.sys.amiga
Subject: Re: Why I don't use the newer Lattice compilers
Keywords: zoo zuu  moo muu help
Message-ID: <11499@s.ms.uky.edu>
Date: 14 Apr 89 05:30:22 GMT
References: <12652@haddock.ima.isc.com> <5236@cs.Buffalo.EDU> <5239@cs.Buffalo.EDU> <11495@s.ms.uky.edu>
Reply-To: sean@ms.uky.edu (Sean Casey)
Distribution: na
Organization: The Leaning Tower of Patterson Office @ The Univ. of KY
Lines: 23

In article <11495@s.ms.uky.edu> jgary@ms.uky.edu (James E. Gary) writes:
>Interesting. You are willing to give up a global optimizer, a symbolic
>debugger, an integrated editor, a make utlity, precompiled header files,
>pragmas for library calls, support for making resident programs, support
>for getting traces from abending programs, a profiler, etc. all because
>you don't want to see warning messages? 

Warning messages are one thing. Excessive warning messages are another.

Not declaring main() as void is perfectly legal C, and shouldn't
generate warning messages. If a compiler spat that out at me, I'd want
my money back.

Turning off warning messages is not a solution, because "normal" warning
messages (such as equivalancing a pointer to int) are useful. I think
the original poster was justified in saying that he wanted a compiler,
not lint.

Sean
-- 
***  Sean Casey                         sean@ms.uky.edu, sean@ukma.bitnet
***  What, me worry?                    {backbone|rutgers|uunet}!ukma!sean
***  ``A computer network should be considerably faster than a slug.'' -Me