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

Adding the Clang analysis (clang ... --analyze) capabilities #783

Closed
yh-sb opened this issue May 29, 2017 · 5 comments
Closed

Adding the Clang analysis (clang ... --analyze) capabilities #783

yh-sb opened this issue May 29, 2017 · 5 comments

Comments

@yh-sb
Copy link

yh-sb commented May 29, 2017

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".

@bobbrow
Copy link
Member

bobbrow commented May 30, 2017

Have you tried our linter? Add "C_Cpp.intelliSenseEngine": "Default" to your settings.json file.

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.

@DemiMarie
Copy link

@bobbrow Are you talking about the EDG C++ front end?

@bobbrow
Copy link
Member

bobbrow commented May 31, 2017

Yes, we use the EDG C++ front end.

@boazsegev
Copy link

@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 C_Cpp.intelliSenseEngine isn't working (see #746 ) or whether using clang will provide better results (even though I believe it will).

The fact of the matter is that clang is also used as collaborative "glue" in many projects, where the .clang_complete file allows us to share settings and flags across development environments.

If vscode can't support clang and it's .clang_complete convention, than collaboration is made that much harder.

I don't know if you code in C or C++ as much, but as a C developer I find clang integration to provide a major improvement to my workflow and I totally appreciate @r44083 's offer to fix this up.

This might just be my 2¢, but I would appreciate if you gave the matter some consideration.

@yh-sb
Copy link
Author

yh-sb commented Jan 10, 2019

Now, the cpptools extension works really well, so it isn't any need to extend it with clang mode support.
Thank you.

@yh-sb yh-sb closed this as completed Jan 10, 2019
@github-actions github-actions bot locked and limited conversation to collaborators Oct 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants