From: "Craig J Copi" <copi@erebus.phys.cwru.edu>
To: egcs@cygnus.com
Subject: Parsing of switch statement
Date: Wed, 10 Dec 1997 12:02:00 -0000 [thread overview]
Message-ID: <199712102001.PAA29621@erebus.phys.cwru.edu> (raw)
Recently I have encountered some code that contains an empty case
statement at the end of a switch (see example below). The code compiles under
gcc but not under g++. I get the error
test.c: In function `int main (int, char **)':
test.c:9: parse error before `}'
If I put a ';' after the case 0 : it will also compile under g++. I've tried
this on sparc-sun-solaris2.5.1 with egcs-2.90.21 971202 (egcs-1.00 release)
and egcs-2.91.02 971206 (gcc-2.8.0); both give the same results. Is this the
correct behavior? Does the C++ spec require this?
Craig
Here is the simple test
#include <stdio.h>
int main (int argc, char *argv[])
{
int i=1;
switch (i) {
case 1 : printf ("1 ");
case 0 : /* a ';' is needed here to compile with g++ */
}
printf ("\n");
return 0;
}
next reply other threads:[~1997-12-10 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-10 12:02 Craig J Copi [this message]
1997-12-10 15:53 ` Joe Buck
1997-12-11 5:32 ` Oleg Krivosheev
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=199712102001.PAA29621@erebus.phys.cwru.edu \
--to=copi@erebus.phys.cwru.edu \
--cc=egcs@cygnus.com \
/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).