From: Eric Niebler (eric_at_[hidden])
Date: 2004-01-02 11:57:54
John Maddock wrote:
>>There are known ways of dealing with this problem. Putting parens around
>>the min and max identifiers prevents the macro invocation. For instance,
>> std::max( a, b ); ==> (std::max)( a, b );
> True, but it's a horrible fix, to be blunt why should Boost authors be
> forced to mangle their perfectly conforming code in order to support one
> non-conforming system?
For the same reason that Boost authors mangle their perfectly conforming
code with horrible macros like BOOST_NESTED_TEMPLATE,
BOOST_STATIC_CONSTANT, etc. Namely, to make it easy to use Boost on the
widest number of platforms possible.
-- 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