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

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

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

尤其是iOS开发者:

如果B是a的浅拷贝，那么对于原语数据，它就像B = [a assign];对于对象，B = [A retain];

B和A指向同一个内存位置

如果B是a的深层副本，则B = [a copy];

B和A指向不同的内存位置

B的内存地址与A的相同

B和A的含量相同

深拷贝

深度复制复制所有字段，并复制由字段指向的动态分配的内存。当对象与其引用的对象一起复制时，就会发生深度复制。

浅拷贝

浅复制是对象的逐位复制。创建一个新对象，该对象具有原始对象中值的精确副本。如果对象的任何字段是对其他对象的引用，则只复制引用地址，即只复制内存地址。

为了补充其他答案，

对象的浅拷贝对值类型执行逐值复制 基于属性，并通过引用复制基于引用类型的属性。 对象的深度复制对基于值类型的对象执行逐值复制 属性，以及基于引用类型的按值复制 层次结构深处的属性(引用类型)

广度vs深度;从引用树的角度考虑，将对象作为根节点。

浅:

变量A和B指的是不同的内存区域，当B被分配给A时，这两个变量指的是相同的内存区域。后来对其中一个内容的修改立即反映在另一个的内容中，因为它们共享内容。

深:

变量A和B指的是不同的内存区域，当B被分配给A时，A所指向的内存区域中的值被复制到B所指向的内存区域。后来对其中一项内容的修改仍为A或B所独有;内容不共享。

{想象两个对象:相同类型_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.