The information in this article applies to:
SYMPTOMSThe 16-bit compilers listed above incorrectly generate the follow error message: In Visual C++32-bit Edition, the following error is incorrectly generated:
CAUSEThe scope of an identifier in C is determined by the placement of its declaration. According to the ANSI specification, if an identifier's declarator or type specification appears within a list of parameter declarations in a function prototype, the identifier is said to have "function prototype scope." This scope terminates at the end of the function prototype. In the C and QuickC compilers, this scope is not correctly terminated for structure and union tags, and a C2025 error may be incorrectly generated. STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. MORE INFORMATION
The sample code below demonstrates this problem. The identifier "tag1" is a
struct/union tag that does appear twice, but because the second instance
appears in the prototype for func1(), it should have scope that is local to
the prototype only. The same is true for "num". If an outer declaration of a lexically identical identifier exists in the same name space, it is hidden until the current scope terminates, after which it again becomes visible.Thus, both of these identifiers should not be visible outside of the prototype itself. Yet, the compiler correctly allows the name "num" to be reused, while incorrectly generating the following error for "tag1": -or-
Sample Code
Additional query words: kbVC400bug 8.00 8.00c 9.00 10.00 10.10 10.20
Keywords : kbCompiler kbVC100bug kbVC200bug kbVC400bug kbVC410bug kbVC420bug kbVC500bug kbVC600bug |
Last Reviewed: July 27, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |