Hacker News new | past | comments | ask | show | jobs | submit login

> The reason for this is that Microsoft's C compiler is notoriously bad at receiving language updates and you would otherwise be stuck with C89.

And what Armin means by "notoriously bad at receiving language updates" is that Microsoft has repeatedly and explicitly stated through Herb Stutter that it does not want C, the C90 compiler is essentially an anomaly, it will remain but it will not be updated to a more recent standard, and only the C++ subset of standards more recent than C90 would ever be supported (by the C++ compiler, if you want pure C you're out of luck)

http://herbsutter.com/2012/05/03/reader-qa-what-about-vc-and...




This year at build was reported that vs 2013 will have C99 support (not complete).

http://blogs.msdn.com/b/vcblog/archive/2013/07/19/c99-librar...


This is, as previously, support for the C standard library in its capacity as a (qualified) subset of the C++ standard library.

VS will have no more C99 support that what was previously stated by Stutter: it will support the common subset of C and C++.


http://blogs.msdn.com/b/somasegar/archive/2013/06/28/cpp-con... lists some non-library C99 features not in C++.


That isn't true; as part of the C++11 support Visual Studio is getting, Microsoft is implementing more of C99 language support.

To quote the blog post the other person mentioned:

...the RTM version will also include a few tactical C99 language extensions when compiling C code...

You can thank the C++11 committee for that; they worked to bring the C11 standard into the fold with C++11.

It's going to become increasingly difficult for curmudgeonly vendors to refuse to support C11 if they support C++11.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: