| <<< The need for a copy constructor | Index | The need for overloaded assignment operator >>> |
There is one more very serious problem in current Rectangle struct implementation:
the default version of the object assignment also makes a shallow copy. For example,
int main()
{
Rectangle rect( "first", 333, 222 );
Rectangle rect2 = rect; // make a deep copy
rect2.set_name( "second" );
std::cout << "rectangle width: " << rect.width << '\n';
std::cout << "rectangle height: " << rect.height << '\n';
std::cout << "rectangle area: " << rect.area() << '\n';
std::cout << "rectangle name: " << rect.get_name() << '\n' << '\n';
rect = rect2; // shallow assignment!
std::cout << "rectangle width: " << rect2.width << '\n';
std::cout << "rectangle height: " << rect2.height << '\n';
std::cout << "rectangle area: " << rect2.area() << '\n';
std::cout << "rectangle name: " << rect2.get_name() << '\n' << '\n';
return 0;
}
And the program crashes are back!
| <<< The need for a copy constructor | Index | The need for overloaded assignment operator >>> |