DOCSLIB.ORG

Object Oriented Programming COP3330 / CGS5409  C++ Automatics ◦ Copy Constructor () ◦ Assignment Operator =  Shallow Copy Vs

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Object Oriented Programming COP3330 / CGS5409  C++ Automatics ◦ Copy Constructor () ◦ Assignment Operator =  Shallow Copy Vs Object Oriented Programming COP3330 / CGS5409 C++ Automatics ◦ Copy constructor () ◦ Assignment operator = Shallow copy vs. Deep copy DMA Review c-strings vs. concept of string class Constructor Destructor Copy Constructor Assignment operator = if you do not explicitly define one in a class, a default version will automatically be built for you by the compiler The automatic versions of the constructor and destructor don't do anything, but they will be there if you do not build them. The constructor you get is the "default constructor" -- no parameters – The automatic versions of the Copy Constructor and the Assignment operator overload are similar to each other, and their default versions are always built in a standard way. A copy constructor IS a constructor, so it is a function with the same name as the class and no return type (just like any constructor). However, it is invoked implicitly when something is done that causes a COPY of an existing object to be created. This happens when: ◦ An object is defined to have the value of another object of the same type ◦ An object is passed by value into a function ◦ An object is returned (by value) from a function Here's an example of item #1 in the above list: Fraction f1, f2(3,4); // declaration of two //fractions Fraction f3 = f2; // declaration of f3 being // initialized as a copy of f2 Note: This last line of code calls the copy constructor, since the initialization is on the same line as the declaration of f3. Contrast this with the following: f1 = f2; // this uses the assignment // operator, since f1 and f2 already exist Since the purpose of a copy constructor is to not only initialize the data in an object, but to initialize it as a copy of another existing object, the original object must be passed in as a parameter. So, a copy constructor always has one parameter, which is of the same type as the class itself. It is always passed by reference, as well (it has to be - - since to pass by value, we must invoke a copy constructor, and this is what we are defining!) Format: className(const className &); The const is not required, but it is usally a good idea, because we only want to make a copy -- we don't want to change the original. Here are some examples of copy constructor declarations for classes we have seen: Fraction(const Fraction & f); Timer(const Timer & t); Directory(const Directory & d); Store(const Store & s); The default version of the copy constructor (created by the compiler) makes what is known as a shallow copy. This simply means that the object is copied exactly as is -- each member data value is copied exactly over to the corresponding member data location in the new object. This is sufficient for many cases, but not for ALL cases. Example: Fraction f1(3,4); This fraction object has a numerator of 3 and a denominator of 4. If this object is passed into a function by value, a copy will be made, and the new object's numerator will be 3, denominator 4. In this case, the shallow copy is sufficient. Consider, however, the Directory class of the phone book example. The member data variables were currentsize and maxsize (both of type int), and a pointer, entryList (of type Entry * ), which pointed to dynamically allocated data outside the actual object. This is the situation in which a shallow copy is not sufficient.! For instance, if the original object is storing the address 1024 in entryList, the copy will also get the 1024, and therefore the copy will be pointing to the original dynamic data! This will especially pose problems if, when the copy goes out of scope, it cleans up the dynamic data along with it. When there is a pointer (inside an object) that points to dynamic data, the shallow copy is not sufficient, because it does not copy the dynamic data, only the pointer. A deep copy is needed. The following slide is what we might write for a copy constructor definition in the Directory class (from the phonebook database example): Directory::Directory(const Directory & d) // copies object 'd' into the new object being created (this one) { // copy the static variables normally maxsize = d.maxsize; currentsize = d.currentsize; // create a new dynamic array for the // new object's pointer entryList = new Entry[d.maxsize]; // copy the dynamic data for (int i = 0; i < currentsize; i++) entryList[i] = d.entryList[i]; } The assignment operator = is similar to the copy constructor. It is called when one object is assigned to another. Example call: Fraction f1, f2; f1 = f2; // this call invokes the //assignment operator Like the copy constructor, the assignment operator has to make a copy of an object. The default version makes a shallow copy. If a deep copy is desired for assignments on a user-defined type (e.g. a class), then the assignment operator should be overloaded for the class. The task done by the assignment operator is very similar to that of a copy constructor, but there are a couple of differences. The copy constructor is initializing a brand new object as a copy of an existing one. The new object's data is being initialized for the first time. An assignment operator sets an existing object's state to that of another existing object. In situations with dynamic allocation, this may mean that old dynamic space must be cleaned up first before the copy is made. Also, an assignment operator also returns the value that was assigned (the copy constructor has no return). Consider the case of integers. In the statement: a = b = c = 4; The first operation is (c = 4), and this operation returns the assigned value (4), so that the result can be used as an operand in the next assignment (b = 4). This value should be returned by reference when overloading = for objects. To return the object, we need to be able to refer to an object from inside the object itself. From inside any member function, an object has access to its own address through a pointer called this, which is a keyword in C++. In an assignment operator, you must return the object itself (by reference), so you can return the target of the this pointer (which would be *this) Like the copy constructor, the original object needs to be passed in, so there will be one parameter (of the same type as the object itself). The parameter is the same as in the copy constructor. Declaration examples for a few classes: Directory& operator= (const Directory &); Fraction& operator=(const Fraction &); Timer& operator=(const Timer &); Circle& operator=(const Circle &); Directory& Directory::operator=(const Directory & d); // copies object 'd' into the new object being created (this one) { if (this != &d) // only copy if object passed is not this one { // since this is not a brand new object, we // should delete any information currently attached delete [] entryList; // similar to the copy constructor definition maxsize = d.maxsize; currentsize = d.currentsize; entryList = new Entry[d.maxsize]; for (int i = 0; i < currentsize; i++) entryList[i] = d.entryList[i]; } return *this; // return the object itself (by reference) } http://www.cs.fsu.edu/~myers/savitch3c++/Ch10/10- 10,%20-11,%20-12/Chapter%2011%20Version/ This example shows a class called PFArrayD, which is declared in the file "pfarrayd.h" and defined in "pfarrayd.cpp". This class stores a list of values of type double -- the list is stored using a dynamically allocated array, so there is no size limit. There are tracking variables in the member data for keeping track of the allocated space and the used space. The class also has a copy constructor and assignment operator -- both of them to do the "deep copy". And of course the destructor cleans up the space. The file "10-12.cpp" contains a main program that demonstrates some of the class features. http://www.cs.fsu.edu/~myers/savitch3c++/Ch10/1 0-10,%20-11,%20-12/Chapter%2011%20Version/ In this particular example, once the capacity of the array is set (when the object is created), it becomes the upper limit of storage for the list. How to use the array resizing technique to add functionality to the class? Specifically, to be able to remove the boundary check in the addElement function, and have no upper limit on the size of the list of values. (This would entail writing a Grow function, or perhaps a more generic "Resize" function -- to allow the allocated space to vary -- then calling it from appropriate places). • http://www.cs.fsu.edu/~myers/deitel5c++/c h11/Fig11_17_18/ This is similar to the previous example, involving dynamic allocation inside a class. It is used to build a safer array type -- the class in this one is called Array, and it stores a dynamically created integer array. Both use dynamic memory management, but they vary a little in specific implementation details. • http://www.cs.fsu.edu/~myers/deitel5c++/ch11/Fig11_1 7_18/ Some highlights of this example: Dynamic creation of array in the constructor Copy constructor and assignment operator, for deep copy Operator overloads provided (equality comparisons and for I/O) Two subscript operators (the brackets [] ). ◦ Note: when bracket operators are provided, the programmer does have the option to provide TWO versions -- one that returns by reference, and one that returns by value or by const reference (and must be a const member function). ◦ The difference is that one will return an L-value (storage location that could be modified), and one will return only an R-value (a read-only value).
Load more

Recommended publications
  • C++ COPY CONSTRUCTOR Rialspo Int.Co M/Cplusplus/Cpp Co Py Co Nstructo R.Htm Copyrig Ht © Tutorialspoint.Com
    C++ COPY CONSTRUCTOR http://www.tuto rialspo int.co m/cplusplus/cpp_co py_co nstructo r.htm Copyrig ht © tutorialspoint.com The copy constructor is a constructor which creates an object by initializing it with an object of the same class, which has been created previously. The copy constructor is used to: Initialize one object from another of the same type. Copy an object to pass it as an arg ument to a function. Copy an object to return it from a function. If a copy constructor is not defined in a class, the compiler itself defines one.If the class has pointer variables and has some dynamic memory allocations, then it is a must to have a copy constructor. The most common form of copy constructor is shown here: classname (const classname &obj) { // body of constructor } Here, obj is a reference to an object that is being used to initialize another object. #include <iostream> using namespace std; class Line { public: int getLength( void ); Line( int len ); // simple constructor Line( const Line &obj); // copy constructor ~Line(); // destructor private: int *ptr; }; // Member functions definitions including constructor Line::Line(int len) { cout << "Normal constructor allocating ptr" << endl; // allocate memory for the pointer; ptr = new int; *ptr = len; } Line::Line(const Line &obj) { cout << "Copy constructor allocating ptr." << endl; ptr = new int; *ptr = *obj.ptr; // copy the value } Line::~Line(void) { cout << "Freeing memory!" << endl; delete ptr; } int Line::getLength( void ) { return *ptr; } void display(Line obj) { cout << "Length of line : " << obj.getLength() <<endl; } // Main function for the program int main( ) { Line line(10); display(line); return 0; } When the above code is compiled and executed, it produces the following result: Normal constructor allocating ptr Copy constructor allocating ptr.
    [Show full text]
  • Concise Introduction to C++
    i i final3 2012/4/19 page 47 i i Chapter 2 Concise Introduction to C++ C++ seems to be most suitable for many practical applications. Indeed, C++ is sufficiently high-level to allow transparent object-oriented programming and efficient use of human resources, yet is also sufficiently low-level to have types, variables, pointers, arrays, and loops to allow efficient use of computer resources. In this chapter, we give a concise description of C++ and illustrate its power as an object-oriented programming language. In particular, we show how to construct and use abstract mathematical objects such as vectors and matrices. We also explain the notion of a template class, which can be filled with a concrete type later on in compilation time. We also discuss inheritance and illustrate its potential. 2.1 Objects As we have seen above, C is a language based on functions. Every command is also a function that returns a value that can be further used or abandoned, according to the wish of the programmer. Furthermore, programmers can write their own functions, which may also return variables of the type specified just before the function name. When the function is called, a temporary, unnamed variable is created to store the returned value until it has been used. C++, on the other hand, is an object-oriented programming language. In this kind of language, the major concern is not the functions that can be executed but rather the objects upon which they operate. Although C++ supports all the operations and features available in C, its point of view is different.
    [Show full text]
  • Things I Learned from the Static Analyzer
    Things I Learned From The Static Analyzer Bart Verhagen [email protected] 15 November 2019 Static code analyzers What can they do for us? Developer High level structure Low level details Static code analyzer Expertise Static code analyzers Focus areas • Consistency • Maintenance • Performance • Prevent bugs and undefined behaviour Static code analyzers Used static code analyzers for this talk • clang-tidy • cppcheck Consistency ??? ??? #include "someType.h" class Type; template<typename T> class TemplateType; typedef TemplateType<Type> NewType; Consistency Typedef vs using Typedef vs using #include "someType.h" class Type; template<typename T> class TemplateType; typedef TemplateType<Type> NewType; using NewType = TemplateType<Type>; // typedef TemplateType<T> NewTemplateType; // Compilation error template<typename T> using NewTemplateType = TemplateType<T>; modernize-use-using Warning: use ’using’ instead of ’typedef’ The Clang Team. Clang-tidy - modernize-use-using. url: https://clang.llvm.org/extra/clang-tidy/checks/modernize-use-using.html Maintenance ??? ??? class Class { public: Class() : m_char('1'), m_constInt(2) {} explicit Class(char some_char) : m_char(some_char), m_constInt(2) {} explicit Class(int some_const_int) : m_char('1'), m_constInt(some_const_int) {} Class(char some_char, int some_const_int) : m_char(some_char), m_constInt(some_const_int) {} private: char m_char; const int m_constInt; }; Maintenance Default member initialization Default member initialization class Class { public: Class() : m_char('1'), m_constInt(2)
    [Show full text]
  • Copy Elision in Exception Handling
    Document Number: J16/04-0165 = WG21 N1725 Date: 2004-11-08 Reply to: William M. Miller Edison Design Group, Inc. [email protected] Copy Elision in Exception Handling I. The Problem Clause 15 has two passages dealing with copy elision in exception handling. 15.1¶5 says, If the use of the temporary object can be eliminated without changing the meaning of the program except for the execution of constructors and destructors associated with the use of the temporary object (12.2), then the exception in the handler can be initialized directly with the argument of the throw expression. When the thrown object is a class object, and the copy constructor used to initialize the temporary copy is not accessible, the program is ill-formed (even when the temporary object could otherwise be eliminated). Similarly, if the destructor for that object is not accessible, the program is ill-formed (even when the temporary object could otherwise be eliminated). In a sometimes overlapping, sometimes differing passage, 15.3¶17 says, If the use of a temporary object can be eliminated without changing the meaning of the program except for execution of constructors and destructors associated with the use of the temporary object, then the optional name can be bound directly to the temporary object specified in a throw-expression causing the handler to be executed. The copy constructor and destructor associated with the object shall be accessible even when the temporary object is eliminated. Part of the difference is terminological. For instance, 15.1¶5 refers to “the exception in the handler,” while the “optional name” in 15.3¶17 is a reference to the exception-declaration that is part of a handler (15¶1).
    [Show full text]
  • The Rule of the Big Five
    C++11: The Rule of the Big Five Resource Management The dynamic creation and destruction of objects was always one of the bugbears of C. It required the programmer to (manually) control the allocation of memory for the object, handle the object’s initialisation, then ensure that the object was safely cleaned-up after use and its memory returned to the heap. Because many C programmers weren’t educated in the potential problems (or were just plain lazy or delinquent in their programming) C got a reputation in some quarters for being an unsafe, memory-leaking language. C++ improved matters significantly by introducing an idiom known (snappily) as RAII/RRID – Resource Acquisition Is Initialisation / Resource Release Is Destruction*. The idiom makes use of the fact that every time an object is created a constructor is called; and when that object goes out of scope a destructor is called. The constructor/destructor pair can be used to create an object that automatically allocates and initialises another object (known as the managed object) and cleans up the managed object when it (the manager) goes out of scope. This mechanism is generically referred to as resource management. A resource could be any object that required dynamic creation/deletion – memory, files, sockets, mutexes, etc. Resource management frees the client from having to worry about the lifetime of the managed object, potentially eliminating memory leaks and other problems in C++ code. However, RAII/RRID doesn’t come without cost (to be fair, what does?) Introducing a ‘manager’ object can lead to potential problems – particularly if the ‘manager’ class is passed around the system (it is just another object, after all).
    [Show full text]
  • Copy Constructors
    Copy Constructors • Shallow Copy: – The data members of one object are copied into the data members of another object without taking any dynamic memory pointed to by those data members into consideration. (“memberwise copy”) • Deep Copy: – Any dynamic memory pointed to by the data members is duplicated and the contents of that memory is copied (via copy constructors and assignment operators -- when overloaded) Copy Constructors • In every class, the compiler automatically supplies both a copy constructor and an assignment operator if we don't explicitly provide them. • Both of these member functions perform copy operations by performing a memberwise copy from one object to another. • In situations where pointers are not members of a class, memberwise copy is an adequate operation for copying objects. • However, it is not adequate when data members point to memory dynamically allocated within the class. Copy Constructors • Problems occur with shallow copying when we: – initialize an object with the value of another object: name s1; name s2(s1); – pass an object by value to a function or when we return by value: name function_proto (name) – assign one object to another: s1 = s2; Copy Constructors • If name had a dynamically allocated array of characters (i.e., one of the data members is a pointer to a char), – the following shallow copy is disastrous! n am e sm it h ("Su e Sm it h "); / / on e ar g con st r u ctor u sed n am e clon e(sm it h ); / / d efau lt cop y con st r u ctor u sed smith clone ptr S ptr u length=10 length=10 e S m i t h '\0' Copy Constructors • To resolve the pass by value and the initialization issues, we must write a copy constructor whenever dynamic member is allocated on an object-by-object basis.
    [Show full text]
  • Chapter 11: Resource Management ______
    Chapter 11: Resource Management _________________________________________________________________________________________________________ This chapter is about two things – putting away your toys when you're done with them, and bringing enough of your toys for everyone to share. These are lessons you (hopefully!) learned in kindergarten which happen to pop up just about everywhere in life. We're supposed to clean up our own messes so that they don't accumulate and start to interfere with others, and try to avoid hogging things so that others don't hurt us by trying to take those nice things away from us. The focus of this chapter is how to play nice with others when it comes to resources. In particular, we will explore two of C++'s most misunderstood language features, the copy constructor and the assignment operator. By the time you're done reading this chapter, you should have a much better understanding of how to manage resources in ways that will keep your programs running and your fellow programmers happy. The material in this chapter is somewhat dense, but fear not! We'll make sure to go over all of the important points neatly and methodically. Consider the STL vector. Internally, vector is backed by a dynamically-allocated array whose size grows when additional space is needed for more elements. For example, a ten-element vector might store those elements in an array of size sixteen, increasing the array size if we call push_back seven more times. Given this description, consider the following code: vector<int> one(kNumInts); for(size_t k = 0; k < one.size(); ++k) one.push_back(int(k)); vector<int> two = one; In the first three lines, we fill one with the first kNumInts integers, and in the last line we create a new vector called two that's a copy of one.
    [Show full text]
  • Basic Concepts of Oops & Classes and Objects
    BASIC CONCEPTS OF OOPS & CLASSES AND OBJECTS Object-Oriented Programming groups related data and functions together in a class, generally making data private and only some functions public. Restricting access decreases coupling and increases cohesion. It has proven to be very effective in reducing the complexity increase with large programs. For small programs may be difficult to see the advantage of OOP over, eg, structured programming because there is little complexity regardless of how it's written. It helps in programming approach in order to built robust user friendly and efficient software and provides the efficient way to maintain real world software. OOP is an Object Oriented Programming language which is the extension of Procedure Oriented Programming language. OOPs reduce the code of the program because of the extensive feature of Polymorphism. OOPs have many properties such as DataHiding, Inheritance Data Abstraction, Data Encapsulation and many more. The main aim is to creating an Object to the Entire program and that to we can control entire program using the Object. The main features of OOPS is Polymorphism, Multiple Inheritance, Abstraction and Encapsulation. Objects: Object is the basic unit of object-oriented programming. Objects are identified by its unique name. An object represents a particular instance of a class. An Object is a collection of data members and associated member functions also known as methods. Classes: • Classes are data types based on which objects are created. • Thus a Class represents a set of individual objects. Characteristics of an object are represented in a class as Properties. The actions that can be performed by objects become functions of the class and are referred to as Methods.
    [Show full text]
  • Copy Constructor and Assignment Operator, to Create a New Object Cloning Another One Or Copying Its Attributes
    Programmazione Prof. Marco Bertini marco.bertini@unifi.it http://www.micc.unifi.it/bertini/ Deep vs. shallow copy Methods created by the compiler • We have seen that the compiler creates for each class a default constructor and destructor… • … but it creates also default copy constructor and assignment operator, to create a new object cloning another one or copying its attributes. • C++11 compiler may create other methods, not discussed in this lecture. Copy methods • C++ treats variables of user-defined types with value semantics. This means that objects are implicitly copied in various contexts. • The copy constructor creates a fresh object based on the state of an existing object. • The assignment operator copies the state of a source object onto an existing target object, thus it has to work a bit more to deal with the already existing target. The compiler • According to the C++ standard: • The compiler will implement copy constructor and assignment operator if they are used but not provided by the programmer (implicit definition) • The implicitly-defined copy constructor for a non-union class X performs a memberwise copy of its sub-objects. • The implicitly-defined copy assignment operator for a non-union class X performs memberwise copy assignment of its subobjects. Shallow copy • The implicit methods copy the content of the attributes of the class, i.e. they perform a bit- by-bit copy of their content (shallow copy). • Is this enough to get a working copy of our object ? Shallow copy example class GameCharacter { // Implicit methods created by the public: // compiler. The default constructor GameCharacter(std::string& name, // is not created because of the int hp) : name(name), hp(hp) // constructor provided by us.
    [Show full text]
  • Rvalue References, Move Semantics, Universal References PV264 Advanced Programming in C++
    Rvalue References, Move Semantics, Universal References PV264 Advanced Programming in C++ Nikola Beneš Jan Mrázek Vladimír Štill Faculty of Informatics, Masaryk University autumn 2020 PV264: Rvalue References, Move Semantics, Universal References autumn 2020 1 / 30 pre-C++11: reallocation means copies copies can be expensive (or even impossible) however, we know that the copied elements will be destroyed immediately afterwards move semantics: take advantage of this observation Motivation How does std::vector work? start endReserved end PV264: Rvalue References, Move Semantics, Universal References autumn 2020 2 / 30 pre-C++11: reallocation means copies copies can be expensive (or even impossible) however, we know that the copied elements will be destroyed immediately afterwards move semantics: take advantage of this observation Motivation How does std::vector work? start endReserved end PV264: Rvalue References, Move Semantics, Universal References autumn 2020 2 / 30 pre-C++11: reallocation means copies copies can be expensive (or even impossible) however, we know that the copied elements will be destroyed immediately afterwards move semantics: take advantage of this observation Motivation How does std::vector work? start endReserved end PV264: Rvalue References, Move Semantics, Universal References autumn 2020 2 / 30 pre-C++11: reallocation means copies copies can be expensive (or even impossible) however, we know that the copied elements will be destroyed immediately afterwards move semantics: take advantage of this observation Motivation
    [Show full text]
  • EMC++ Chapter 4 Smart Pointers C++11 / C++14 Smart Pointer Types Auto Ptr Unique Ptr Shared Ptr Weak Ptr
    EMC++ Chapter 4 Smart Pointers C++11 / C++14 smart pointer types auto_ptr unique_ptr shared_ptr weak_ptr C++11 / C++14 smart pointer types auto_ptr C++98. Deprecated in C++11. Removed in C++17. unique_ptr C++11 replacement for auto_ptr. C++14 adds make_unique. shared_ptr C++11. Reference-counting. weak_ptr C++11. "Weak" references. EMC++ Item 18 Use std::unique_ptr for exclusive-ownership resource management. std::unique_ptr<T> stack heap ptr to T controlled object of type T std::unique_ptr<T, Deleter> stack heap ptr to T controlled object deleter of type T of type Deleter EMC++ Item 19 Use std::shared_ptr for shared-ownership resource management. std::shared_ptr<T> stack heap ptr to T ptr to controlled object control block reference count weak ref count custom deleter? ptr to controlled object Copying a std::shared_ptr stack heap ptr to T ptr to controlled object control block reference count ++ ptr to T weak ref count ptr to custom deleter? control block ptr to controlled object std::shared_ptr to base class stack heap ptr to A controlled object of type ptr to class D: control public A, B block reference count ++ ptr to B weak ref count ptr to default_delete<D> control block ptr to controlled object of type D “Shares ownership with” #include <memory> #include <vector> using Vec = std::vector<int>; std::shared_ptr<int> foo() { auto elts = { 0,1,2,3,4 }; std::shared_ptr<Vec> pvec = std::make_shared<Vec>(elts); return std::shared_ptr<int>(pvec, &(*pvec)[2]); } int main() { std::shared_ptr<int> ptr = foo(); for (auto i = -2; i < 3; ++i) { printf("%d\n", ptr.get()[i]); } } “Shares ownership with” #include <memory> #include <vector> using Vec = std::vector<int>; std::shared_ptr<int> foo() { auto elts = { 0,1,2,3,4 }; std::shared_ptr<Vec> pvec = std::make_shared<Vec>(elts); return std::shared_ptr<int>(pvec, &(*pvec)[2]); } Share ownership with pvec but point to &(*pvec)[2] int main() { std::shared_ptr<int> ptr = foo(); for (auto i = -2; i < 3; ++i) { printf("%d\n", ptr.get()[i]); } } EMC++ Item 20 Use std::weak_ptr for shared_ptr-like pointers that can dangle.
    [Show full text]
  • Objects with Dynamic Memory Contents the Compiler Will
    Objectdynmemory.oo3 10/1/13 2:45:27 1 Objects with dynamic memory contents Some terminology needed for two ways in which the contents of one object are supplied by another. Copy - one object gets a copy of the data in another object Two notions of copy applied to member variables: shallow copy - we simply copy the values of the declared member variables. deep copy - we copy the data referred to by member variables (especially data referred to by a pointer). Copy construction - create and initialize an object containing a copy of an existing object's data Thing t2(t1); // create t2 and initialize it to have a copy of the contents of t1; Thing t2 = t1; // same effect - not an assignment because t2 is a newly defined object Copy assignment - discard the current contents of lhs object and change it to a copy of rhs's contents Thing t1, t2; . // stuff is done to t1 and t2 t1 = t2; // whatever was in t1 is gone, replaced by a copy of t2; Another concept - instead of copying the data, we move the data (new in C++11) always a "shallow" move - no such thing as a "deep" move - only member variable values are changed. move construction - new object gets the existing object's data, original object left in an "empty" state move assignment - lhs gets the data in rhs; rhs left in "empty" state Moving data is much faster than copying data, and works just fine if original owner of the data is no longer going to be used for anything But original object must be left in a state in which it can be destroyed correctly - like an "empty" state, or some other valid contents.
    [Show full text]