Would you this problem affect the autocompletion, calltip and symbol browser?Sure, yes. because the macro expansion happens in the lower tokenizer level, so that the high level parserthread only see the expanded tokens.
I take some time to do a simple research, I think macro expansion shouldn't be a problem.
Let me put the example code here again.
Here, I think a good code style is not use the macro definition to give a type a new name, the best way here is using typedef.
So, if we have the code:
typedef unsigned char uint8;
void f(uint8 aaa);
Then, the parser still see the "void f(uint8 aaa);"
I see that under MSVC, many types are actually typedef, such as "BOOL", "LPCTSTR".
BTW: I don't see much response about this patches serials
, so this is a "ping" for further comments, thanks.