GCC -E

days before I wrote a class with many macros, especially the ‘#'s,  to simplify the code, actually just to increase reusability, and the effect is very well. but it also brings problem to debug. it’s not easy to find out the errors if too much macros are involved, what’s worse is with template feature used. then I found the –E argument of GCC is useful, with which you can preprocess your code and check the preprocessed code to help finding the bugs. but there’s still a problem remains to resolve. the preprocessed code is bad-formatted, which is illegible. I didn’t find a good solution.

转载于:https://www.cnblogs.com/hpsoar/archive/2010/12/12/1904042.html