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

...

Not being an expert on min/max macro issues, I wonder if this is necessary, or if the macro could be prevented from leaking to user code (without the user defining NOMINMAX).

I am not quite sure what you are complaining about. Boost.Test doesn't define these macro nor it could undefine them. If you do not want to be exposed to system level headers use offline component.

The question basically was, if the macros could be automatically undefined after the inclusion of the windows headers in case they weren't defined in beforehand (or alternatively, if NOMINMAX could be selectively defined for the implementation of Boost.Test). Stephan