Re: c++/5930: Incorrect access control checking on static data members

Re: c++/5930: Incorrect access control checking on static data members

[Gabriel Dos Reis]

The following reply was made to PR c++/5930; it has been noted by GNATS.

From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Kriang Lerdsuwanakij <lerdsuwa@users.sourceforge.net>
Cc: lerdsuwa@gcc.gnu.org, adc@ee.port.ac.uk, gcc-bugs@gcc.gnu.org,
   gcc-gnats@gcc.gnu.org
Subject: Re: c++/5930: Incorrect access control checking on static data members
Date: 29 Dec 2002 18:33:29 +0100

 Kriang Lerdsuwanakij <lerdsuwa@users.sourceforge.net> writes:
 
 | I will add a testcase from PR2739 which is the exact same problem
 | just for sure.
 
 Thanks!
 
 -- Gaby

Re: c++/5930: Incorrect access control checking on static data members

[Kriang Lerdsuwanakij]

The following reply was made to PR c++/5930; it has been noted by GNATS.

From: Kriang Lerdsuwanakij <lerdsuwa@users.sourceforge.net>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: lerdsuwa@gcc.gnu.org, adc@ee.port.ac.uk, gcc-bugs@gcc.gnu.org,
        gcc-gnats@gcc.gnu.org
Subject: Re: c++/5930: Incorrect access control checking on static data members
Date: Sun, 29 Dec 2002 23:48:12 +0700

 I will add a testcase from PR2739 which is the exact same problem
 just for sure.
 
 --Kriang
 
 
 Gabriel Dos Reis wrote:
 
 >lerdsuwa@gcc.gnu.org writes:
 >
 >| Synopsis: Incorrect access control checking on static data members
 >| 
 >| State-Changed-From-To: analyzed->closed
 >| State-Changed-By: lerdsuwa
 >| State-Changed-When: Sun Dec 29 08:14:40 2002
 >| State-Changed-Why:
 >|     Fixed in the main trunk after parser merge.
 >
 >Hi,
 >
 >  Is there an existing testcase for this bug?  If not, a new testcase
 >should be submitted.
 >
 >Thanks.
 >
 >-- Gaby
 >
 >
 >
 
 
 

Re: c++/5930: Incorrect access control checking on static data members

[Gabriel Dos Reis]

The following reply was made to PR c++/5930; it has been noted by GNATS.

From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: lerdsuwa@gcc.gnu.org
Cc: adc@ee.port.ac.uk, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: c++/5930: Incorrect access control checking on static data members
Date: 29 Dec 2002 17:17:20 +0100

 lerdsuwa@gcc.gnu.org writes:
 
 | Synopsis: Incorrect access control checking on static data members
 | 
 | State-Changed-From-To: analyzed->closed
 | State-Changed-By: lerdsuwa
 | State-Changed-When: Sun Dec 29 08:14:40 2002
 | State-Changed-Why:
 |     Fixed in the main trunk after parser merge.
 
 Hi,
 
   Is there an existing testcase for this bug?  If not, a new testcase
 should be submitted.
 
 Thanks.
 
 -- Gaby

Re: c++/5930: Incorrect access control checking on static data members

[lerdsuwa]

Synopsis: Incorrect access control checking on static data members

State-Changed-From-To: analyzed->closed
State-Changed-By: lerdsuwa
State-Changed-When: Sun Dec 29 08:14:40 2002
State-Changed-Why:
    Fixed in the main trunk after parser merge.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5930

Re: c++/5930: Incorrect access control checking on static data members

[lerdsuwa]

Synopsis: Incorrect access control checking on static data members

State-Changed-From-To: open->analyzed
State-Changed-By: lerdsuwa
State-Changed-When: Wed Jun  5 08:34:48 2002
State-Changed-Why:
    Confirmed.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5930

c++/5930: Incorrect access control checking on static data members

[adc]

>Number:         5930
>Category:       c++
>Synopsis:       Incorrect access control checking on static data members
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          accepts-illegal
>Submitter-Id:   net
>Arrival-Date:   Tue Mar 12 15:26:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Alastair Channon
>Release:        3.0.2 (and 2.96)
>Organization:
>Environment:
Red Hat Linux release 7.2
>Description:
The following program is invalid, but is accepted by
g++, without even a warning (even with -pedantic -Wall).

As I understand it, Child::childFunc() should not be allowed
access to Parent::parentVar, which is private in Parent.

This is probably related to Problem Report 3664.

#include <iostream>
using namespace std;

class Parent { private: static int parentVar; }; // parentVar is **private**
int Parent::parentVar=999;

class Child : public Parent { public: void childFunc(); };
void Child::childFunc() { cout << parentVar << endl; } // can access parentVar (**BAD**)
//nb same bug with protected and private inheritance

int main(int argc,char* argv[])
{
  Child child;
  // cout << child.parentVar << endl; // cannot access parentVar (good)
  child.childFunc();
  return 0;
}
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: