Microsoft KB Archive/182659

{|
 * width="100%"|

PRB: Signed/Unsigned Mismatch Warning When Using MSCS Constants

 * }

Q182659

-

The information in this article applies to:


 * Microsoft Win32 Software Development Kit (SDK)
 * Microsoft Windows NT Server, Enterprise Edition version 4.0

-

SYMPTOMS
When building a project that uses "constants" defined for Microsoft Cluster Server, the compiler might report a signed or unsigned mismatch warning.

CAUSE
The values are defined in clusapi.h using enum instead of #define. Enum values are of type int, but the values are most often used as DWORD (unsigned long) parameters. If the high bit of the value is set, the compiler generates a warning.

RESOLUTION
The values can be cast to a DWORD before assigning them to, or using them as, a DWORD. For example:

  dwParam = (DWORD) CLUSTER_CHANGE_HANDLE_CLOSE;

STATUS
This behavior is by design.

MORE INFORMATION
When the high bit of one value of an enum is set, the compiler considers the value to be negative. When the value is assigned to an unsigned variable, the compiler warns that some information (the "negativeness") is lost in the assignment.

Enums are used instead of #define to make it easier for other languages to use the values from a generated type library.

Additional query words:

Keywords :

Issue type : kbprb

Technology : kbWinNTsearch kbWinNT400xsearch kbWinNTSsearch kbWinNTSEntSearch kbWinNTSEnt400 kbWinNTS400xsearch kbWin32SDKSearch kbAudDeveloper kbSDKSearch kbWin32sSearch