-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C++11 as standard #114
Comments
It's definitely something that I've been ruminating in the last few months. From the developer point of view it's a no-brainer. However, since we (OceanScan) have a lot of systems in the field with C++98 only compilers it would be a major effort for us to upgrade those systems in order for them to run new DUNE versions. With that being said, I'm inclined to take the leap to C++14 one of these days. |
That makes sense, and thank you for the reply. In the meantime, would be it an option to somehow enable this on a task-specific basis? Or the other way around, disable tasks if C++14 is not available for the compiler? This would make it possible to use the legacy compilers for most of the tasks. I'l close this for now as I mainly wanted your input, keep us posted. |
Reopened to hear the status of this. |
I gave LSTS access to OceanScan-MST codebase which already sets the
required C++ standard to C++-14. We are using gcc 4.9 for production which
supports C++-11 and some C++-14 features.
…On Wed, Aug 29, 2018 at 12:37 PM Kristian Klausen ***@***.***> wrote:
Reopened to hear the status of this.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#114 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABTFhE2FLR1oOlwESefipvFwChkijiYzks5uVnzngaJpZM4R1Q1B>
.
|
Now using CPP14 (master). |
Hi,
I was wondering if there has been any discussion about using C++11 as default for DUNE? We have been using it internally for a while, and several of the features are really useful when working with DUNE.
Kristian
The text was updated successfully, but these errors were encountered: