The copy constructor is used to initialize the new object with the previously created object of the same class. By default compiler wrote a shallow copy. Shallow copy works fine when dynamic memory allocation is not involved because when dynamic memory allocation is involved then both objects will points towards the same memory location in a heap, Therefore to remove this problem we wrote deep copy so both objects have their own copy of attributes in a memory. In order to read the details with complete examples and explanations you could see the article C++ constructors.

在面向对象编程中，类型包括成员字段的集合。这些字段可以按值或引用(即指向值的指针)存储。

在浅复制中，将创建该类型的新实例，并将值复制到新实例中。引用指针也像值一样被复制。因此，引用指向原始对象。对引用存储的成员的任何更改都同时出现在原始和副本中，因为没有对引用的对象进行复制。

在深度复制中，像以前一样复制按值存储的字段，但不复制按引用存储的对象指针。相反，对引用的对象进行深度复制，并存储指向新对象的指针。对这些引用对象所做的任何更改都不会影响该对象的其他副本。

浅复制是创建一个新对象，然后将当前对象的非静态字段复制到新对象。如果字段是值类型——>，则执行字段的逐位复制;对于引用类型——>，引用被复制，但被引用的对象没有;因此，原始对象及其克隆对象引用同一个对象。

深度复制是创建一个新对象，然后将当前对象的非静态字段复制到新对象。如果字段是值类型——>，则执行字段的逐位复制。如果字段是引用类型——>，则执行引用对象的新副本。要克隆的类必须标记为[Serializable]。

{想象两个对象:相同类型_t的A和B(相对于c++)，你正在考虑将A浅/深复制到B}

浅拷贝: 简单地将a的引用复制到b中，把它看作是a的地址的副本。 因此，A和B的地址将是相同的，即它们将指向相同的内存位置，即数据内容。

Deep copy: Simply makes a copy of all the members of A, allocates memory in a different location for B and then assigns the copied members to B to achieve deep copy. In this way, if A becomes non-existant B is still valid in the memory. The correct term to use would be cloning, where you know that they both are totally the same, but yet different (i.e. stored as two different entities in the memory space). You can also provide your clone wrapper where you can decide via inclusion/exclusion list which properties to select during deep copy. This is quite a common practice when you create APIs.

只有当你了解其中的利害关系时，你才可以选择做浅拷贝。当你在c++或C中有大量的指针要处理时，做一个对象的浅拷贝真的是一个坏主意。

EXAMPLE_OF_DEEP COPY_ An example is, when you are trying to do image processing and object recognition you need to mask "Irrelevant and Repetitive Motion" out of your processing areas. If you are using image pointers, then you might have the specification to save those mask images. NOW... if you do a shallow copy of the image, when the pointer references are KILLED from the stack, you lost the reference and its copy i.e. there will be a runtime error of access violation at some point. In this case, what you need is a deep copy of your image by CLONING it. In this way you can retrieve the masks in case you need them in the future.

EXAMPLE_OF_SHALLOW_COPY I am not extremely knowledgeable compared to the users in StackOverflow so feel free to delete this part and put a good example if you can clarify. But I really think it is not a good idea to do shallow copy if you know that your program is gonna run for an infinite period of time i.e. continuous "push-pop" operation over the stack with function calls. If you are demonstrating something to an amateur or novice person (e.g. C/C++ tutorial stuff) then it is probably okay. But if you are running an application such as surveillance and detection system, or Sonar Tracking System, you are not supposed to keep shallow copying your objects around because it will kill your program sooner or later.

简而言之，这取决于什么指向什么。在浅拷贝中，对象B指向对象a在内存中的位置。在深度复制中，对象A的内存位置中的所有东西都被复制到对象B的内存位置。

这篇wiki文章有一个很好的图表。

http://en.wikipedia.org/wiki/Object_copy

var source = { firstName="Jane", lastname="Jones" };
var shallow = ShallowCopyOf(source);
var deep = DeepCopyOf(source);
source.lastName = "Smith";
WriteLine(source.lastName); // prints Smith
WriteLine(shallow.lastName); // prints Smith
WriteLine(deep.lastName); // prints Jones