This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/29040] missing access control checks in subclasses for nested types
- From: "paolo.carlini at oracle dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 14 Oct 2013 18:05:39 +0000
- Subject: [Bug c++/29040] missing access control checks in subclasses for nested types
- Auto-submitted: auto-generated
- References: <bug-29040-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29040
Paolo Carlini <paolo.carlini at oracle dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|gcc-bugs at gcc dot gnu.org |
Known to fail| |
--- Comment #2 from Paolo Carlini <paolo.carlini at oracle dot com> ---
To be clear: the issue isn't access control of subclasses per se: the real
issue is about access control for 'struct n' vs 'n' when the declaration of p
is parsed: 'struct n' is handled like 'struct whatever', is accepted without
even performing a lookup. Indeed, changing 'struct n' to 'n' per normal C++ for
this kind of code, leads to the expected error message. I think that accepting
'struct n' without lookup and thus without access control in this kind of code
used to be legal in cfront.