From: Eric Niebler (eric_at_[hidden])
Date: 2006-06-19 15:30:51
Stephan Tolksdorf wrote:
>>>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
>>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).
Could they be undefined? Yes. Should they? Absolutely not. Whether we
like it or not, there is code out there that depends on the fact that
#include <windows.h> causes the min/max macros to be defined. Boost
should not interfere.
-- Eric Niebler Boost Consulting www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk