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.

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

We should select a C++ std too #372

Closed
FiloSpaTeam opened this issue Apr 26, 2018 · 5 comments
Closed

We should select a C++ std too #372

FiloSpaTeam opened this issue Apr 26, 2018 · 5 comments

Comments

@FiloSpaTeam
Copy link
Contributor

C++ 11/14/17 ... 👍

@annejan
Copy link
Member

annejan commented Apr 26, 2018

The only hinderance is upstream compatibility (older linux distributions).

But that should not stop us in my opinion.

@FiloSpaTeam
Copy link
Contributor Author

No, certainly.
We can always use preprocessor definitions to support something. But i think some standards are important too nowdays 😀

@FiloSpaTeam
Copy link
Contributor Author

I ve seen in .pro thst we support c+11 so we can use this one i think?

@jounathaen
Copy link
Member

I guess c++11 is widely supported.
This discussion lists the common Linux distros which have c++11 support: icecc/icecream#353 and that's representing almost every available Linux Distro.
I guess on Win and Mac there is also c++11 widespread.

As far as I heard of, c++14 was not such a big thing, so I think it is not a necessary dependency. (Haven't used these features myself).

My suggestion: C++11 and closing this issue :-D

@annejan annejan closed this as completed Aug 15, 2018
@annejan
Copy link
Member

annejan commented Oct 24, 2018

Check out #425 for some semi-automated cleanup . .

This will probably break on some older linux distro's . .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants