public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: kunert@physik.tu-dresden.de
To: gcc-gnats@gcc.gnu.org
Subject: c++/6479: access control bug
Date: Fri, 26 Apr 2002 11:06:00 -0000	[thread overview]
Message-ID: <20020426180442.5903.qmail@sources.redhat.com> (raw)


>Number:         6479
>Category:       c++
>Synopsis:       access control bug
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Fri Apr 26 11:06:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Thomas Kunert
>Release:        gcc version 3.1 20020423
>Organization:
>Environment:
$ /opt/bin/g++-31 -v
Reading specs from /opt/lib/gcc-lib/i686-pc-linux-gnu/3.1/specs
Configured with: ../gcc/configure i686-pc-linux-gnu --enable-shared --prefix=/opt --enable-languages=c,c++,f77
Thread model: single
gcc version 3.1 20020423 (prerelease)
>Description:
The following code is being rejected. 
This is a regression from 3.0.

class A {
protected:
  A& operator=( const A& a ) { return *this; }
};

class B : public A
{};

int main()
{
  B x;
  B y;
  x = y;
}

$ /opt/bin/g++-31 x2.cc  
x2.cc: In member function `B& B::operator=(const B&)':
x2.cc:3: `A& A::operator=(const A&)' is protected
x2.cc:13: within this context

class B : public A
{};

int main()
{
  B x;
  B y;
  x = y;
}
>How-To-Repeat:

>Fix:

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


             reply	other threads:[~2002-04-26 18:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26 11:06 kunert [this message]
2002-04-26 13:31 mmitchel
2002-04-26 15:38 mmitchel

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=20020426180442.5903.qmail@sources.redhat.com \
    --to=kunert@physik.tu-dresden.de \
    --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).