public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joerg at netbsd dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55361] New: Access control in templates only happens when instantiating a method
Date: Fri, 16 Nov 2012 22:25:00 -0000	[thread overview]
Message-ID: <bug-55361-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 55361
           Summary: Access control in templates only happens when
                    instantiating a method
    Classification: Unclassified
           Product: gcc
           Version: 4.7.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: joerg@netbsd.org


Consider the following example:

class C
{
    bool blocked;
};
template < class > struct F
{
    void operator* ()
    {
        C a;
        a.blocked;
    }
};

int main() {
F<int> x;
}

The operator is violating the access specifications of C, but this isn't
detected until it is actually used. Nothing in it depends on the template
though, so this check should happen earlier.


             reply	other threads:[~2012-11-16 22:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16 22:25 joerg at netbsd dot org [this message]
2012-11-16 22:32 ` [Bug c++/55361] " pinskia at gcc dot gnu.org
2012-11-16 22:39 ` pinskia at gcc dot gnu.org
2012-11-16 23:06 ` paolo.carlini at oracle dot com
2012-11-17  0:19 ` redi at gcc dot gnu.org
2013-02-08  9:17 ` redi at gcc dot gnu.org
2022-01-05 15:41 ` ppalka 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=bug-55361-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).