FIX: Nested Macros Cause Errors C2065 and C2064

Last reviewed: September 19, 1997
Article ID: Q164947
The information in this article applies to:
  • The C/C++ Compiler (CL.EXE) included with: - Microsoft Visual C++, 32-bit Editions, versions 4.0, 4.1

SYMPTOMS

A nested macro may cause errors similar to the following:

   error C2065: 'MACRO_B' : undeclared identifier
   error C2064: term does not evaluate to a function
   error C2143: syntax error : missing ';' before '}'

CAUSE

The second macro is not being expanded correctly. A preprocessed file for the following sample shows that MACRO_B is not expanded:

      { MACRO_B ("Hello world.\n") };

It should expand to:

      { { printf("Hello world.\n"); } };

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug was corrected in Visual C++ 32-bit Edition, versions 4.2.

MORE INFORMATION

Sample Code

      /* Compile options needed: none
      */

      #include <stdio.h>

      #define MACRO_A(A)      { MACRO_B A }
      #define MACRO_B(A)      { printf(A); }

      void main()
      {
          MACRO_A(("Hello world.\n"));
      }

Keywords          : CLIss CodeGen kbtool kbbuglist kbfixlist vcbuglist400 vcbuglist420
Component         : C/C++ Compiler
Version           : 4.0 4.1
Platform          : NT WINDOWS
Issue type        : kbbug
Solution Type     : kbfix


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 19, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.