public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nathan@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	swhite@discreet.com
Subject: Re: c++/6340: copy constructor vs non-default constructor
Date: Thu, 18 Apr 2002 00:58:00 -0000	[thread overview]
Message-ID: <20020418075838.2366.qmail@sources.redhat.com> (raw)

Synopsis: copy constructor vs non-default constructor

State-Changed-From-To: open->closed
State-Changed-By: nathan
State-Changed-When: Thu Apr 18 00:58:37 2002
State-Changed-Why:
    not a bug.
    	Thing2 b = a;
    is formally
    	Thing2 b(Thing2 (a));
    i.e. convert a to Thing2 then copy construct b with
    that. [8.5]/14 class copy initialization case.
    But we are allowed to elide that temporary Thing2.
    See [12.8]/15 of the std. The copy ctor must
    exist and be accessible though.

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


             reply	other threads:[~2002-04-18  7:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18  0:58 nathan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-17 12:16 swhite

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=20020418075838.2366.qmail@sources.redhat.com \
    --to=nathan@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=swhite@discreet.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).