From: Andrew Pinski <pinskia@physics.uc.edu>
To: Peter Cech <pcech@vision.ee.ethz.ch>
Cc: gcc@gcc.gnu.org
Subject: Re: Passing temprary by reference requires copy constructor in 3.4?
Date: Fri, 26 Nov 2004 19:48:00 -0000 [thread overview]
Message-ID: <9C148074-3FDF-11D9-941D-000A95D692F4@physics.uc.edu> (raw)
In-Reply-To: <20041126191040.GD9325@ee.ethz.ch>
On Nov 26, 2004, at 2:10 PM, Peter Cech wrote:
> Hi,
> a.cpp: In function `void caller2()':
> a.cpp:16: error: `AnyEvent::AnyEvent(const AnyEvent&)' is private
> a.cpp:29: error: within this context
>
> Why gcc requires copy constructor in such situation?
It does not require the copy constructor, just requires it be
accessible.
I would read the changes page for 3.4 which documents why this changed.
Mainly this is required by the C++ standard.
Thanks,
Andrew Pinski
next prev parent reply other threads:[~2004-11-26 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-26 19:38 Peter Cech
2004-11-26 19:48 ` Andrew Pinski [this message]
2004-11-26 20:10 ` Mikael Kilpeläinen
2004-11-26 21:36 ` Andrew Pinski
2004-11-26 21:41 ` Mikael Kilpeläinen
2004-11-27 18:16 ` Paolo Bonzini
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=9C148074-3FDF-11D9-941D-000A95D692F4@physics.uc.edu \
--to=pinskia@physics.uc.edu \
--cc=gcc@gcc.gnu.org \
--cc=pcech@vision.ee.ethz.ch \
/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).