From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Jamie Lokier <jamie@shareable.org>
Cc: gcc@gcc.gnu.org
Subject: Re: C99 parsing error?
Date: Sun, 18 May 2003 14:19:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.53.0305181432170.10922@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <20030518082723.GA6350@mail.jlokier.co.uk>
On Sun, 18 May 2003, Jamie Lokier wrote:
> Is it really not permitted to write this in C99?:
>
> while (--length >= 0)
> {
> loop:
> int byte = *data++;
>
> GCC 3.2.2 reports: parse error before "int"
> If I replace "loop:" with "loop:;", it's fine.
> Perhaps GCC is correct to reject this, but it is surprising.
A compound statement is a sequence of statements and declarations; only
statements can have labels; see 6.8.1 and 6.8.2. The existing GCC
extension of attributes on labels means that we don't accept labels on
declarations as an extension either.
--
Joseph S. Myers
jsm28@cam.ac.uk
next prev parent reply other threads:[~2003-05-18 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-18 8:52 Jamie Lokier
2003-05-18 10:27 ` Neil Booth
2003-05-18 14:19 ` Joseph S. Myers [this message]
2003-05-18 15:22 ` Falk Hueffner
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=Pine.LNX.4.53.0305181432170.10922@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc@gcc.gnu.org \
--cc=jamie@shareable.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).