9Proprietary + Confidential Large Scale Refactorings & Automated Refactoring Tools 10 10Refactoring Tool Use Cases 02 11Proprietary + Confidential Consistent Code Formatting 12 12Proprietary + Confidential

RBJ .OBJ .OBJ .DEF CvtRes .LIB C runtime, DLL Import, .LIB C runtime, DLL Import, .EXE .EXE tool text file binary file 图 1- 1 一个32位Wi ndows SDK 程序的开发流程 曾经有的程序，现已不需要 5 Win32 程序开发流程 Windows Registration 2. Persistent Object Data Format 3. Mapping of Windows Handles to Objects 4. C++ Template Tool 6. Message Maps 7. Debugging Trace Options 8. MFC OLE Support 11. Using MFC as Part of a DLL Applications with MFC3.1 ■MFC Architecture TN002: Persistent Object Data Format TN004: C++ Template Tool TN006: Message Maps TN016: Using C++ Multiple Inheritance with MFC TN019: Updating Existing MFC

onwards, there is a commitment to stability, with the goal of not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions 2.1, 2.2, ..., 2.X should in Github and counts with contributions from more than 300 different users (this is just the client tool). • Many other users contribute recipes for ConanCenter via the https://github.com/conan-io/conan-center-index contain hands-on, fully operational examples with code, aimed to explain some very specific feature, tool or behavior. They do not have a conducting thread, they should be navigated by topic. • The reference

onwards, there is a commitment to stability, with the goal of not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions 2.1, 2.2, ..., 2.X should in Github and counts with contributions from more than 300 different users (this is just the client tool). • Many other users contribute recipes for ConanCenter via the https://github.com/conan-io/conan-center-index contain hands-on, fully operational examples with code, aimed to explain some very specific feature, tool or behavior. They do not have a conducting thread, they should be navigated by topic. • The reference

onwards, there is a commitment to stability, with the goal of not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions 2.1, 2.2, ..., 2.X should in Github and counts with contributions from more than 300 different users (this is just the client tool). • Many other users contribute recipes for ConanCenter via the https://github.com/conan-io/conan-center-index contain hands-on, fully operational examples with code, aimed to explain some very specific feature, tool or behavior. They do not have a conducting thread, they should be navigated by topic. • The reference

onwards, there is a commitment to stability, with the goal of not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions 2.1, 2.2, ..., 2.X should in Github and counts with contributions from more than 300 different users (this is just the client tool). • Many other users contribute recipes for ConanCenter via the https://github.com/conan-io/conan-center-index contain hands-on, fully operational examples with code, aimed to explain some very specific feature, tool or behavior. They do not have a conducting thread, they should be navigated by topic. • The reference

onwards, there is a commitment to stability, with the goal of not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions 2.1, 2.2, ..., 2.X should in Github and counts with contributions from more than 300 different users (this is just the client tool). • Many other users contribute recipes for ConanCenter via the https://github.com/conan-io/conan-center-index contain hands-on, fully operational examples with code, aimed to explain some very specific feature, tool or behavior. They do not have a conducting thread, they should be navigated by topic. • The reference

onwards, there is a commitment to stability, with the goal of not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions 2.1, 2.2, ..., 2.X should in Github and counts with contributions from more than 300 different users (this is just the client tool). • Many other users contribute recipes for ConanCenter via the https://github.com/conan-io/conan-center-index contain hands-on, fully operational examples with code, aimed to explain some very specific feature, tool or behavior. They do not have a conducting thread, they should be navigated by topic. • The reference

onwards, there is a commitment to stability, with the goal of not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions 2.1, 2.2, ..., 2.X should in Github and counts with contributions from more than 300 different users (this is just the client tool). • Many other users contribute recipes for ConanCenter via the https://github.com/conan-io/conan-center-index contain hands-on, fully operational examples with code, aimed to explain some very specific feature, tool or behavior. They do not have a conducting thread, they should be navigated by topic. • The reference

onwards, there is a commitment to stability, with the goal of not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions 2.1, 2.2, ..., 2.X should in Github and counts with contributions from more than 300 different users (this is just the client tool). • Many other users contribute recipes for ConanCenter via the https://github.com/conan-io/conan-center-index contain hands-on, fully operational examples with code, aimed to explain some very specific feature, tool or behavior. They do not have a conducting thread, they should be navigated by topic. • The reference