Page 1 of 2
C++ 17
Posted: 24 Oct 2017, 13:17
by psi29a
One of the things to look out for is this:
https://www.phoronix.com/scan.php?page= ... -System-TS
ISO/IEC TS 18822:2015 defines a set of standard interfaces for C++ for dealing with file-system operations. This TS, which is based upon the Boost library's file-system implementation, is optional in C++17 and is now supported by the GCC C++ compiler.
The C++ file-system library introduces the concept of paths, directory entries, file information, easy copying of files, symlink handling, file renaming, checking of file types, and other easy helpers.
This would help us ditch even more Boost and I hope that we an aim to target this when gcc, clang and msvc mature...
Re: C++ 17
Posted: 24 Oct 2017, 14:54
by Chris
I doubt we'll be using C++17 any time soon, considering we don't even use C++14 and only recently started using C++11. It'd be nice if we could start using C++14, though we'd almost certainly have to drop MSVC 2013 support for that.
Re: C++ 17
Posted: 24 Oct 2017, 17:36
by Ace (SWE)
I'd be all for dropping VS2013 support soon, keeping official support to the two latest stable versions should hopefully be enough for people. Even if it means probably losing Windows XP support.
But yes, let's move to C++14 before we try to aim for 17.
Re: C++ 17
Posted: 24 Oct 2017, 18:28
by psi29a
I'm game...
Re: C++ 17
Posted: 24 Oct 2017, 19:34
by lysol
Ace (SWE) wrote: ↑24 Oct 2017, 17:36
Even if it means probably losing Windows XP support.
There will of course be people against this, but seriously. We need to let that OS die.
Re: C++ 17
Posted: 24 Oct 2017, 19:51
by psi29a
Let's get this party started right...
https://github.com/OpenMW/openmw/pull/1520
Sorry, XP is dead along with Vista... Microsoft said so. Done and done.
Re: C++ 17
Posted: 24 Oct 2017, 20:03
by AnyOldName3
lysol wrote: ↑24 Oct 2017, 19:34
Ace (SWE) wrote: ↑24 Oct 2017, 17:36
Even if it means probably losing Windows XP support.
There will of course be people against this, but seriously.
We need to let that OS die.
And probably its users. If they're so keen to let their computers get viruses, then they're probably a massive risk to public health and need quarantining and burning lest they kill us all.
Re: C++ 17
Posted: 24 Oct 2017, 20:24
by psi29a
Right, so how do we flip the switch for MSVC?
Re: C++ 17
Posted: 24 Oct 2017, 21:05
by Ace (SWE)
MSVC always builds with the latest supported C++ version, so there's no switch to flip on there. It's just a case of starting to push C++14 code.
You know that you've reached c++14 territory (Or just full C++11 territory) once MSVC2013 builds start failing, at which point it's probably best to update the appveyor config to build with 2015 and 2017 instead
Re: C++ 17
Posted: 24 Oct 2017, 21:07
by psi29a
OK, so I don't need to do anything until someone does something >= C++14-ish
