public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/45917] inaccessible types allowed as template argument in nested-name-specifier
Date: Wed, 06 Oct 2010 21:48:00 -0000	[thread overview]
Message-ID: <20101006214800.JPDCR6SzLn59ncLPjy6633nHdOKi6iqOaZkRhRmvZtQ@z> (raw)
In-Reply-To: <bug-45917-4@http.gcc.gnu.org/bugzilla/>

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |accepts-invalid
            Summary|Friend of friend is allowed |inaccessible types allowed
                   |the access to the private   |as template argument in
                   |type through the template   |nested-name-specifier

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> 2010-10-06 21:48:01 UTC ---
Here's another variation that should fail but doesn't, showing this has nothing
to do with friends:

template<class T>
struct list
{
  struct nested { };
};

class F
{
  struct R { };
};

void f() { list<F::R>::nested n; }

list<F::R>::nested n;


I've changed the summary to reflect this


  parent reply	other threads:[~2010-10-06 21:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06 21:20 [Bug c++/45917] New: Friend of friend is allowed the access to the private type through the template yuri at tsoft dot com
2010-10-06 21:40 ` [Bug c++/45917] " redi at gcc dot gnu.org
2010-10-06 21:48 ` redi at gcc dot gnu.org [this message]
2013-03-14 21:15 ` [Bug c++/45917] inaccessible types allowed as template argument in nested-name-specifier jason at gcc dot gnu.org
2013-03-14 21:40 ` jason at gcc dot gnu.org
2013-03-17  2:40 ` jason at gcc dot gnu.org
2013-03-22 11:18 ` paolo.carlini at oracle dot com
2013-04-01 21:04 ` jason at gcc dot gnu.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=20101006214800.JPDCR6SzLn59ncLPjy6633nHdOKi6iqOaZkRhRmvZtQ@z \
    --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).