Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ Library : Other (not classified elsewhere) » Changing default standard from c++14 to c++17 (2020.2 Release) (Question for 2020.2 Release)
Changing default standard from c++14 to c++17 (2020.2 Release) [message #54750] Sun, 06 September 2020 22:18 Go to next message
Klugier is currently offline  Klugier
Messages: 1075
Registered: September 2012
Location: Poland, Kraków
Senior Contributor
Hello,

I just noticed that current build methods are basing on c++14 standard. Should we migrate to c++17 by default? c++14 is 6 years standard and we have two new standards that were release after (c++17 and c++20).

Klugier


U++ - one framework to rule them all.

[Updated on: Sun, 06 September 2020 22:22]

Report message to a moderator

Re: Changing default standard from c++14 to c++17 (2020.2 Release) [message #54751 is a reply to message #54750] Mon, 07 September 2020 09:25 Go to previous message
mirek is currently offline  mirek
Messages: 13975
Registered: November 2005
Ultimate Member
Klugier wrote on Sun, 06 September 2020 22:18
Hello,

I just noticed that current build methods are basing on c++14 standard. Should we migrate to c++17 by default? c++14 is 6 years standard and we have two new standards that were release after (c++17 and c++20).

Klugier


- There are problems in Win CLANG with new overloading in C++17
- I am not sure there is anything really essential in C++17 that we dramatically improve the way I do code
- I still have to support systems without C++17 support. 3 years is too short.
Previous Topic: Updating GLEW to version 2.2.0 for 2020.2 Release
Next Topic: [Proposal] Adding a GLLock struct to GLCtrl
Goto Forum:
  


Current Time: Fri Mar 29 12:13:55 CET 2024

Total time taken to generate the page: 0.01128 seconds