Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!batcomputer!riley
From: riley@batcomputer.tn.cornell.edu (Daniel S. Riley)
Newsgroups: comp.sys.amiga
Subject: Re: Why I don't use the newer Lattice compilers
Message-ID: <7746@batcomputer.tn.cornell.edu>
Date: 14 Apr 89 15:03:49 GMT
References: <12652@haddock.ima.isc.com> <5236@cs.Buffalo.EDU> <5239@cs.Buffalo.EDU> <11495@s.ms.uky.edu> <11499@s.ms.uky.edu>
Reply-To: riley@tcgould.tn.cornell.edu (Daniel S. Riley)
Distribution: na
Organization: Cornell Theory Center, Cornell University, Ithaca NY
Lines: 24

synopsis:  does the Lattice C compiler generate too many warnings?

In article <11499@s.ms.uky.edu> sean@ms.uky.edu (Sean Casey) writes:
>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.

Actually, not declaraing main() as void is not a warning.  If you don't
include <stdlib.h>, it doesn't generate any messages.  If you include
<stdlib.h>, it generates an "external item attribute mismatch" *error*.
This is arguably a bug in <stdlib.h>, which declares main() as type
void, not a problem with the compiler itself.

>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.

Lattice lets you turn off *individual* warning messages.  So you can
suppress just the ones you don't like, and still get the rest of the
warnings.

-Dan Riley (riley@tcgould.tn.cornell.edu, cornell!batcomputer!riley)
-Wilson Lab, Cornell U.