From: Mike (mike.dev_at_[hidden])
Date: 2019-08-22 09:16:46
> Gesendet: Donnerstag, 22. August 2019 um 11:06 Uhr
> Von: "Hans Dembinski via Boost" <boost_at_[hidden]>
> The max/min macro issue does not seem to be relevant anymore in modern compilers. I was completely unaware of this in Boost.Histogram and the code works fine on all msvc versions which support C++14. I added the patches to Histogram to get rid of this warning, but now that code became a lot less readable. I am considering to revert this change and propose instead to remove the min/max macro check from the inspection list. Or is there a way to blacklist it locally for my library?
This is not a compiler problem. The windows.h file (https://en.wikipedia.org/wiki/Windows.h) is defining those macros
unless special workarounds are applied like defining NOMINMAX before including the file.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk