Home/ Questions/Q 6186319
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T01:52:04+00:00

What I’m talking about is to find a way to avoid the macros in

  • 0

What I’m talking about is to find a way to avoid the macros in <windows.h> from polluting whatever project I’m writing.

Excerpts from windows.h:

#ifdef UNICODE
#define LoadImage  LoadImageW
#else
#define LoadImage  LoadImageA
#endif // !UNICODE

#ifdef UNICODE
#define GetMessage  GetMessageW
#else
#define GetMessage  GetMessageA
#endif // !UNICODE

The majority of macros (over 99%) I’m okay with, but some of them I just couldn’t find a way to avoid.

My idea is that since I always qualify the functions calls in my particular framework, e.g. ImageTool::LoadImage, Visual Studio should have enough clue that I’m not referencing the Windows API, which are all in the root namespace, i.e. ::LoadImage. But the MACRO system does not seem to be that smart.

Is there a compiler or preprocessor option that will just enable that?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Macro substitution are basically simple textual replacements, done before the proper compiler even starts to parse the code. Therefore they are not aware of namespaces or any other parts of the C++ syntax above the pure lexical level.

    The straight forward way to avoid replacement of your identifiers is to remove the macros:

    #ifdef LoadImage
#undef LoadImage
#endif

    This of course will also stop following code from accessing the Windows API with the name LoadImage.

    • 0