[boost] Re: A mem_fn thought

From: David Abrahams (dave_at_[hidden])
Date: 2003-09-18 12:48:32

"Peter Dimov" <pdimov_at_[hidden]> writes:

> David Abrahams wrote:
>> "Peter Dimov" <pdimov_at_[hidden]> writes:
>>
>>> The problem here is that mem_fn(&X::m) can only expose a single
>>> result_type, and the choice is between M or M const&, neither of
>>> which allows assignment. boost::mem_fn exposes M const& as its
>>> result_type. It _returns_ a proper non-const reference when its
>>> argument is (a pointer to) non-const, though, except on MSVC <7.0
>>> and, ironically, Metrowerks (a recent patch by
>>> Dave)
>>
>> I broke Metrowerks??
>
> No, you only broke MSVC 7.0. ;-)
>
> You changed
>
> #if !defined(BOOST_MSVC) || (BOOST_MSVC > 1300)
>
> to
>
> #if !BOOST_WORKAROUND(BOOST_MSVC, < 1300) && !BOOST_WORKAROUND(__MWERKS__,
> BOOST_TESTED_AT(0x3003))
>
> effectively applying the VC7- workaround to all Metrowerks versions
> IIUC.

And how did that break vc7 ??!  Oh, whoops.  I should've written "<=
1300", right?

Are you going to fix this or am I?

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com