??
In the near future, Effectvie C + + carefully read the side, very marvel at the power and charm of C + +. Recent reading experience and reading notes will be recorded here in the near future. necessary to find the use, assuming the summary of what is wrong, welcome criticism:
Now only the framework is listed. It will be fully populated as soon as possible:
Part 2nd: Construction/destruction/assignment operations
Personally feel that this is a more difficult to understand the C + + place, but also the depth of C + +, just start reading, may be in some places do not understand, the best way is to read the side of the programming implementation, intentions to think about its essence!
Article 5: Understanding C + + silently writing and invoking those functions
Article 6: If you do not want to use the compiler's own self-generated functions, it should be understood to deny
Article 7: Declaring a virtual destructor for a polymorphic base class
Article 8: Don't let exceptions escape destructors
Article 9: Never call the virtual function in the construction and destruction process
Clause 10: Make operator= return a reference to *this
Article 11: Handling Self-assignment in operator=
Article 12: Don't forget every ingredient when copying objects
Note: Because there are a lot of links between the terms, all some of the provisions are not suitable for separate pull out, this will be combined with other provisions of the record, there is no understanding of the place. Welcome to the Exchange.
Effective C + + study notes (part Two:item 5-12)