This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: copy ctor not called

From: Eljay Love-Jensen <eljay at adobe dot com>
To: Jeroen Wijnhout <jeroen at wijnhout dot com>, gcc-help at gcc dot gnu dot org
Date: Thu, 07 Jul 2005 07:04:51 -0500
Subject: Re: copy ctor not called
References: <200507022024.10598.Jeroen.Wijnhout@kdemail.net><5d0f609905070305263875cb57@mail.gmail.com><200507031547.33672.Jeroen.Wijnhout@kdemail.net><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

Follow-Ups:
- Re: copy ctor not called
  - From: Jeroen Wijnhout

References:
- copy ctor not called
  - From: Jeroen Wijnhout
- Re: copy ctor not called
  - From: Dirk Jagdmann
- Re: copy ctor not called
  - From: Jeroen Wijnhout
- Re: copy ctor not called
  - From: Eljay Love-Jensen

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]