WIN32 vs. _WIN32

_WIN32 vs. WIN32

1. Predefined macros

The Microsoft C/C++ compiler (MSVC) predefines certain preprocessor macros, depending on the language (C or C++), the compilation target, and the chosen compiler options.

MSVC supports the predefined preprocessor macros required by the ANSI/ISO C99, C11, and C17 standards, and the ISO C++14 and C++17 standards. The implementation also supports several more Microsoft-specific preprocessor macros. Some macros are defined only for specific build environments or compiler options. Except where noted, the macros are defined throughout a translation unit as if they were specified as /D compiler option arguments. When defined, the macros are expanded to the specified values by the preprocessor before compilation. The predefined macros take no arguments and can't be redefined..

2. What's the difference between the WIN32 and _WIN32 defines in C++

I know that WIN32 denotes win32 compilation but what is _WIN32 used for?.

3. QM BITES: UNDERSTAND WINDOWS OS IDENTIFICATION PREPROCESSOR MACROS

There’s confusion between user-defined and predefined Windows 32/64-bit operating-system identification macros. Matthew Wilson shines light on the issue..

4. Both _WIN32 and _WIN64 are defined when targeting 32-bit windows from 64-bit windows #1062

Both _WIN32 and _WIN64 are defined when targeting 32-bit windows from 64-bit windows #1062.

5. Option to remove _WIN32 define for Windows platform #1235

This is a paragraphIn issue #185 Bob wrote:

_WIN32 and MACH should be defined already on the relevant platforms, but if there are additional defines that you need to define, you can add them to the "defines" array in your c_cpp_properties.json file.

We have some common code for windows and embedded systems. When developing firmware for embedded systems having _WIN32 defined in #ifdef branches causes some extra includes, which are not available and rises errors about missing headers. Is it possible to remove _WIN32 define?

Suggestion: do not force _WIN32 define. Leave it as default for windows platform but add an option to remove it..

6. Should I define both _WIN32 and _WIN64 in 64bit build?

When we add a 64bit configuration from a 32bit project that has already existed, Visual Studio copies the 32bit configurations by default. VS even copies _WIN32 All my 64bit projects define also _WIN32 now, despite they(64bit PEs) never can run on 32bit Windows. It is very uncomfortable to me.

I'd like to remove the _WIN32 if it doesn't have any problem. I'm not sure about that. Is it okay if I remove the _WIN32 definition?.

7. WIN32 versus _WIN32

n the many projects I have been involved in I see a very mixed bag. And more importantly, what is the right thing to do?.

8. The difference between WIN32 and _WIN32

The difference between WIN32 and _WIN32.

9. What's the difference between the WIN32 and _WIN32 defines in C++

I know that WIN32 denotes win32 compilation but what is _WIN32 used for?.

This is a paragraph.

This is a paragraph.

This is a paragraph.

This is a paragraph.

This is a paragraph.

This is a paragraph.

This is a paragraph.

This is a paragraph.

This is a paragraph.