public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10245: [3.3/3.4 regression] ?: operator requires public copy constructor of return type
Date: Thu, 27 Mar 2003 18:16:00 -0000	[thread overview]
Message-ID: <20030327175600.29632.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/10245; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: Andreas Schwab <schwab@suse.de>
Cc: gcc-bugs@gcc.gnu.org, <harri.pasanen@trema.com>,
   <jean-paul_marinier@hp.com>, <tot@trema.com>, <gcc-gnats@gcc.gnu.org>
Subject: Re: c++/10245: [3.3/3.4 regression] ?: operator requires public copy
 constructor of return type
Date: Thu, 27 Mar 2003 11:55:29 -0600 (CST)

 > |>     Apparently it wants to make a copy of the return arguments.
 > |>     Since at least in Standard C++ (not in Gnu C++) ?: returns
 > |>     an rvalue, I don't think this is necessary.
 > 
 > ?: returns an lvalue if both expressions have the same type.
 
 Sorry for the confusion, you are of course right. It shouldn't change the 
 outcome, though. I still think this behavior is in error.
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-03-27 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-27 18:16 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-30 21:00 paolo
2003-03-27 20:58 Janis Johnson
2003-03-27 17:56 Andreas Schwab
2003-03-27 17:26 bangerth

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=20030327175600.29632.qmail@sources.redhat.com \
    --to=bangerth@ices.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).