From: Jason Merrill <jason@redhat.com>
To: Kai Tietz <ktietz70@googlemail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch c++]:PR/15774 - Conflicting function decls not diagnosed (this time really for 15774)
Date: Sun, 26 Dec 2010 18:19:00 -0000 [thread overview]
Message-ID: <4D167220.9080404@redhat.com> (raw)
In-Reply-To: <AANLkTinzaGiLOM+k2QKknmNEPJEt1Y=CSREUecP4ADsJ@mail.gmail.com>
On 12/25/2010 11:00 AM, Kai Tietz wrote:
> Hmm, not sure. Case 2 is simply ill-formed, but doesn't cause wrong
> code. But case 1 in fact can produce wrong code. See as expample
I agree that we should reject it, I'm just saying we should reject it in
a different function. :)
Jason
prev parent reply other threads:[~2010-12-25 22:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinGynF-v_UmCCNJrH7GEOcFQDC-5RHc4XbK+Fr2@mail.gmail.com>
2010-12-22 23:48 ` Kai Tietz
2010-12-23 12:33 ` Kai Tietz
2010-12-25 6:27 ` Jason Merrill
2010-12-25 6:27 ` Kai Tietz
2010-12-25 16:00 ` Kai Tietz
2011-01-04 3:41 ` Dave Korn
2011-01-04 6:09 ` Dave Korn
2010-12-26 9:50 ` Jason Merrill
2010-12-26 16:56 ` Kai Tietz
2010-12-26 18:19 ` Jason Merrill [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=4D167220.9080404@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ktietz70@googlemail.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).