public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/13830] Invalid covariant type for identical type, friend related
Date: Sat, 24 Apr 2004 08:26:00 -0000	[thread overview]
Message-ID: <20040424053005.12747.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040123120418.13830.mattyt-bugzilla@tpg.com.au>


------- Additional Comments From bangerth at dealii dot org  2004-04-24 05:30 -------
Of course it has to do with friend classes. In the original code, 
in the friend declaration we look up X, don't find anything, and 
inject this name in the global namespace. When we later come back 
in the derived class, we see the friend declaration again, but this 
time we seem to know that the base class also has a member class X and 
think that the friend declaration corresponded to this. 
 
If you add a global class X to the snippet, then the name injection doesn't 
have to happen, and we seem to always believe that the friend declaration 
corresponds to the global class X. 
 
W. 

-- 


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


  parent reply	other threads:[~2004-04-24  5:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23 12:04 [Bug c++/13830] New: Invalid covariant type for identical type mattyt-bugzilla at tpg dot com dot au
2004-01-23 16:26 ` [Bug c++/13830] " bangerth at dealii dot org
2004-04-23 21:07 ` [Bug c++/13830] Invalid covariant type for identical type, friend related pinskia at gcc dot gnu dot org
2004-04-24  8:26 ` bangerth at dealii dot org [this message]
2004-10-13 15:17 ` lerdsuwa at gcc dot gnu dot org
2004-12-28 15:29 ` lerdsuwa at gcc dot gnu dot org
2005-03-14 14:40 ` lerdsuwa at gcc dot gnu dot org
2005-05-22 11:43 ` lerdsuwa at gcc dot gnu dot org
2005-05-22 14:06 ` pinskia 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=20040424053005.12747.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).