public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dmuell@gmx.net
To: gcc-gnats@gcc.gnu.org
Subject: c++/2739: g++ allows accessing a private member
Date: Fri, 04 May 2001 08:16:00 -0000	[thread overview]
Message-ID: <200105041513.f44FDb727721@rotes20.wohnheim.uni-kl.de> (raw)

>Number:         2739
>Category:       c++
>Synopsis:       g++ allows accessing private members
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          accepts-illegal
>Submitter-Id:   net
>Arrival-Date:   Fri May 04 08:16:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Dirk Mueller
>Release:        3.0 20010504 (prerelease)
>Organization:
>Environment:
System: Linux 2.4.4
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../configure --enable-shared --enable-threads --enable-languages=c,c++
>Description:

g++ fails to check the declared private: access specification in derived
classes for static members. 

>How-To-Repeat:

=== Cut ===
class Base {
private:
    static int fooprivate;
protected:
    static int fooprotected;
public:
    static int foopublic;
};

class Derived : public Base {
public:
    void test();
};

int Base::fooprivate=42;
int Base::fooprotected=42;
int Base::foopublic=42;

void Derived::test() {
    if ( fooprivate );
    if ( fooprotected );
    if ( foopublic );
}

int main()
{
    Derived d;
    d.test();
}
=== Cut ===

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


                 reply	other threads:[~2001-05-04  8:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200105041513.f44FDb727721@rotes20.wohnheim.uni-kl.de \
    --to=dmuell@gmx.net \
    --cc=gcc-gnats@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).