macro and member function conflict

前端 未结 5 539
名媛妹妹
名媛妹妹 2020-12-05 18:05

I have problem that,std::numeric_limits::min() conflicts with the \"min\" macro defined in \"windef.h\". Is there any way to resolve this conflict without undefine the \"mi

相关标签:
5条回答
  • 2020-12-05 18:22

    Yep, I've meet the same problem. I found only one solution:

    #ifdef min
    #undef min
    #endif //min
    

    Place it right after includes have done.

    0 讨论(0)
  • 2020-12-05 18:23

    In addition to jalf's answer, you could also #define WINDOWS_LEAN_AND_MEAN before including windows.h. It will get rid off min, max and some more noise from windows headers.

    0 讨论(0)
  • 2020-12-05 18:26

    The only really general solution is to not include windows.h in your headers.

    That header is a killer, and does pretty much anything it can to make your code blow up. It won't compile without MSVC language extensions enabled, and it is the worst example of macro abuse I've ever seen.

    Include it in a single .cpp file, and then expose wrappers in a header, which the rest of your code can use. If windows.h isn't visible, it can't conflict with your names.

    For the min/max case specifically, you can #define NOMINMAX before including windows.h. It will then not define those specific macros.

    0 讨论(0)
  • 2020-12-05 18:26

    Dewfy, The problem with that solution is if you nee to use the macro afteryards.

    I even tried the defining NOMINMAX but it didn't work.

    The best solution i found was the one from Johannes Schaub: (std::numeric_limits::min)()

    0 讨论(0)
  • 2020-12-05 18:29

    The workaround is to use the parenthesis: int max = (std::numeric_limits<int>::max)();

    It allows you to include the windef.h, doesn't require you to #undef max (which may have adverse side effects) and there is no need to #define NOMINMAX. Works like a charm!

    0 讨论(0)
提交回复
热议问题