5 ms·
> But today, there is little reason for most projects not use the advances found in C99. Does visual studio support c99 yet? Last I heard MS wasn’t interested
by imron 7y ago
> But today, there is little reason for most projects not use the advances found in C99.
Does visual studio support c99 yet? Last I heard MS wasn’t interested in supporting it.
- hazeii 7y agoReally? No longer an MS user but occasionally my code gets ported to Windows so would like to know more.
- dfox 7y agoMSVC in C mode is essentially C89 plus extensions needed to compile C++/C99-isms present in Windows SDK and DDK headers. And Microsoft seems to be mostly interested in whether the compiler is able to build NT kernel and drivers and nothing much else.
- nwellnhof 7y agoThat's not true for quite some time. Visual Studio 2013 added many C99 features that aren't in C++ like compound literals or designated initializers.
- flohofwoe 7y agoThe only notable C99 features not supported on the MSVC C compiler are: (a) VLAs, and (b) type-generic macros. The distinction between the MSVC C and C++ compiler is important though. The MSVC C++ compiler doesn't support any C99 features.
- zelly 7y agoYou can use clang on VS
- xeeeeeeeeeeenu 7y agoIt supports most of it. Useless stuff like VLA is still uninmplemented though.
- polyphonicist 7y agoWhy is VLA useless? Why was it added to C99?
- flohofwoe 7y agoBecause even C isn't free from the occasional misfeature slipping into the standard. VLAs come with a lot of caveats (e.g. available stack size being limited and opaque, no sizeof() support, etc). VLAs were made optional in C11, so it's better not to use them at all for portable code.