public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakobsybren at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/40901]  New: Access qualifiers of embedded templates are discarded
Date: Wed, 29 Jul 2009 09:45:00 -0000	[thread overview]
Message-ID: <bug-40901-17996@http.gcc.gnu.org/bugzilla/> (raw)

Consider the following code fragment:
==== BEGIN CODE ======
#include <iostream>
using namespace std;

class A {
  private: //protected:
  template <size_t y>
  struct s {
    enum {value = y };
  };

  public:
  A() {}
};

int main() {
  A();
  cout << A::s<10>::value << endl;
  return 0;
}
==== END CODE ======
Both for private and protected access for the embedded template, this code will
compile without errors and show the number 10 when the resulting binary is ran.
This code should give compilation errors however, because the template is not
public. In more elaborate code where class A is used as the baseclass for
derived classes, the same problem arises. The template is public in all derived
classes both when defined as private and protected in class A.


-- 
           Summary: Access qualifiers of embedded templates are discarded
           Product: gcc
           Version: 4.3.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jakobsybren at gmail dot com


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


             reply	other threads:[~2009-07-29  9:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29  9:45 jakobsybren at gmail dot com [this message]
2009-07-29 11:01 ` [Bug c++/40901] " jwakely dot gcc at gmail dot com
2009-08-25 14:04 ` bangerth at gmail 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-40901-17996@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).