Closed vbfox closed 8 years ago
I'll use this PR to also fix #280
LGTM. After this, the policy to always specify values (perhaps by writing an analyzer) sounds even better.
Yes while I think we should allow still allow to not specify them when they aren't in the header files, we should have an analyzer and only suppress it after the header file have been checked and a comment is added.
// Sequential values are used in the original header file (WinUser.h)
#pragma warning disable XXXX
It's a lot more specific an would avoid "OOPS" cases like this
Fixes #278
Note: No idea if it build as my work PC can't build the solution at the moment, showing :
So i'll let appveyor decide :)