public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/12479] System header should not cause -pedantic to error about "extra `;'"
Date: Wed, 01 Oct 2003 17:51:00 -0000 [thread overview]
Message-ID: <20031001175110.383.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031001174228.12479.levon@movementarian.org>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12479
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |critical
Keywords| |diagnostic
Summary|superfluous colon with - |System header should not
|pedantic gives error not |cause -pedantic to error
|present w/o -pedantic |about "extra `;'"
|(mozilla build failure) |
Target Milestone|--- |3.4
------- Additional Comments From pinskia at gcc dot gnu dot org 2003-10-01 17:51 -------
I am not the one who is going to make the discussion here but the error message is correct that
the semicolon is extra (since 3.4 is more compliant this happens).
next prev parent reply other threads:[~2003-10-01 17:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 17:42 [Bug c++/12479] New: superfluous colon with -pedantic gives error not present w/o -pedantic (mozilla build failure) levon at movementarian dot org
2003-10-01 17:46 ` [Bug c++/12479] " pinskia at gcc dot gnu dot org
2003-10-01 17:51 ` pinskia at gcc dot gnu dot org [this message]
2003-10-01 17:58 ` [Bug c++/12479] System header should not cause -pedantic to error about "extra `;'" levon at movementarian dot org
2003-10-01 18:01 ` pinskia at gcc dot gnu dot org
2003-10-01 18:06 ` levon at movementarian dot org
2003-10-01 18:09 ` pinskia at gcc dot gnu dot org
2003-10-01 18:19 ` levon at movementarian dot org
2003-10-01 18:31 ` zack at gcc dot gnu dot org
2003-10-01 18:44 ` gdr at integrable-solutions dot net
2003-10-01 18:46 ` gdr at integrable-solutions dot net
2003-10-01 18:57 ` zack at gcc dot gnu dot org
2003-10-01 19:19 ` gdr at integrable-solutions dot net
2003-10-01 19:46 ` levon at movementarian dot org
2003-10-01 19:53 ` gdr at integrable-solutions dot net
2003-10-01 19:55 ` gdr at integrable-solutions dot net
2003-10-02 1:27 ` levon at movementarian dot org
2003-10-02 1:59 ` gdr at integrable-solutions dot net
2003-11-30 8:36 ` [Bug c++/12479] [3.4 only] " pinskia at gcc dot gnu dot org
2003-12-20 4:12 ` pinskia at gcc dot gnu dot org
2003-12-22 9:18 ` mmitchel at gcc dot gnu dot org
2003-12-22 19:21 ` cvs-commit at gcc dot gnu dot org
2003-12-22 19:26 ` mmitchel at gcc dot gnu dot org
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=20031001175110.383.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).