When should we write our own copy constructor?

C++ compiler provide default copy constructor (and assignment operator) with class. When we don’t provide implementation of copy constructor (and assignment operator) and tries to initialize object with already initialized object of same class then copy constructor gets called and copies members of class one by one in target object.

The problem with default copy constructor (and assignment operator) is – When we have members which dynamically gets initialized at run time, default copy constructor copies this members with address of dynamically allocated memory and not real copy of this memory. Now both the objects points to the same memory and changes in one reflects in another object, Further the main disastrous effect is, when we delete one of this object other object still points to same memory, which will be dangling pointer, and memory leak is also possible problem with this approach.

Hense, in such cases, we should always write our own copy constructor (and assignment operator).

Source: http://www.fredosaurus.com/notes-cpp/oop-condestructors/copyconstructors.html

This article is attributed to GeeksforGeeks.org



You Might Also Like

leave a comment



load comments

Subscribe to Our Newsletter