public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	harri.pasanen@trema.com, jean-paul_marinier@hp.com,
	nobody@gcc.gnu.org, tot@trema.com
Subject: Re: c++/10245: [3.3/3.4 regression] ?: operator requires public copy constructor of return type
Date: Thu, 27 Mar 2003 17:26:00 -0000	[thread overview]
Message-ID: <20030327172247.10603.qmail@sources.redhat.com> (raw)

Old Synopsis: regression in 3.3, C++ ternary operator confuses type lookup
New Synopsis: [3.3/3.4 regression] ?: operator requires public copy constructor of return type

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Thu Mar 27 17:22:47 2003
State-Changed-Why:
    Confirmed. This worked in 3.2, but doesn't anymore in 3.3 and
    3.4. Here's an extract:
    ----------------------------
    struct X {};
    
    struct Y {
        Y ();
        operator X () const;
      private:
        Y (const Y &);
    };
    
    void foo() {
      X x = (1 ? Y() : Y());
    }
    ------------------------
    
    g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c x.cc
    x.cc: In function `void foo()':
    x.cc:7: error: `Y::Y(const Y&)' is private
    x.cc:12: error: within this context
    x.cc:7: error: `Y::Y(const Y&)' is private
    x.cc:12: error: within this context
    
    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.
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10245


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

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

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=20030327172247.10603.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=harri.pasanen@trema.com \
    --cc=jean-paul_marinier@hp.com \
    --cc=nobody@gcc.gnu.org \
    --cc=tot@trema.com \
    /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).