Re: [boost] Visual Studio 2015 Update 3 has removedstd::unary_functionand std::binary_function

Subject: Re: [boost] Visual Studio 2015 Update 3 has removedstd::unary_functionand std::binary_function
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2016-11-07 11:23:33

On 11/07/16 18:01, Edward Diener wrote:
>
> I have been making fixes on the 'develop' branch of various CMT
> libraries, but I don't think it should be an issue for 1.63 so close to
> release. In other words I think it too dangerous to push these fixes for
> 1.63 as it is now scheduled and I don't see why we can't wait for 1.64.
> While we try to satisfy VC++ end-users because VC++ is a very heavily
> used compiler I would not compromise the integrity of the release for
> this issue. If Boost decides to push back the 1.63 release by a few
> weeks to satisfy this single concern, then I can see trying to push
> through these changes for 1.63.

I'd rather have 1.63 released in time but without all the fixes for 
MSVC. Just my 2 cents.

Also, isn't there a way to bring those deprecated components back even 
in the C++17 mode? A macro or a compiler switch? The standard library 
still has to have them for C++14 mode, doesn't it?