Add the debug header to the function (3)

PreviousAdd the debug header to the function (Extension 2)

New features to be added

1. The inclusion of debug_astyle.h does not add path layer identification. You can directly use the system directory or additional directory for configuration items to achieve the effect. Use the # include <debug_asytle.h> statement. The disadvantage is that debug_astyle.h can only be the same for different projects, but it is not a problem (MFC and non-MFCProgramAt the same time, question 5 about # include <windows. h> is exposed ).

2. identify whether the header and tail macros have been added. If they have already been added, they will not be added again (Advanced Extension: maintain a file operation record table. For files that have not been modified since the previous traversal, no repeated scansCode)
3. Identify call levels (obtain thread IDs and use different call counts for different threads to monitor the runtime of the function stack called by threads)
4. performance problems (for functions that have been repeatedly called for a short time, disable printing debugging strings. Will it be slower? Although it requires constant judgment, it should be acceptable that it is not displayed on a low-speed device such as a screen. However, this is lossy optimization detection and compromise .)

5. Fatal error c1189: # error: Windows. h already included. MFC APPs must not # include <windows. h> for the MFC class, identify # include "stdafx. H ", placed after it, and debug_astyle.h cannot contain # include <windows. h>. Currently, it is still manual. It seems difficult to identify the code files of the MFC class.

6. Create a UI tool, mainly tree control + checkbox, to select the folder path to be configured for the file tree