[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #61800] possible code simplification with c++1
From: |
Arun Giridhar |
Subject: |
[Octave-bug-tracker] [bug #61800] possible code simplification with c++17 std::variant |
Date: |
Wed, 12 Jan 2022 15:43:34 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Android 11; Mobile; rv:95.0) Gecko/95.0 Firefox/95.0 |
Follow-up Comment #2, bug #61800 (project octave):
C++17 is already 4.5 years old at this point and gcc has supported it since
gcc 5, and it's default in gcc 11.
https://gcc.gnu.org/projects/cxx-status.html#cxx17
A search shows there are very few distros that ship compilers older than that:
https://distrowatch.com/search-mobile.php?pkg=gcc&relation=less&pkgver=5.0&distrorange=InLatest#pkgsearch
of which Scientific Linux is the largest and that was last updated in 2018,
now discontinued. The results for Clang 5 are similarly old.
If there are benefits to Octave in using C++17 (such as the polymorphic
allocator and the improvement in this report), it would be worth switching to
it from Octave 8, which gives enough time for packages to catch up. No need to
maintain two versions in parallel.
How do the maintainers feel about making current Octave 8 dev sources require
C++17 once Octave 7 has been released?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?61800>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/