I found a very interesting bug that Microsoft thought about a Microsoft's interesting bug. It is interesting because this bug does not exist in the program, but exists in the header file. The phenomenon of this bug is this: If there is the following content in your project: #include
Then your project is compiled, and there is no accident, the compilation error is C1004, and the file that indicates that you go wrong is WABTags.h. I spent some time, and finally determined the problem in Microsoft. In WABTags.h, there is a non-printing character in front of the * number, which is 0xA0. This is not a problem under the English platform, and the compiler is simply slightly annotated. But the problem under the Chinese platform came out. 0xA0 is the legal LeadByte of the GB2312 character set (so-called LeadByte refers to the first byte of two bytes (such as Chinese characters)). So the compiler treats 0xA0 and the following * as a character of the double-word character set. So the entire file becomes non-compliant grammar rules. From this question, I will take a small header file in Microsoft. It is found that there is still a lot of situations that contain invalid characters, but most of these invalid characters do not have problems (because they are in the comments and have no chance to swallow normal characters). And these issues should have more than 5 years. Someone replied to me ahead: Don't say any designer, do a programmer in Microsoft, more than your designer. I don't see this sentence from or not, at least I can see a blind worship against Microsoft. I think this idea also has considerable representation. There will be a problem with this kind of emotion. Don't forget Microsoft's procedures, it is written, so they will make mistakes. In the extension, the master's words are also said, so there will be errors. To say that the old saying, I believe that others, don't forget to believe in yourself.
Author Blog:
http://blog.9cbs.net/leezy_2000
