-
Notifications
You must be signed in to change notification settings - Fork 171
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? #7
Comments
Yes. Plus don't shy away from dropping VS 2010 support. 😉 |
VS2013 (not sure about VS2015) has incomplete support for const_expr, initializer lists and std::chrono::high_resolution_timer only has millisecond accuracy (not sure if they fixed that in one of the recent updates). Other then that I haven't come across major C++11 showstoppers across platforms (gcc 4.8, clang 3.x, VS2013+2015). |
A lot more people are willing to accept C++11 in this binding which is very cool! If I really need C++11 only stuff (like lambdas or something like that) and using old features would hurt the perfomance/readability/end user interface then I'll use it and at the same time I'll try to make it optional. :) |
I think also the next major sfml release will make use of c++11 (sfml 3.x) |
@susnux yeah, this will be so neat |
Any new thoughts about that topic? |
Once SFML is going to have a stable release with C++17 in it (and it's currently being rewritten to it), I might use C++17 in ImGui-SFML too. |
Hm, the (quite old) topic was about c++11. The readme states that you still target 03. Is that still valid? If so, is there a chance that you at least start targeting 11 (or even 14)? |
Yes, ImGui-SFML still works on C++03. C++11 seems a bit old and if we go "modern C++" it doesn't make sense to stick with version that's over 10 years old. |
Reopening, since this is a thing now. Please note that for now only C++11 (not C++14,17, etc.) will be used. |
Actually, I'll create a new issue about this. :) |
I tried to avoid using C++11 because ImGui and SFML don't use it and I didn't want to introduce new dependencies.
But I've noticed lately that I used
nullptr
and there were no complaints about that. So, what if I moderately use C++11 from now on? Here's some stuff I want to use (all of it is supported in VS 2010+ and in old GCC and Clang versions):auto
nullptr
unique_ptr
The text was updated successfully, but these errors were encountered: