-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Adding the Clang analysis (clang ... --analyze) capabilities #783
Comments
Have you tried our linter? Add We're not ruling out the possibility of supporting Clang as a linter at some future date, but it's not in our current roadmap. Our extension is not open source due to license restrictions in some of the code we use, so unfortunately there is no way for us to integrate any pull requests at this time. |
@bobbrow Are you talking about the EDG C++ front end? |
Yes, we use the EDG C++ front end. |
@bobbrow , I'm thankful for all the work you're all putting in to help create and improve this wonderful program. However, this isn't just about the fact that the default The fact of the matter is that If vscode can't support I don't know if you code in C or C++ as much, but as a C developer I find This might just be my 2¢, but I would appreciate if you gave the matter some consideration. |
Now, the cpptools extension works really well, so it isn't any need to extend it with clang mode support. |
Hi, I some times ago I had used SublimeText to work with C/C++ projects. To simplify my workflow I wrote extension which analyzed my opened files. It work pretty intellectually, see example below:
https://github.com/r44083/clang-linter
Now I have completely migrated to the VSCode and I was disappointed by the lack of such analysis. So I am going to implement this feature for VSCode.
I would like to integrate this into the "vscode-cpptools" extension. In this case Clang linter disables intellisense analyzer
Let me know if you agree to integrate my pool requests.
Clang analysis tool works really fast, reliably and deeply analyzes the code "on the fly".
The text was updated successfully, but these errors were encountered: