3 ms·

People often take it as common knowledge that Visual Studio barely supports C. As of VS2015 almost all of the C99 standard is implemented, with a few corners m

by Omnus 11y ago

People often take it as common knowledge that Visual Studio barely supports C. As of VS2015 almost all of the C99 standard is implemented, with a few corners missing, like tgmath. I am interested to see if this allows more C libraries to be built with VS rather than relying on MinGW and other Unix based alternatives.

ndesaulniers 11y ago
Indeed, on my post about "Designated Initialization With Compound Literals in C" [0], someone commented "cool, but I use MSVC so..." [1]. Note: that was two years ago, I'm sure that's not the case. I'm sure IDE's have great features; I wanted to avoid them in the article; they are simply not for me. [0] http://nickdesaulniers.github.io/blog/2013/07/25/designated-initialization-with-pointers-in-c/ http://nickdesaulniers.github.io/blog/2013/07/25/designated-... [1] http://nickdesaulniers.github.io/blog/2013/07/25/designated-initialization-with-pointers-in-c/#comment-977161427 http://nickdesaulniers.github.io/blog/2013/07/25/designated-...
santaclaus 11y ago
Doesn't Visual Studio support Clang as an official alternative to MS' compilers, now?
- ndesaulniers 11y ago
  If not now, when? I suspect this is a goal of Google's.
- TwoBit 11y ago
  I think the answer is yes and no. You can get clang to compile standard C/C++, but not any Windows code, as Microsoft has many compiler extensions and quirks they depend on.
pjmlp 11y ago
Mostly because that is required by the C++11/14 standard revisions.
aninteger 11y ago
It may increase a bit. In fact the recently started C-based project Handmade Hero is done within Visual Studio so maybe that will spark some interest. The real advantage of mingw and other opensource tools is that you can use the same compiler on both Windows and Linux. With something like msys you can even get away with using a single Makefile. Also because C is a small language many professional C developers are unlikely to use an IDE and so would more likely use the windows sdk (assuming that still ships with the command line compiler which I'm not sure about).

by Omnus 11y ago

ndesaulniers 11y ago

Indeed, on my post about "Designated Initialization With Compound Literals in C" [0], someone commented "cool, but I use MSVC so..." [1]. Note: that was two years ago, I'm sure that's not the case. I'm sure IDE's have great features; I wanted to avoid them in the article; they are simply not for me. [0] http://nickdesaulniers.github.io/blog/2013/07/25/designated-initialization-with-pointers-in-c/ http://nickdesaulniers.github.io/blog/2013/07/25/designated-... [1] http://nickdesaulniers.github.io/blog/2013/07/25/designated-initialization-with-pointers-in-c/#comment-977161427 http://nickdesaulniers.github.io/blog/2013/07/25/designated-...

santaclaus 11y ago

Doesn't Visual Studio support Clang as an official alternative to MS' compilers, now?

ndesaulniers 11y ago
If not now, when? I suspect this is a goal of Google's.
TwoBit 11y ago
I think the answer is yes and no. You can get clang to compile standard C/C++, but not any Windows code, as Microsoft has many compiler extensions and quirks they depend on.

pjmlp 11y ago

Mostly because that is required by the C++11/14 standard revisions.

aninteger 11y ago

It may increase a bit. In fact the recently started C-based project Handmade Hero is done within Visual Studio so maybe that will spark some interest. The real advantage of mingw and other opensource tools is that you can use the same compiler on both Windows and Linux. With something like msys you can even get away with using a single Makefile. Also because C is a small language many professional C developers are unlikely to use an IDE and so would more likely use the windows sdk (assuming that still ships with the command line compiler which I'm not sure about).