From: Eljay Love-Jensen <eljay@adobe.com>
To: Jeroen Wijnhout <jeroen@wijnhout.com>, gcc-help@gcc.gnu.org
Subject: Re: copy ctor not called
Date: Thu, 07 Jul 2005 12:02:00 -0000 [thread overview]
Message-ID: <6.2.1.2.2.20050707070253.028b4e28@iplan-mn.corp.adobe.com> (raw)
In-Reply-To: <6.2.1.2.2.20050705090751.0243dd68@iplan-mn.corp.adobe.com>
Hi Jeroen,
>According to your statement they are wrong.
Please re-read my statement. My statement does not contradict what you cited from C++ Primer.
What is being elided is the assignment operator, not the copy constructor. The copy constructor is still being used for initialization.
Sincerely,
--Eljay
next prev parent reply other threads:[~2005-07-07 12:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-02 18:21 Jeroen Wijnhout
2005-07-02 19:17 ` Travis Spencer
2005-07-03 8:15 ` Jeroen Wijnhout
2005-07-03 12:27 ` Dirk Jagdmann
2005-07-03 13:44 ` Jeroen Wijnhout
2005-07-05 14:10 ` Eljay Love-Jensen
2005-07-07 11:45 ` Jeroen Wijnhout
2005-07-07 12:02 ` Eljay Love-Jensen [this message]
2005-07-08 18:26 ` Jeroen Wijnhout
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=6.2.1.2.2.20050707070253.028b4e28@iplan-mn.corp.adobe.com \
--to=eljay@adobe.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jeroen@wijnhout.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).