C++- Big Three in C99
来源:互联网 发布:nginx ssl跳转 编辑:程序博客网 时间:2024/04/30 11:52
Introduction
C++ treats variables of user-defined types with value semantics.This means that objects are implicitly copied in various contexts,and we should understand what "copying an object" actually means.
Let us consider a simple example:
class person{ std::string name; int age;public: person(const std::string& name, int age) : name(name), age(age) { }};int main(){ person a("Bjarne Stroustrup", 60); person b(a); // What happens here? b = a; // And here?}
(If you are puzzled by the name(name), age(age)
part,this is called amember initializer list.)
Special member functions
What does it mean to copy a person
object?The main
function shows two distinct copying scenarios.The initializationperson b(a);
is performed by the copy constructor.Its job is to construct a fresh object based on the state of an existing object.The assignmentb = a
is performed by the copy assignment operator.Its job is generally a little more complicated,because the target object is already in some valid state that needs to be dealt with.
Since we declared neither the copy constructor nor the assignment operator (nor the destructor) ourselves,these are implicitly defined for us. Quote from the standard:
The [...] copy constructor and copy assignment operator, [...] and destructor are special member functions. [Note: The implementation will implicitly declare these member functions for some class types when the program does not explicitly declare them. The implementation will implicitly define them if they are used. [...]end note ] [n3126.pdf section 12 §1]
By default, copying an object means copying its members:
The implicitly-defined copy constructor for a non-union class X performs a memberwise copy of its subobjects. [n3126.pdf section 12.8 §16]
The implicitly-defined copy assignment operator for a non-union class X performs memberwise copy assignment of its subobjects. [n3126.pdf section 12.8 §30]
Implicit definitions
The implicitly-defined special member functions for person
look like this:
// 1. copy constructor person(const person& that) : name(that.name), age(that.age) { } // 2. copy assignment operator person& operator=(const person& that) { name = that.name; age = that.age; return *this; } // 3. destructor ~person() { }
Memberwise copying is exactly what we want in this case:name
and age
are copied, so we get a self-contained, independent person
object.The implicitly-defined destructor is always empty.This is also fine in this case since we did not acquire any resources in the constructor.The members' destructors are implicitly called after the person
destructor is finished:
After executing the body of the destructor and destroying any automatic objects allocated within the body, a destructor for class X calls the destructors for X's direct [...] members [n3126.pdf 12.4 §6]
Managing resources
So when should we declare those special member functions explicitly?When our classmanages a resource, that is,when an object of the class is responsible for that resource.That usually means the resource isacquired in the constructor(or passed into the constructor) and released in the destructor.
Let us go back in time to pre-standard C++.There was no such thing as std::string
, and programmers were in love with pointers.Theperson
class might have looked like this:
class person{ char* name; int age;public: // the constructor acquires a resource: // in this case, dynamic memory obtained via new[] person(const char* the_name, int the_age) { name = new char[strlen(the_name) + 1]; strcpy(name, the_name); age = the_age; } // the destructor must release this resource via delete[] ~person() { delete[] name; }};
Even today, people still write classes in this style and get into trouble:"I pushed a person into a vector and now I get crazy memory errors!"Remember that by default, copying an object means copying its members,but copying thename
member merely copies a pointer, not the character array it points to!This has several unpleasant effects:
- Changes via
a
can be observed viab
. - Once
b
is destroyed,a.name
is a dangling pointer. - If
a
is destroyed, deleting the dangling pointer yields undefined behavior. - Since the assignment does not take into account what
name
pointed to before the assignment,sooner or later you will get memory leaks all over the place.
Explicit definitions
Since memberwise copying does not have the desired effect, we must define the copy constructor and the copy assignment operator explicitly to make deep copies of the character array:
// 1. copy constructor person(const person& that) { name = new char[strlen(that.name) + 1]; strcpy(name, that.name); age = that.age; } // 2. copy assignment operator person& operator=(const person& that) { if (this != &that) { delete[] name; // This is a dangerous point in the flow of execution! // We have temporarily invalidated the class invariants, // and the next statement might throw an exception, // leaving the object in an invalid state :( name = new char[strlen(that.name) + 1]; strcpy(name, that.name); age = that.age; } return *this; }
Note the difference between initialization and assignment:we must tear down the old state before assigning toname
to prevent memory leaks.Also, we have to protect against self-assignment of the formx = x
.Without that check, delete[] name
would delete the array containing thesource string,because when you write x = x
, both this->name
andthat.name
contain the same pointer.
Exception safety
Unfortunately, this solution will fail if new char[...]
throws an exception due to memory exhaustion.One possible solution is to introduce a local variable and reorder the statements:
// 2. copy assignment operator person& operator=(const person& that) { char* local_name = new char[strlen(that.name) + 1]; // If the above statement throws, // the object is still in the same state as before. // None of the following statements will throw an exception :) strcpy(local_name, that.name); delete[] name; name = local_name; age = that.age; return *this; }
This also takes care of self-assignment without an explicit check.An even more robust solution to this problem is thecopy-and-swap idiom,but I will not go into the details of exception safety here.I only mentioned exceptions to make the following point:Writing classes that manage resources is hard.
Noncopyable resources
Some resources cannot or should not be copied, such as file handles or mutexes.In that case, simply declare the copy constructor and copy assignment operator asprivate
without giving a definition:
private: person(const person& that); person& operator=(const person& that);
Alternatively, you can inherit from boost::noncopyable
or declare them as deleted (C++0x):
person(const person& that) = delete; person& operator=(const person& that) = delete;
The rule of three
Sometimes you need to implement a class that manages a resource.(Never manage multiple resources in a single class,this will only lead to pain.)In that case, remember therule of three:
If you need to explicitly declare either the destructor, copy constructor or copy assignment operator yourself, you probably need to explicitly declare all three of them.
(Unfortunately, this "rule" is not enforced by the C++ standard or any compiler I am aware of.)
Advice
Most of the time, you do not need to manage a resource yourself,because an existing class such asstd::string
already does it for you.Just compare the simple code using astd::string
memberto the convoluted and error-prone alternative using achar*
and you should be convinced.As long as you stay away from raw pointer members, the rule of three is unlikely to concern your own code.
- C++- Big Three in C99
- Big-Three
- String的Big-Three
- c++ big three
- C++中的Big Three
- The Big Three Rule
- C++ 之 Big Three
- Big Three+noncopyable
- C++ Big Three
- string 模拟之-big three
- Big Three设计原则学习
- return c C99
- C标准--C99
- wikipedia c language -c99
- Ecllipse c配制C99
- c语言 c99 标准
- ANSI C,C90,C99
- ANSI C和C99
- LTE Rel-12及其后续演进系统中的MIMO技术
- win32常用消息WM_DESTROY - 窗口销毁时的消息
- 用手机播放电脑上的文件
- win32常用的消息WM_SYSCOMMAND - 系统命令消息
- Qt学习手记 - 1
- C++- Big Three in C99
- win32常用的消息WM_CREATE - 窗口创建成功,但还未显示之前
- Android应用程序结构
- 算法和数据结构的实际应用
- ATM
- win32常用的消息WM_SIZE - 窗口的大小发生变化后
- c++ 模板学习笔记:函数模板的类型识别(权哥)
- 制作网页中的表单并在提交时对输入的内容进行检验
- win32函数 MoveWindow使用说明