08-28-2019, 12:36 AM
We currently use C++11. Shall we move on to C++17? Doing that would require dropping the clang-3.5 and gcc-4.8 from Travis CI tests (thus making Travis twice as fast 
| Poll: Which C++ standard shall we use? You do not have permission to vote in this poll. |
|||
| Keep C++11 | 0 | 0% | |
| Update to C++17 | 0 | 0% | |
| Total | 0 vote(s) | 0% | |
| * You voted for this item. | [Show Results] |
|
Update c++ standard?
|
08-28-2019, 12:37 AM
My 1.13 work in https://github.com/cuberite/cuberite/pull/4377 already uses some C++17 features, but if we so decide, I can still change it back to C++11.
08-28-2019, 12:41 AM
@bearbin will there be problems with the buildserver cross-compiling for raspberry pi?
08-28-2019, 12:56 AM
(08-28-2019, 12:41 AM)xoft Wrote: @bearbin will there be problems with the buildserver cross-compiling for raspberry pi? The current version of GCCused for the crosscompile-builds on the buildserver doesn't support C++17, so it will need to be updated. I'll get on that if it's confirmed that we are switching over to the new standard. |
|
« Next Oldest | Next Newest »
|
Users browsing this thread: 3 Guest(s)