-
Notifications
You must be signed in to change notification settings - Fork 91
Fix #449 (Update c++ standard to c++11) #450
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
Conversation
@mptre Do you have objections about switching from C++03 to C++11 ? |
No, I don't have any objections |
@danmar Well, that's up to you to decide. I am not aware of switching to C++11 helping with any of the major known problems, so it's an arbitrary decision. If the ticket or the PR had some reasoning there might be something to base a discussion on. |
No objection.
|
It's just that C++11 has some nicer syntax and more robustness in general.. it is not a specific problem. |
Not at all. The important issue is to still support C++03 syntax analysis of simplecpp with other source code files. |
The question is how many people have this integrated into a C++03 codebase but I guess that feedback will come after the change. It would allow to fix some minor warnings from various tooling. But taking the previous paragraph in mind we should hold off on those for a few weeks. |
Probably makes sense to enable the two C++11 warnings for Clang in |
Thanks for asking. No objections. |
FYI: Clang-tidy has some great code analysis tools, supporting C++11 and later. I am looking forward to this transition! |
No description provided.