Possible problems with NOMINMAX on Visual C++

Question

What problems could I get when defining NOMINMAX before anything else in my program?

As far as I know, this will make not

Answer 1

Using NOMINMAX is the only not-completely-evil way to include . You should also define UNICODE and STRICT. Although the latter is defined by default by modern implementations.

You can however run into problems with Microsoft’s headers, e.g. for GdiPlus. I’m not aware of problems with headers from any other companies or persons.

If the header defines a namespace, as GdiPlus does, then one fix is to create a wrapper for the relevant header, where you include , and inside the header’s namespace, using namespace std; (or alternatively using std::min; and using std::max):

#define NOMINMAX
#include 
namespace Gdiplus
{
  using std::min;
  using std::max;
}

Note that that is very different from a using namespace std; at global scope in header, which one should never do.

I don’t know of any good workaround for the case where there's no namespace, but happily I haven’t run into that, so in practice that particular problem is probably moot.