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++/27227] [4.0 Regression] rejects valid code with some extern "C"
Date: Sat, 15 Jul 2006 10:28:00 -0000 [thread overview]
Message-ID: <20060715102757.28924.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27227-6528@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from pinskia at gcc dot gnu dot org 2006-07-15 10:27 -------
(In reply to comment #9)
> So apparently this is invalid code. However, I feel very strongly that a point
> release of GCC should *not* introduce a new error - Mark, please modify the
> patch applied to the 4.1 branch in a way to allow this code.
Why? It is better to reject invalid code even than keeping backwards
compatiblity.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27227
next prev parent reply other threads:[~2006-07-15 10:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 19:36 [Bug c++/27227] New: [4.0/4.1/4.2 " pinskia at gcc dot gnu dot org
2006-04-22 20:28 ` [Bug c++/27227] " pinskia at gcc dot gnu dot org
2006-05-26 15:28 ` bangerth at dealii dot org
2006-06-04 18:28 ` mmitchel at gcc dot gnu dot org
2006-06-14 4:19 ` mmitchel at gcc dot gnu dot org
2006-06-14 17:48 ` mmitchel at gcc dot gnu dot org
2006-06-14 17:51 ` [Bug c++/27227] [4.0/4.1 " mmitchel at gcc dot gnu dot org
2006-06-14 19:17 ` mmitchel at gcc dot gnu dot org
2006-06-14 19:19 ` [Bug c++/27227] [4.0 " mmitchel at gcc dot gnu dot org
2006-06-15 16:19 ` sje at cup dot hp dot com
2006-06-15 16:50 ` pinskia at gcc dot gnu dot org
2006-06-30 18:03 ` ben at decadentplace dot org dot uk
2006-07-15 10:18 ` tbm at cyrius dot com
2006-07-15 10:28 ` pinskia at gcc dot gnu dot org [this message]
2006-07-15 10:41 ` pinskia at gcc dot gnu dot org
2006-07-15 10:42 ` tbm at cyrius dot com
2006-07-15 10:48 ` pinskia at gcc dot gnu dot org
2006-07-15 10:58 ` tbm at cyrius dot com
2006-07-19 6:00 ` mark at codesourcery dot com
2007-02-03 16:52 ` gdr 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=20060715102757.28924.qmail@sourceware.org \
--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).