Skip to content
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.

Sign up for GitHub

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

Jump to bottom

C++ 11 #453

Closed
apeyser opened this issue Aug 8, 2016 · 2 comments
Closed

C++ 11 #453

apeyser opened this issue Aug 8, 2016 · 2 comments
Labels
I: External API Developers of extensions or other language bindings may need to adapt their code S: Normal Handle this with default priority T: Discussion Still searching for the right way to proceed / suggestions welcome ZC: Kernel DO NOT USE THIS LABEL ZP: Reminder DO NOT USE THIS LABEL

Comments

@apeyser
Copy link
Contributor

apeyser commented Aug 8, 2016

Following #344, we should consider transitioning towards C++11.

All HPC machines currently support at least C++ 11, except possibly for K, which is in the process of porting their gcc-based compiler to gcc-4.8.2 at some point this year.

STLs are usable, curly brace constructors remove narrowing, constructors and converters are vastly improved, templates are vastly improved...

In fact given that most machines will have llvm compilers going forward, an even more aggressive position is tenable.
@apeyser apeyser mentioned this issue Aug 11, 2016
Merged
@heplesser heplesser added ZC: Kernel DO NOT USE THIS LABEL I: External API Developers of extensions or other language bindings may need to adapt their code ZP: Reminder DO NOT USE THIS LABEL S: Normal Handle this with default priority T: Discussion Still searching for the right way to proceed / suggestions welcome labels Nov 17, 2016
@uahic
Copy link
Contributor

uahic commented Jan 5, 2017 •
edited
Loading

@apeyser
Is it 'allowed' to include C++11 code in pull requests from now on? I did not find any hint what the current state is, in the MUSIC repo we also wanted to move towards c++11 but same issue .. waiting for K ;)

@jougs
Copy link
Contributor

jougs commented Feb 7, 2018

At the NEST Conference 2017 we officially announced that C++11 is allowed in NEST from now on. I'm thus closing this issue.

@jougs jougs closed this as completed Feb 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
I: External API Developers of extensions or other language bindings may need to adapt their code S: Normal Handle this with default priority T: Discussion Still searching for the right way to proceed / suggestions welcome ZC: Kernel DO NOT USE THIS LABEL ZP: Reminder DO NOT USE THIS LABEL
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@apeyser @heplesser @jougs @uahic