public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: wolfgang.bangerth@iwr.uni-heidelberg.de
To: gcc-gnats@gcc.gnu.org
Cc: wolfgang@dealii.org
Subject: c++/6402: Qualified reference to variable causes copy
Date: Mon, 22 Apr 2002 01:46:00 -0000 [thread overview]
Message-ID: <20020422084012.5363.qmail@sources.redhat.com> (raw)
>Number: 6402
>Category: c++
>Synopsis: Qualified reference to variable causes copy
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Apr 22 01:46:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Wolfgang Bangerth
>Release: unknown-1.0
>Organization:
>Environment:
gcc 2.95, 3.1pre, 3.2 mainline
>Description:
The following snippet doesn't compiler, although I believe
it should. The copy operation is caused by me qualifying
the name of the member variable "t" with the name of the
base class. The original code came from an application
where the base class exists twice and a qualification is
actually necessary.
Regards
Wolfgang
-----------------------code------------------------
struct T {
T();
private:
T (const T&);
};
struct Base {
T t;
};
struct Derived : public Base {
void f() {
const T &t_ref = Base::t; // taking reference, not a copy!
};
};
-----------------error message-----------------------
x.cc: In method `void Derived::f()':
x.cc:4: `T::T(const T &)' is private
x.cc:13: within this context
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-04-22 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 1:46 wolfgang.bangerth [this message]
2002-09-15 5:10 nathan
2002-12-30 14:37 reichelt
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=20020422084012.5363.qmail@sources.redhat.com \
--to=wolfgang.bangerth@iwr.uni-heidelberg.de \
--cc=gcc-gnats@gcc.gnu.org \
--cc=wolfgang@dealii.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).