heng wrote:
Quote:
Salt_Peter wrote:
>
>
Thanks. But you explicitly define the copy constructor in your example,
I mean, without the explicit copy constructor, which constructor is
used in the expression like
>
A obj2(obj1);
>
is it still the copy constructor?
Yes, the compiler must provide a copy ctor unless you explicitly
prevent it.
Otherwise, the above would generate an error.
So why not implement the copy to match your needs?
To push the logic a little further, how come the following works?
class A {
};
int main()
{
A a; // def ctor
A b(a); // copy ctor
a = b; // assignment - not a copy!!!
}
