From: "Mikael Kilpeläinen" <mikael.kilpelainen@kolumbus.fi>
To: gcc@gcc.gnu.org
Subject: Re: Passing temprary by reference requires copy constructor in 3.4?
Date: Fri, 26 Nov 2004 21:41:00 -0000 [thread overview]
Message-ID: <200411262210.14153.mikael.kilpelainen@kolumbus.fi> (raw)
In-Reply-To: <416BE1A0-3FE6-11D9-941D-000A95D692F4@physics.uc.edu>
On Friday 26 November 2004 22:03, Andrew Pinski wrote:
> Why, the DR is still active so GCC is correct as of right now.
> If and when the DR goes to defect, we will implement the needed
> change. But currently GCC is following the standard.
Yes, I was not saying that gcc is wrong. That was not my intention, I just
wanted to point out that it is likely to happen and the flag could be helpful
for certain people. Of course I might be wrong. I just saw fine opportunity
to talk about this :)
Mikael
next prev parent reply other threads:[~2004-11-26 20:10 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
2004-11-26 20:10 ` Mikael Kilpeläinen
2004-11-26 21:36 ` Andrew Pinski
2004-11-26 21:41 ` Mikael Kilpeläinen [this message]
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=200411262210.14153.mikael.kilpelainen@kolumbus.fi \
--to=mikael.kilpelainen@kolumbus.fi \
--cc=gcc@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).