public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jwcacces at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/52965] New: c++11 - subclass is private, but g++ ignores access modifier when using auto
Date: Thu, 12 Apr 2012 22:48:00 -0000	[thread overview]
Message-ID: <bug-52965-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 52965
           Summary: c++11 - subclass is private, but g++ ignores access
                    modifier when using auto
    Classification: Unclassified
           Product: gcc
           Version: 4.6.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: jwcacces@yahoo.com


/*
   Is this a bug, that g++ ignores the private access modifier when using "auto
type deduction"?
   Compile with g++ -std=c++0x private_access.cpp
             vs g++ -std=c++0x private_access.cpp -DUSE_AUTO

   This seems similar to bug 52816
*/

class C
{
private:
   class PVT { };
public:
   PVT p() { return PVT(); };
};

int main(int, char*[])
{
   C c;
#ifdef USE_AUTO
   auto p = c.p();          // why does this work (in c++11)
#else
   C::PVT p = c.p();        // but this reports that C::PVT is private?
#endif
   return 0;
};


             reply	other threads:[~2012-04-12 22:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12 22:48 jwcacces at yahoo dot com [this message]
2012-04-12 22:56 ` [Bug c++/52965] " redi at gcc dot gnu.org
2012-11-07 18:39 ` paolo.carlini at oracle dot com
2012-11-07 18:41 ` jwcacces at yahoo dot com
2012-11-07 18:45 ` daniel.kruegler at googlemail dot com
2012-11-07 18:47 ` paolo.carlini at oracle dot com

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=bug-52965-4@http.gcc.gnu.org/bugzilla/ \
    --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).