Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!taumet!mike
From: mike@taumet.com (Michael S. Ball)
Newsgroups: comp.lang.c++
Subject: Re: copy constructor semantics
Message-ID: <756@taumet.com>
Date: 4 Jun 91 14:27:22 GMT
References: <1991Jun03.220604.18506@thegang.uucp>
Reply-To: mike@taumet.UUCP (Michael S. Ball)
Organization: Taumetric Corporation, San Diego
Lines: 15

In article <1991Jun03.220604.18506@thegang.uucp> wells@thegang.uucp (David Wells) writes:
>can someone please clarify an issue i have concerning copy constructor semantics?
>
>in section 12.6.1 of Ellis and Stroustrup's ARM, (on the bottom of page 286) it
>is stated that initializing a class object with an explicit = results in a
>copy constructor being invoked.
:
>does anyone know if the ARM's treatment of copy constructors has been revised?

The ARM's treatment was itself a late revision and has not yet been inserted
into most compilers.  This was a grey area in the language, and most
compiler vendors elected to follow cfront rather than break new ground.
-- 
Michael S. Ball			mike@taumet.com
TauMetric Corporation		(619)697-7607