If a certain design pattern UML can be reproduced in your head, then it will be easy to encode. UML reverse tool basically relies on header files.h/.hpp to analyze the relationship between classes. From the perspective of use, it is impossible to obtain a perfect UML diagram from the code. It requires manual modification. You can first reverse the UML relationship diagram based on the reverse function of the UML tool, and then manually modify it. Currently, commonly used UML diagram tools include: EA, IBM's ROSE, StartUML, and Understand. From the perspective of usage effect: EA=ROSE>Understand=StartUML, among which the EA tool comes with very powerful help.
I spent 2 days studying the use of CMake and sorted out oneCMake usage tutorial, it was actually pushed to the homepage. It was extremely lucky. Later, I made a relatively simple and practical CMakeLists and generated Visual Studio project to compile the code for each design pattern. It felt good.
In the past, most of the developments used Git's daily operations such as modification, fallback, patching, merging, and submission. Now we learn more about managing open source code knowledge, and also read a very meaningful book. If you are interested in making open source code, this book is recommended.Click here to visit, available in Chinese.
A lightweight log system glog from Google has simple functions, but can basically meet the needs of small projects. It is much lighter than log4cpp and is suitable for use in small projects. It is not used in the design mode because there are too few logs for each design mode, and it is a bit redundant to use it forcibly. It is considered as a preparation for the future.
Also use the coding specifications from Google. If you are interested, you can clickGet it hereGoogle's open source project style guide, also has a Chinese version! This specification feels generally good when used, and it corrects some of my previous minor problems, but some still feel it is not good, such as the naming of member variables, which prefers to start with "m_". Google recommends full spelling of words, lowercase, and adding '_' at the end. Of course, it varies from person to person. Overall, if the team uses the same standards when developing, it is a good method.