Re: [boost] [test] test/included min max macro issue

Gennaro Prota wrote:

That would of course be possible, but still not transparent. Basically the first inclusion of windows.h for each translation unit determines whether the min and max macros will be present.

(...)

Microsoft's logic for the windows.h header seems to imply that it is never included from include files. This holds every time you put NOMINMAX, NOTHIS or NOTHAT macros in the apparent intent to give the user more control: what results, as you can see, is no control at all.

Thanks for explaining the issue. Stephan