• Source: Object slicing

In C++ programming, object slicing occurs when an object of a subclass type is copied to an object of superclass type: the superclass copy will not have any of the member variables or member functions defined in the subclass. These variables and functions have, in effect, been "sliced off".
More subtly, object slicing can likewise occur when an object of a subclass type is copied to an object of the same type by the superclass's assignment operator, in which case some of the target object's member variables will retain their original values instead of getting copied over from the source object.
This issue is not inherently unique to C++, but it does not occur naturally in most other object-oriented languages — not even in C++'s relatives such as D, Java, and C# — because copying of objects is not a basic operation in those languages.
Instead, those languages prefer to manipulate objects via implicit references, such that only copying the reference is a basic operation.
In C++, by contrast, objects are copied automatically whenever a function takes an object argument by value or returns an object by value.
Additionally, due to the lack of garbage collection in C++, programs will frequently copy an object whenever the ownership and lifetime of a single shared object would be unclear. For example, inserting an object into a standard library collection (such as a std::vector) typically involves making and inserting a copy into the collection.




Example






See also


Diamond problem




External links


What is the slicing problem in C++?
geeksforgeeks.org/object-slicing-in-c/
learncpp.com/cpp-tutorial/121-pointers-and-references-to-the-base-class-of-derived-objects/

Kata Kunci Pencarian:

• Object slicing
• Slicing
• Slic3r
• Value type and reference type
• Index of object-oriented programming articles
• Criticism of C++
• False color
• Array slicing
• Slicer (3D printing)
• Multi-material 3D printing