From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] C99 and you
Date: Sat, 7 Oct 2006 02:00:18 +1000 [thread overview]
Message-ID: <775b8d190610060900xc05821dpe729122bb0493062@mail.gmail.com> (raw)
In-Reply-To: <45578282b32b388fd2b85b062cbeefac@quanstro.net>
sorry, i misunderstood the absurd standard, again.
brucee
On 10/6/06, erik quanstrom <quanstro@quanstro.net> wrote:
> actually, the switch statement here is a red herring. here's what kenc dislikes:
>
> label: int assignment = 0;
>
> so this will generate an error, too:
>
> void
> main(void)
> {
> begin: int j;
> j = 0;
> if(j>1)
> goto begin;
> exits("");
> }
>
> gcc is also unable to parse this production.
>
> - erik
>
prev parent reply other threads:[~2006-10-06 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 18:32 Skip Tavakkolian
2006-10-06 0:09 ` Bruce Ellis
2006-10-06 1:33 ` Skip Tavakkolian
2006-10-06 8:28 ` Charles Forsyth
2006-10-06 9:51 ` erik quanstrom
2006-10-06 16:00 ` Bruce Ellis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=775b8d190610060900xc05821dpe729122bb0493062@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).