public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vlukas at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/17435] [4.0 Regression] Binding a temporary of derived type to reference of base
Date: Mon, 13 Sep 2004 15:07:00 -0000 [thread overview]
Message-ID: <20040913150751.7898.qmail@sourceware.org> (raw)
In-Reply-To: <20040912110521.17435.vlukas@gmx.de>
------- Additional Comments From vlukas at gmx dot de 2004-09-13 15:07 -------
(In reply to comment #4)
> I think I remember that there was some language in the standard that
> says that the compiler _may_ invoke the copy constructor (which, btw,
> was the reason the copy constructor of the base class has to be
> accessible, one of our constant streams of bug reports). I understand
> that that is a rather vague pointer at the right place of the standard,
> I guess I will have to go look it up some time, just not today.
I assume you mean 12.2 "Temporary objects".
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17435
next prev parent reply other threads:[~2004-09-13 15:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-12 11:05 [Bug c++/17435] New: Temporay bound to reference is immediately destructed vlukas at gmx dot de
2004-09-12 23:22 ` [Bug c++/17435] " bangerth at dealii dot org
2004-09-12 23:49 ` gdr at integrable-solutions dot net
2004-09-13 7:57 ` [Bug c++/17435] [4.0 Regression] " pinskia at gcc dot gnu dot org
2004-09-13 13:11 ` bangerth at dealii dot org
2004-09-13 15:07 ` vlukas at gmx dot de [this message]
2004-09-13 15:43 ` [Bug c++/17435] [4.0 Regression] Binding a temporary of derived type to reference of base bangerth at dealii dot org
2004-10-15 0:44 ` pinskia at gcc dot gnu dot org
2004-10-15 0:45 ` pinskia at gcc dot gnu dot org
2004-10-28 1:03 ` mmitchel at gcc dot gnu dot org
2004-10-28 5:17 ` cvs-commit at gcc dot gnu dot org
2004-10-28 5:26 ` mmitchel at gcc dot gnu dot org
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=20040913150751.7898.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).