Opened 6 years ago
Last modified 5 years ago
#12972 new Bugs
converter.hpp uses std::unary_function which is removed in c++17
| Reported by: | anonymous | Owned by: | Fernando Cacciola |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | numeric |
| Version: | Boost 1.64.0 | Severity: | Problem |
| Keywords: | c++17, Visual Studio 2017 | Cc: | antoshkka@… |
Description
Some code, which uses boost::lexical_cast does not compile on Windows 10 with Visual Studio 2017 Community using the compiler flag /std:c++latest (which enables c++17 standard). From what I understand from this page http://en.cppreference.com/w/cpp/utility/functional/unary_function, std::unary_function will be removed with c++17. However, struct Trivial_converter_impl and struct rounding_converter in file converter.hpp derive from std::unary_function
Change History (12)
follow-up: 2 comment:1 by , 6 years ago
| Milestone: | To Be Determined → Boost 1.62.0 |
|---|---|
| Resolution: | → obsolete |
| Status: | new → closed |
comment:3 by , 5 years ago
| Resolution: | obsolete |
|---|---|
| Status: | closed → reopened |
| Version: | Boost 1.63.0 → Boost 1.64.0 |
comment:4 by , 5 years ago
| Component: | conversion → numeric |
|---|---|
| Milestone: | Boost 1.62.0 → To Be Determined |
comment:5 by , 5 years ago
| Owner: | changed from to |
|---|---|
| Status: | reopened → new |
comment:6 by , 5 years ago
| Cc: | added |
|---|
comment:7 by , 5 years ago
Can confirm that while this seems to be fixed in develop, no one has merged from develop to master in months or longer.
comment:10 by , 5 years ago
There is a PullRequest with a fix for VS 2017. As soon as I figure out how to properly merge it, I will.
comment:11 by , 5 years ago
Since I am not too familiar with the release cycles, may I ask when we can expect a new version to contain this merge?
comment:12 by , 5 years ago
With another boost release coming up within a couple of weeks, would it be possible to merge this (if it hasn't already)? I (and surely many others) would be very grateful indeed!
The issue was fixed here in version 1.62