Path: csiph.com!news.swapon.de!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Ike Naar <ike@iceland.freeshell.org>
Newsgroups: comp.lang.c
Subject: Re: gcc needs a curly bracket matching/counting function
Date: Tue, 20 Dec 2016 22:00:47 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 15
Message-ID: <slrn3vfso5jaiu.ob1.ike@iceland.freeshell.org>
References: <o3a201$nfs$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 20 Dec 2016 22:00:47 -0000 (UTC)
Injection-Info: mx02.eternal-september.org; posting-host="93f89ffefe2bd4139b5735864a1e49a4"; logging-data="2286"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/9VtOX4HGC1PuG7EWWxxZA"
User-Agent: slrn/0.9.9p1 (NetBSD)
Cancel-Lock: sha1:Isu/WSZYBMnd8qvQlz1MOQZgVK0=
Xref: csiph.com comp.lang.c:99941

On 2016-12-20, DFS <nospam@dfs.com> wrote:
> This would potentially help a lot.
>
> I had ONE extraneous closing curly bracket } in place in a function, and 
> gcc -Wall threw 60+ warnings and errors.
>
> Took me several minutes to find it, and once it was removed I got a 100% 
> clean compile

What's the problem? It took you a few minutes this time, and it
will probably take you a few seconds when it happens again because
you have learned from the previous experience.

It's surprising that (see elsethread) so much commotion is caused by
something as futile as an unmatched curly brace.