Re:C++17 is formally approved
by dzdt on Thursday September 07, 2017 @01:04PM
(#15193742)
Lol. At my work I am still eagerly awaiting the arrival of C++11.
[ Parent
| on HN ]
That's not the point. The point is that, when you get it, you won't encounter a list of breaking changes and your code will continue to work.
Re:C++17 is formally approved
by ernst_klim on Friday September 08, 2017 @05:23AM
(#15198900)
>you won't encounter a list of breaking changes and your code will continue to work.
Sure, that's why my gstreamermm app refused to build when I switched to --std=c++17
Here's the list: https://stackoverflow.com/questions/6399615/what-breaking-ch...
Was it one of those? If not then the fault was with your code or the implementation, not the spec. The language itself is very good at maintaining backward compatibility.
Re:C++17 is formally approved
by ernst_klim on Friday September 08, 2017 @12:48PM
(#15201791)
>you won't encounter a list of breaking changes
>list of breaking changes
Yeap, some shit with smart pointers in glibmm, didn't investigated much.