Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail
From: Ralph Spitzner <rasp@spitzner.org>
Newsgroups: comp.lang.c
Subject: Re: What good C compilers are available for Linux/UNIX?
Date: Wed, 18 May 2011 11:35:01 +0200
Organization: Hanswurst & Kaspar Hauser Ltd.
Lines: 29
Message-ID: <5fgca8-e1q.ln1@spitzner.org>
References: <8eb9284bb6299673802a767c810c1395@msgid.frell.theremailer.net> <8lsaa8-o9.ln1@wilbur.25thandClement.com> <iquhne$tm$1@dont-email.me>
NNTP-Posting-Host: mK+LqTsuhwQzkg6IUpj9FQ.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:2.0.1) Gecko/20110511 Firefox/4.0.1 SeaMonkey/2.1
X-Notice: Filtered by postfilter v. 0.8.2
Xref: x330-a1.tempe.blueboxinc.net comp.lang.c:4216

August Karlstrom wrote:

> Clang give excellent error messages. For example, try to compile this
> program with gcc and then with clang and see for yourself:
>
> struct t {
> int n;
> }
>
> int main(void)
> {
> return 0;
> }
>
>
> /August
>


Well, gcc tels you you're missing something _before_
the declaration of main.
For which I don't need a compiler because it's clear to see
what's wrong.

struct somename { sometype somename; ); [semicolon here]

So perhaps actually _reading_ books was worth it :-P

	-rasp