Re:Visual Studio Code 1.5
by redwards510 on Thursday September 08, 2016 @09:45PM
(#12459123)
I tried to get C++ working in vscode but ran into trouble getting it to debug with gdb. I was looking for a smooth "hit f5 to compile and run (with breakpoints)" experience like I am used to with VS, but unfortunately there are no tutorials I could find on making that happen. The C++ extension is available, but I can't figure out what exactly it does or how to use it. It suffers from that common problem where they give you a config file, but don't tell you the possible options. There is an opportunity for a good blog post here if someone out there knows how to do this!
This may be due to a bug I've filed a few days ago:
https://github.com/Microsoft/vscode-cpptools/issues/191#issu...
Unfortunately, it seems that the fix hasn't been landed on this release yet.
100% agree, similar experience
I've used it a lot for C with great success, although that's not C++.
Give it a shot with the cpptools (I think that's what it's called), as well as the clang extension (which improved the experience by an order of magnitude).
Re:Visual Studio Code 1.5
by Hydraulix989 on Thursday September 08, 2016 @06:09PM
(#12457825)
Are they mutually exclusive? Or can I use both? You recommend clang instead?
I really don't like how limited Sublime's linting/static analysis options are.