From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2874 invoked by alias); 4 Dec 2002 19:03:03 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 2853 invoked by uid 61); 4 Dec 2002 19:03:02 -0000 Date: Wed, 04 Dec 2002 11:03:00 -0000 Message-ID: <20021204190302.2852.qmail@sources.redhat.com> To: Boris.Maric@consol.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org From: bangerth@dealii.org Reply-To: bangerth@dealii.org, Boris.Maric@consol.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/8813: members of a nested class should not have special access to members of an enclosing class X-SW-Source: 2002-12/txt/msg00231.txt.bz2 List-Id: Synopsis: members of a nested class should not have special access to members of an enclosing class State-Changed-From-To: open->closed State-Changed-By: bangerth State-Changed-When: Wed Dec 4 11:03:01 2002 State-Changed-Why: There is a defect report to the C++ standard that treats this. The resolution is that the elements of member classes have the same access as member functions, for example, so they can also access private members of the enclosing class. I personally don't like this resolution, but it is there and is part of the C++ standard. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8813