public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nathan at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/18100] [3.4/4.0 regression] template member with same name as class not rejected
Date: Wed, 08 Dec 2004 09:05:00 -0000	[thread overview]
Message-ID: <20041208090524.2681.qmail@sourceware.org> (raw)
In-Reply-To: <20041021205738.18100.reichelt@gcc.gnu.org>


------- Additional Comments From nathan at codesourcery dot com  2004-12-08 09:05 -------
Subject: Re:  [3.4/4.0 regression] template member with same
 name as class not rejected

Mark Mitchell wrote:
> lerdsuwa at gcc dot gnu dot org wrote:
> 
>> ------- Additional Comments From lerdsuwa at gcc dot gnu dot org  
>> 2004-12-07 12:34 -------
>> Patch for 3.4 is submitted:
>>   http://gcc.gnu.org/ml/gcc-patches/2004-12/msg00450.html
> 
> 
> (There is a typo in your test case; you meant "nested" instead of "ested".)
> 
> That aside, I'm concerned that this fix might cause something else to 
> break, and, given that the problem is only a missed diagnostic, I do not 
> think that's a good tradeoff.  Nathan, what do you think?

Does this allow templated ctors? If those are still permitted, I think
the patch is ok.

(IMO it would be simpler to check those things
that are allowed to have the same name, rather than all those that aren't.
That would not be a sensible 3.4 change though.)



nathan



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18100


  parent reply	other threads:[~2004-12-08  9:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-21 20:57 [Bug c++/18100] New: " reichelt at gcc dot gnu dot org
2004-10-21 21:02 ` [Bug c++/18100] " pinskia at gcc dot gnu dot org
2004-11-01  0:46 ` mmitchel at gcc dot gnu dot org
2004-11-16 10:05 ` reichelt at gcc dot gnu dot org
2004-11-16 20:35 ` reichelt at gcc dot gnu dot org
2004-11-16 21:08 ` reichelt at gcc dot gnu dot org
2004-12-04  7:34 ` lerdsuwa at gcc dot gnu dot org
2004-12-06 10:26 ` lerdsuwa at gcc dot gnu dot org
2004-12-07 12:35 ` lerdsuwa at gcc dot gnu dot org
2004-12-08  5:48 ` mark at codesourcery dot com
2004-12-08  9:05 ` nathan at codesourcery dot com [this message]
2004-12-08 10:13 ` lerdsuwa at gcc dot gnu dot org
2004-12-08 10:25 ` cvs-commit at gcc dot gnu dot org
2004-12-08 10:54 ` cvs-commit at gcc dot gnu dot org
2004-12-08 10:56 ` lerdsuwa 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=20041208090524.2681.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).