3 ms·
My experience with hobbyist C programming in VSCode (with C/C++ extension) is yet to match the experience of hobbyist C++ programming in VS. I'll try out CLion
by markus_zhang 4y ago
My experience with hobbyist C programming in VSCode (with C/C++ extension) is yet to match the experience of hobbyist C++ programming in VS. I'll try out CLion someday.
The biggest issues I noticed are:
- Lack of error indication e.g. used an indeclared variable
- Intellisense meh
- Rusky 4y agoThe C/C++ extension actually uses the same underlying engine as VS's C++ IntelliSense. If you're missing things like error indicators then it's likely you just need to configure it a bit more precisely- VS Code has a bunch of ways to do that, but they're all sort of DIY, while VS's is set up out of the box if you're using its project format or CMake support.
- edg5000 4y agoThere is an intellisense alternative for VS Code called clangd (made by LLVM developers) you might want to try, I use it heavily. You don´t need to use clang as your compiler. It scans my CMake output to perform indexing.
- markus_zhang 4y agoThanks! Gonna try it out. Does it conflict with the official C/C++ extension?
- spacemanspiff01 4y agoYou need to disable intelligence (there is a popup)
- shepherdjerred 4y agoCLion is pretty good! If you like JetBrians IDE's, you'll like CLion.
- markus_zhang 4y agoThanks, I do! I use Pycharm and Datagrip a lot in my current life, both are excellent.
- qalmakka 4y agoAs another comment said, try Clangd, it's IMHO superior to intellisense on VSCode and supports anything that can emit `compile_commands.json`files.
- markus_zhang 4y agoThanks man. TBH I never dug deep into those json files. I need to take a look.