Am 21.01.23 um 20:48 schrieb Will Godfrey:
I'm also thinking of moving to C++17 as our minimum standard. I understand there are a number of benefits to this, and it still leaves (at least) a 5 year margin for people working on older systems.
There are some nice additional features in C++17, yet our codebase rather is not written in a way that those features are really necessary. In some code I wrote for the PadSynth background loading, I used something like std::optional, by just providing our own drop-in replacement using the same implementation technique as the standard library does. Thus up to now we managed to get along well with C++14. Upgrading to C++17 would probably imply to drop off the old Ubuntu LTS releases 14.04 and 16.04. With some quirks I was still able to build a package for these, and in the past some people were glad we still supported those distros. By using a backport of a newer compiler, it might still be further possible to support those very old distros, not sure if this works though. Thus we might ask first on the users mailinglist. Needless to say that at some point we must drop compatibility, and C++17 looks like a nice target with wide support on recent systems. -- Hermann _______________________________________________ Yoshimi-devel mailing list Yoshimi-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
